Open ericcho opened 5 years ago
I'll have to look into why this has changed - it may be simply that if you send a Cc: header via SES, SES will act on the header and send a copy of the message to those CC'd. There may be a situation where the Cc: header is preserved, but not acted upon, but I have since forgotten what the circumstances are.
I'm not using Amazon SES. I'm using Sendmail on shared web hosting.
Dada Mail Version 8.2.0 was working for me to allow the recipients to see who was CC'ed, but even then there was a problem with not being able to see additional recipients addressed using To. That old problem is documented at https://github.com/justingit/dada-mail/issues/375
Hmm: sendmail allows you to set the recipients on the command line, telling it to ignore what's set in the message itself. In fact, the, "-t" flag is added to explicitly look at the headers, rather than on the command line (in the sendmail manpage, this is called the, "send list")
I could re-implement this, but it would mean that there's an option for sendmail, that would NOT be available for SMTP or Amazon SES - which could add some confusion to users. I prefer parity to all the different ways to send out a message.
According to this, the idea (use a send list instead of having the MTA parse the headers themselves) is still supported using postfix's sendmail binary:
I'd like to see this re-implemented also - I use Amazon SES.
About four years ago, Dada Mail would preserve the To: and CC: recipients in the header. That was useful so the recipients could see who all received the message and reply to the same recipients. Can that feature be put back in, at least as an option? Whether the mailing list is in To: or CC: ? I notice there were two issues involving CC:
May 24, 2015 CC addresses not removed from bridge email when using SES #507
Oct 17, 2017 bridge plugin, Cc field with list email address, repetitively sends emails #698