Individual reminder emails

[nop33]

Currently, the reminder emails are sent by including all the recipients in the BCC field. We need to reconsider this approach and maybe send one email per recipient, using the TO field instead, since the implementation causes issues to some mailing list servers.

[mlassnig]

Hello, I've recently seen a similar problem, as we typically put mailing lists (egroups) as destinations for the reminders. Turns out that this information is then lost, and this breaks the email filters for the egroups (which are typically done like if "To:" == <egroup> then move to <folder>. Thanks.

[artlbv]

Same here, the absence of the To:filed brakes our discourse email filter

[ThiefMaster]

To be fair, I don't think sending event reminders to a discourse mail-in address makes much sense...

[artlbv]

To be fair, I don't think sending event reminders to a discourse mail-in address makes much sense...

Well, with the move from Hypernews to discourse this is what we'll have to live with in CMS.

Personally I prefer calendar notifications for events (which is why I subscribe to the indico category ics), but some people only live within email.

[ThiefMaster]

I think a good option for this particular usecase would be to use the Indico API to check for upcoming events and then use that data to notify people using whatever way they prefer (could be discourse, mattermost, email, etc)

[artlbv]

So the built-in reminder functionality is for who them? for events with registered users?

[ThiefMaster]

Its primary goal is to send emails to humans... and there it's typically not a problem to use BCC - many newsletters etc do that as well.

That said, I think sending emails to individual recipients would probably make sense nontheless; we do it in many other places as well...

[camclean]

For my POG (and most groups in CMS), the best way to consistently send meeting announcements is through indico reminders to hypernews (and now discourse). What is the problem with changing indico to use the TO field?

[ThiefMaster]

BCC: Indico sends one email, the mail server distributes it to the individual recipients. Also just one email in the indico event log
To: Indico sends n emails. Also n emails in the indico event log.

I think the logging part is in fact the main reason we did not already change this for Indico 3.0... we'll have to find some way to collapse those entries (or just accept that it;'s a bit spammy in the log)