I wasn't involved in the move of the mailing list at all, but this was a needed thing. Since all of you should have SPF records on your domain, when the mailing list program attempted to send mail with your from address, it should have been picked up by spam filters because it was coming from the AMFUG server which most likely wasn't authorized in your SPF record. With the combination of SPF, DKIM, and now DMARC, mailing lists cannot (and shouldn't) fake people's from email address. How the team that did the move completed this is technically correct. The sender's name is great but you have to use the right domain.
That being said, somehow appending the sender's email within the body of the message would be useful, as you mention to reply offlist. Additionally, while SES is DKIM signing mail, it is not doing it with the AMFUG domain. The powers that be need to setup a verified domain in SES so the mail actually appears to come from AMFUG and not SES. Robbie Wright Siuslaw Broadband <http://siuslawbroadband.com> 541-902-5101 On Fri, Oct 31, 2014 at 8:19 AM, Darin Steffl via Af <[email protected]> wrote: > I agree and was waiting to see if someone else would bring it up. It only > shows the name so I have no way of seeing the actual sender email address > to bring something off-list. > > On Fri, Oct 31, 2014 at 10:15 AM, tcidan via Af <[email protected]> wrote: > >> Since the change to the new mailing list host, the From: header on >> messages shows <[email protected]> rather than the actual sender. >> >> I find this change to not be beneficial. >> >> --danp >> > > > > -- > Darin Steffl > Minnesota WiFi > www.mnwifi.com > 507-634-WiFi > <http://www.facebook.com/minnesotawifi> Like us on Facebook > <http://www.facebook.com/minnesotawifi> >
