Re: [Mailman-Users] 2.1.18 internal documentation suggestions
On Thu, 01 May 2014 at 22:52:27 -0700, Mark Sapiro wrote: Do you have a setting to change From: user@domain to From: user@domain.INVALID - that is the hack I would like to use. No, not currently. It is an interesting idea, but it may cause issues in delivery of mail From: a non-existent domain. None of the current options to try to work around the DMARC breakage work well; all fail in various ways. Until people figure out real ways of making DMARC work with forwrders mailing lists (see ietf-...@ietf.org for one place discussions are going on), I think it useful to have more work-around hacks out there so that people can experiment with them to see which ones more-or-less work in different situations. Andrew Partan -- 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
[Mailman-Users] Ignore DMARC bounces?
Is there some way of ignoring the DMCAC bounces? That way a message From: some...@yahoo.com will not not increase the bounce count of all Yahoo, AOL, Hotmail, ATT, MSN, and Comcast users. Yahoo ATT say this: 554 5.7.9 Message not accepted for policy reasons. See http://postmaster.yahoo.com/errors/postmaster-28.html AOL says this: 521 5.2.1 : (DMARC) This message failed DMARC Evaluation and is being refused due to provided DMARC Policy Comcast says this: 550 5.2.0 x4fx1n03n5DGQ1A034fysP Message rejected due to DMARC. Please see http://postmaster.comcast.net/smtp-error-codes.php#DM01 MSN/Hotmail say this: 550 5.7.0 (BAY0-MCn-Fn) Unfortunately, messages from (N.N.N.N) on behalf of (yahoo.com) could not be delivered due to domain owner policy restrictions.) Andrew Partan -- 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
Re: [Mailman-Users] 2.1.18 internal documentation suggestions
On Thu, May 01, 2014 at 08:29:30PM -0700, Mark Sapiro wrote: Here's what I've got. I didn't change the name of the setting, but I changed its description and all the detail. I now have Do you have a setting to change From: user@domain to From: user@domain.INVALID - that is the hack I would like to use. Andrew Partan -- 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
Re: [Mailman-Users] Creatng a new list
On Thu, Feb 02, 2006 at 01:21:44PM -0700, Ronnie Napster Tash wrote: Hi am geting this error when am creating a new mailing lists. Bug in Mailman version 2.1.7 We're sorry, we hit a bug! I ran into this too; run check_perms see if there is a new directory that was created with the wrong permissions. Fix the permissions (check_perms -f) and try to create the list again. --asp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
