Separate emails sent for each recipient

[Alex Buccino <alexander.buccino@…>]

Trac sends out separate emails for each recipient which meant that putting email aliases in the CC field could mean people would get duplicate messages. If all the addresses were placed in the To and Cc fields then email servers could weed out duplicates in the standard way.

[eblot]

Note: sandbox/notification [2598] implements this feature

[Alex Buccino <alexander.buccino@…>]

Just a note: While this is as much as Trac can do, it may not address the issue of multiple emails going to users that are both addressed directly and are members of an alias. Some mail systems may handle this gracefully, but I now realize that at least our email server, Lotus Notes, is only able to weed out duplicates sent from within Notes. It appears that outside emails are always sent to all recipients, even if they are already receiving a copy as members of an alias.

[Gunnar Wagenknecht <gunnar@…>]

It would be better to collect all mail addresses for notification and remove duplicates from that list before sending notifications.

I prefere one mail per recipient and not putting everybody on CC/TO. Please not that this is also problematic from a data privacy point of view in some countries (eg. Germany). Mailinglisst or systems sending out mail to multiple recipients must ensure that recipients can't see who got this mail too.

[Gunnar Wagenknecht <gunnar@…>]

Paragraph two line one: s/Please not/Please note
;)

[eblot]

This issue is addressed up to some level in the notification sandbox.

There is a configuration option to either send the CC list as Cc: or Bcc: (to fulfill the privacy requirement). Duplicates are also removed (as long as they appear with the exact same syntax, no alias resolution is done here) before emails are sent.

I do not think one mail / recipient is a good idea, as notifications are processed synchronoulsy within the web request: the web server sends the next page once the communication with the SMTP server is complete. The current implementation​ uses one SMTP connection per recipient. Although this might be optimized, I think it is preferable to send one email for all recipients - there may be a flaw here if the list of recipients is very long, but I think this could be addressed in a second step.

[Gunnar Wagenknecht <gunnar@…>]

There is a configuration option to either send the CC list as Cc: or Bcc: (to fulfill the privacy requirement)

What's contained in the To: header?

[eblot]

To: reporter, owner (as long as I remember)
To: is always visible whatever the Cc/Bcc setting.

[eblot]

Should be fixed in [2799]

[eblot]

See also #2727.