Re: [Mailman-Users] All AOL unsubscribed
AOL, AOL, AOL - they always do things a bit differently. I can't fully blame them as they probably are still the #1 target of spammers. As others have written, the most important information is in the outgoing SMTP logs so you can see what AOL said, if anything, about why they are refusing the mail. You will also find useful information at the links below, provided by AOL to help the rest of the world navigate their unique email processing: http://postmaster.aol.com/Postmaster.Troubleshooting.php http://postmaster.aol.com/Reputation.php On Fri, Dec 12, 2014 at 09:32:25AM -0500, joseph cook wrote: This morning all of my subscribers with aol addresses were automatically unsubscribed from my list. [...] -- 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] OS X Question --- yes I know sigh
On Sun, Nov 23, 2014 at 04:54:09PM -0700, David Dodell wrote: Hi, I know from past experience that the OS X version of Mailman is met with some contempt because of what Apple did with it .. but I have it working well for several years on a 10.7.5 Lion Server, and it has been very stable. Note that there's also a version from MacPorts: $ port list mailman mailman@2.1.13 mail/mailman [this is on my Mountain Lion box, your mileage may vary] -- 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] Mountain Lion server trouble
This is why it's important to keep server configurations in a configuration management system, like Chef, Puppet, cfengine, Ansible, Salt Stack, etc. When set up right, the configuration management will put back any unwanted OS changes, or at the very least tell after an upgrade what files no longer contain your edits. On Tue, Nov 04, 2014 at 11:59:02AM -0500, nxnw wrote: ... 1. Mostly good news - after the OS and server.app upgrades, mailman was (mostly) running. The only thing that was not working was the web interface. After a bit of investigation, I found that the upgrade overwrote /Library/Server/Web/Config/apache2/httpd_server_app.conf, so that file had to be edited (again) to add the following: #Mailman Include /private/etc/apache2/extra/httpd-mailman.conf I put the above right after Include /Library/Server/Web/Config/apache2/other/*.conf. Apache must be restarted after the edit. -- 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] Squirrelmail and wrapped messages
I've converted a list to Mailman, and as I posted previously, I decided to use wrapped messages to keep AOL's hairtrigger spam filters from discarding incoming messages from AOL users. Now I'm getting complaints from Outlook 2007 and Squirrelmail users that the messages from Mailman show up as text attachments that aren't automatically displayed or previewed. It looks like Outlook 2007 users can turn previewing on, but I don't see any such options for Squirrelmail. How have other Mailman admins dealt with this? I wonder if it's possible to to make wrapped messages a user preference, or have them only turned on for certain domains as discussed previously. Is this a patch that would be accepted in the future? -- Ed -- 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] AOL screening Reply-To header thru DMARC ?
I'm setting up a new Mailman server to replace an elderly MajorDomo that isn't DMARC-compatible. I set up the list to use the list's address as the From address and to put the sender's address in Reply-To:. I started playing around with a test list - in no time at all, AOL began bouncing all my mail. After researching AOL's error messages, it appeared that my server had been temporarily blacklisted. That went away but then I noticed this error: Oct 18 01:01:26 vc18 postfix/smtp[25098]: C77D416B4D9: host mailin-01.mx.aol.com[152.163.0.67] said: 421 4.2.1 : (RLY:SN) http://postmaster.info.aol.com/errors/421rlysn.html (in reply to end of DATA command) According to that URL on AOL's site, either my From or Reply-To is using an address in violation of DMARC. I had already checked the From address so it was apparent the Reply-To was at fault. Aalthough the mail was not being rejected, given AOL's hair-trigger sensors I figured it would be better to do it their way. Changing the Reply-To: to the list's address got rid of the 421 error. Has anyone else run into this? I hate doing this, since now we're going to see people sending what they think are private messages to the entire list. I see from the docs that Mailman can do different behavior on the From: address depending on whether it is in a DMARC-protected domain - are there any plans to do the same for the Reply-To? Looks to me like it will be necessary given what AOL is doing. Thanks, -- Ed -- 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] AOL screening Reply-To header thru DMARC ?
On Sat, Oct 18, 2014 at 11:03:11AM -0700, Mark Sapiro wrote: ... I have a somewhat different issue. I am using dmarc_moderation_action = Munge From, and when an AOL user posts to the list, the list message sent back to the user bounces with 521 5.2.1 : AOL will not accept delivery of this message. (in reply to end of DATA command)). The same messages sent to other AOL users are accepted by AOL. From your lips to AOL's ears! I'm seeing that too. A message from an AOL user was bounced when sent back to the original user, and AOL also bounced it going to the other AOL recipient on the test list. I think I'm going to have to set every AOL user to no metoo, and tell them if they want to see confirmation of their posts they need to turn ack on. I just tested it and there's no bouncing. But that's probably going to be a headache to maintain, so maybe I'll switch to wrapped messages. -- Ed -- 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
