Hello,

I have been following the discussion of the DMARC issues and Mailman's attempts to live with it. I was wondering if anyone has an "Executive Summary" of the DMARC issue in a general sense.

The information on the wiki talks about the impact on Mailman, but I need a generic explanation that can be presented to our CFO. Our management wants to move our email from an in-house Exchange environment (with Mailman on the side for mailing lists) to a totally MS365 solution. We have been told that everything we do with Mailman can be done with Exchange distribution lists, etc. I know all the reasons this is really a poor statement, but distribution lists have the same DMARC problem.

I created a test distribution list here. I created local contacts that forward to my personal gmail.com and icloud.com addresses. I added these and my work address to the list. Email from gmail and icloud works fine, however the author address ("From:") carries the original address. When I sent an email from my yahoo.com account, it was not delivered to gmail. I never saw a bounce, though, so I don't know who, if anyone, gets notified.

I am hoping that I can make this issue plain at an executive level so we can get them to stay with a Mailman solution as we "go to the cloud".

Of course if someone says that the current MS365 implementation has addressed this, then that's a different (unfortunate) story.

--
Gary Algier, WB2FWZ            g...@ulticom.com             +1 856 787 2758
Ulticom Inc., 1020 Briggs Rd, Mt. Laurel, NJ 08054     Fax:+1 856 866 2033

Nielsen's First Law of Computer Manuals:
    People don't read documentation voluntarily.
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Reply via email to