Page MenuHomePhabricator

don't add email addresses to CC if they are already in TO
ClosedPublic

Authored by talshiri on Jul 18 2014, 1:18 AM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Dec 12, 4:29 AM
Unknown Object (File)
Thu, Dec 12, 4:29 AM
Unknown Object (File)
Thu, Dec 12, 4:07 AM
Unknown Object (File)
Thu, Dec 12, 3:42 AM
Unknown Object (File)
Tue, Dec 10, 6:48 PM
Unknown Object (File)
Thu, Dec 5, 2:17 PM
Unknown Object (File)
Wed, Nov 20, 4:07 PM
Unknown Object (File)
Oct 26 2024, 3:23 PM
Subscribers

Details

Summary

Some mailers remove the duplicate entries themselves, but some (Mailgun) don't.
This affects installations with metamta.one-mail-per-recipient set to false, and will cause

  • ugly looking "to" entries. Gmail, for example, collapses to+cc entries to one list, so you get something that looks like "to: me me john"
  • It sometimes causes duplicate delivery of the same message when used in conjuction with Google Groups. I suspect that their message de-dup mechanism is confused by it (I fuzzed it directly with Mailgun, and saw the same message delivered twice - once directly through mailgun, and bounced again through Google Groups). This doesn't happen when the entries are not duplicated.
Test Plan

Created some tasks. Added subscribers. Things seem to work reasonably well.

Diff Detail

Repository
rP Phabricator
Lint
Lint Skipped
Unit
Tests Skipped

Event Timeline

talshiri retitled this revision from to don't add email addresses to CC if they are already in TO.
talshiri updated this object.
talshiri edited the test plan for this revision. (Show Details)
talshiri added a reviewer: epriestley.
epriestley edited edge metadata.

This is bad if you have "Cc" mail client rules and expect them to identify objects you're subscribed to, but in theory everyone "should" be using X-Phabricator-Cc, and I'm not sure this rule is useful anyway.

This revision is now accepted and ready to land.Jul 18 2014, 1:32 AM
epriestley updated this revision to Diff 23975.

Closed by commit rP570a78d42af7 (authored by @talshiri, committed by @epriestley).