Hey all,
My hosts and I are looking around for a solution to the recent changes by Yahoo to enable DMARC. Yahoo has broken every mailing list in the world (p=reject was turned on)
(http://www.ietf.org/mail-archive/web/ietf/current/msg87153.html)
An example below of the bounce:
[email protected]
(generated from mylist.domain.com)
SMTP error from remote mail server after end of data:
host mta5.am0.yahoodns.net [98.138.112.34]: 554 5.7.9 Message not accepted for policy reasons. See http://postmaster.yahoo.com/errors/postmaster-28.html
Suggestions seem to be:
* Suspend posting permission of all yahoo.com addresses, to limit damage
* Tell Yahoo users to get a new mail account somewhere else, pronto, if they want to continue using mailing lists
* If you know people at Yahoo, ask if perhaps this wasn't such a good
My question is, can anyone direct me to a solution to the problem. I know with mailman it can be done but having no luck with majordomo.
Thanks all,
Anthony
My hosts and I are looking around for a solution to the recent changes by Yahoo to enable DMARC. Yahoo has broken every mailing list in the world (p=reject was turned on)
(http://www.ietf.org/mail-archive/web/ietf/current/msg87153.html)
An example below of the bounce:
[email protected]
(generated from mylist.domain.com)
SMTP error from remote mail server after end of data:
host mta5.am0.yahoodns.net [98.138.112.34]: 554 5.7.9 Message not accepted for policy reasons. See http://postmaster.yahoo.com/errors/postmaster-28.html
Suggestions seem to be:
* Suspend posting permission of all yahoo.com addresses, to limit damage
* Tell Yahoo users to get a new mail account somewhere else, pronto, if they want to continue using mailing lists
* If you know people at Yahoo, ask if perhaps this wasn't such a good
My question is, can anyone direct me to a solution to the problem. I know with mailman it can be done but having no luck with majordomo.
Thanks all,
Anthony