On Oct 20, 2021, at 12:58 PM, Bruce Johnson via Mailman-Users 
<mailman-users@python.org<mailto:mailman-users@python.org>> wrote:

Thinking more upon this I think this was why we originally had the email 
hostname set to the list server FQDN instead of our domain. originally mailman 
lived on our mail server, but got moved to a different system when we moved to 
Exchange for mail (and later on to O365)  We had to create weird distribution 
lists for all the lists ( ie: a DL 
t...@pharmacy.arizona.edu<mailto:t...@pharmacy.arizona.edu><mailto:t...@pharmacy.arizona.edu>
 that has as it’s only member 
t...@lists.pharmacy.arizona.edu<mailto:t...@lists.pharmacy.arizona.edu><mailto:t...@lists.pharmacy.arizona.edu>
 ) for everything to work.

This worked well for years until we moved to a new mail spam and security 
service and introduced stricter DMARC and DKIM settings for all our mail. This 
is what broke one of our larger lists (our alumni outreach list, and of course 
it’s Homecoming next week, and the last email resulted in 650+ bounces for 
DMARC failures..mostly from aol and yahoo. )

Is it possible to have the email addresses of the mailman administrivia 
addresses (-owner -bounces, etc) be the FQDN, but outgoing list traffic be set 
to just the domain?

And I reset my test list to use the FQDN of the list server and it now works, 
so that’s the issue.  :-(



--
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group

Institutions do not have opinions, merely customs

------------------------------------------------------
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
    https://mail.python.org/archives/list/mailman-users@python.org/

Reply via email to