[Mailman-Users] Please help, big problem with members being automatically unsubscribed
Hi, I'm trying to figure out what is happening that my lists are having significant numbers of users unsubscribed automatically, even though I turned off bounce processing. It seems that the members being removed indeed have a number of bounces, but if I turned off bounce processing how could this be happening? Thanks for any suggestions Ricardo -- 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] configuration glitch causing mail delivery fail (FIXED)
On 1/7/2014 4:40 PM, Mark Sapiro wrote: On 01/07/2014 03:18 PM, Steve Lindemann wrote: Unfortunately when mailman sends messages they fail to deliver to most of the list subscribers and the maillog shows that the helo used is the actual name of the server, not the name of the email server. Naturally the receiving server disconnects when the names isn't right. How is Mailman delivering mail? If it is delivering to a local MTA on localhost, how it identifies itself in HELO to this MTA is irrelevant as it is this MTA, not Mailman that is attempting delivery to the recipient MX. I could understand this with the move to the new server except every where I know to configure this (both postfix and mailman) I have the name email.marmot.org configured as the URL of the host. Regular email works fine from that box, just mailman is having a problem sending. Does anyone have any idea what I'm missing? In the normal case, Mailman relays mail through the local MTA (Postfix). How Mailman identifies itself to this MTA is irrelevant as long as the MTA accepts the mail from Mailman (does it)? If the local postfix can deliver mail, but not Mailman's mail, the only thing I can see that would affect this is the envelope sender which would be LISTNAME-bounces@HOSTNAME where HOSTNAME is the list's host_name attribute. Damn... that was fun. It took two things to get it working again. I needed to rename the server to something with a mx record, in this case: email.marmot.org vrs what it was. AND I had to turn off ipv6 on the interfaces. Mailman and postfix are on the same box. Somehow the mailman messages where picking up the ipv6 localhost address as the source of the original message and it appears that being rejected by receiving servers. Once I renamed the server and ditched ipv6 the messages started delivering again. -- Steve -- 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] Please help, big problem with members being automatically unsubscribed
On 01/08/2014 01:48 PM, Ricardo Kleemann wrote: It seems that the members being removed indeed have a number of bounces, but if I turned off bounce processing how could this be happening? Turning off bounce processing will prevent new bounces from being processed and disabling delivery, but members whose delivery is already disabled by bounce will still be sent their warnings and ultimately be unsubscribed by cron/disabled. See the script at http://www.msapiro.net/scripts/reset_bounce.py for a way to reenable delivery for all disabled by bounce members. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] configuration glitch causing mail delivery fail (FIXED)
On 01/08/2014 01:43 PM, Steve Lindemann wrote: Somehow the mailman messages where picking up the ipv6 localhost address as the source of the original message ... Probably because the /etc/hosts entry for 'localhost' is the ipv6 address. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] User's emails being rejected for content type not explicitly allowed
I've got one user whose emails always get bounced back with the message The message's content type was not explicitly allowed'. There are no attachments or images in the rejected emails that I can see. Where do I start looking to find out what it's objecting to? Note that we've just moved this list to a new list server, so it's likely to be something we've set wrongly on the new server. There's a dkim-signature header in it. Could that be doing it? I'm not an admin, so I don't have access to any of the list settings. What settings should I ask the admin for to help diagnose it? Peter Shute Sent from my iPad -- 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] User's emails being rejected for content type not explicitly allowed
I was looking at the message attached to the user's rejection email, but now that I look at the one attached to the moderator alert email, I can see that there's an html signature that appears to have been treated as a separate attachment of content-type application/unknown. What's the best way to deal with those? Peter Shute From: Mailman-Users [mailman-users-bounces+pshute=nuw.org...@python.org] On Behalf Of Peter Shute [psh...@nuw.org.au] Sent: Thursday, 9 January 2014 3:42 PM To: mailman-users@python.org Subject: [Mailman-Users] User's emails being rejected for content type not explicitly allowed I've got one user whose emails always get bounced back with the message The message's content type was not explicitly allowed'. There are no attachments or images in the rejected emails that I can see. Where do I start looking to find out what it's objecting to? Note that we've just moved this list to a new list server, so it's likely to be something we've set wrongly on the new server. There's a dkim-signature header in it. Could that be doing it? I'm not an admin, so I don't have access to any of the list settings. What settings should I ask the admin for to help diagnose it? Peter Shute Sent from my iPad -- 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/pshute%40nuw.org.au -- 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] User's emails being rejected for content type not explicitly allowed
On 01/08/2014 09:13 PM, Peter Shute wrote: I was looking at the message attached to the user's rejection email, but now that I look at the one attached to the moderator alert email, I can see that there's an html signature that appears to have been treated as a separate attachment of content-type application/unknown. What's the best way to deal with those? That's not it. Look at the list's content filtering options. What is happening is that pass_mime_types is not empty and does not contain the content-type of the message and filter_action is reject. This most often happens when the content-type is text/html and that is not allowed, but it can also happen for example it the message's content-type is say multipart/related, and pass_mime_types contains multipart/mixed and multipart/alternative but not multipart and not multipart/related. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Newsletter Blast sending duplicates to subscribers
Hi, We've been using mailman for quite a long time now, and suddenly the last newsletter we sent out sent duplicates to random users as far as I can tell. All the people that have e-mailed us about this issue were specifically yahoo addresses. Reports of 4-50 duplicates per user were sent to them. We only have one list of users we send users to, and this is the first time this has ever happened. I have a few accounts added to the list myself, and my aol account did not recieve the email at all. Previously the aol account received the messages, I had a couple of the newsletters in my account still unread. So, my question specifically... does anybody have advice in what I should look for as to why this happened? I read a post from 2002 that was somewhat similar to this issue, but it had to do with not haveing enough memory... and currently my server has 53gigs free, so that couldn't be the issue... unless of course you have to 'allocate' memory to mailman in some config file. We have about 12k users on our list. Thank you in advance, and let me know if I lacked some details to help solve my issue. Thanks, Doug -- 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] Quick mailman configuration question...
I have been poking around and trying to see if I can configure mailman to not include the list in the email being sent? The idea is we are going to be sending a newsletter and want to prevent users from accidentally reply-all to the entire the group. Instead we want it to only go back to the original poster. Make sense? Thanks in advance! -Scott. -- 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] Quick mailman configuration question...
On 01/08/2014 08:58 AM, Scott Chapman wrote: The idea is we are going to be sending a newsletter and want to prevent users from accidentally reply-all to the entire the group. Instead we want it to only go back to the original poster. Mailman is designed primarily to support discussion lists and as such takes great pains to ensure that 'reply all' includes the list. See the FAQ at http://wiki.list.org/x/3YA9 for our recommendations on setting up a newsletter type list that subscribers can't post to. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Newsletter Blast sending duplicates to subscribers
On 01/08/2014 08:03 AM, Doug Hutson wrote: So, my question specifically... does anybody have advice in what I should look for as to why this happened? Look at the logs from your outgoing MTA. These should show all the interactions with Yahoo and at least give you clues. For the missing AOL mail, see the FAQ at http://wiki.list.org/x/4oA9. Also look at Mailman's 'smtp' and smtp-failure' logs. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Newsletter Blast sending duplicates to subscribers
On Jan 8, 2014, at 6:03 AM, Doug Hutson d...@mrdirectint.com wrote: We've been using mailman for quite a long time now, and suddenly the last newsletter we sent out sent duplicates to random users as far as I can tell. All the people that have e-mailed us about this issue were specifically yahoo addresses. Reports of 4-50 duplicates per user were sent to them. We only have one list of users we send users to, and this is the first time this has ever happened. So, my question specifically... does anybody have advice in what I should look for as to why this happened? I would start with looking at the logs of your mail server. You want to figure out where the duplication is occurring. Was it sent to Yahoo more than once? Or was it accepted by Yahoo just once? If the latter, the duplication is happening at Yahoo and it is not your problem to solve. You didn’t say what mail server is being used but SMTP is designed not to lose mail. Therefore, a duplicate is preferable to losing mail. If the receiving SMTP server receives the mail but does not tell the sending server it has it (sending server sends “end of message” but receiving server does not acknowledge), then the sending server assumes something went wrong and tries to send it again. My guess would be it’s either happening between your outgoing SMTP server and Yahoo (or the next server if you’re relaying through another server) or internally in Yahoo. It’s very unlikely, particularly since you say it only happens with Yahoo, that it’s a problem in Mailman. Rather, it’s happening after Mailman is done with the message so is not a Mailman problem per se. -- Larry Stone lston...@stonejongleux.com http://www.stonejongleux.com/ -- 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] Newsletter Blast sending duplicates to subscribers
On 1/8/14, 10:03 AM, Doug Hutson wrote: All the people that have e-mailed us about this issue were specifically yahoo addresses. Reports of 4-50 duplicates per user were sent to them. We only have one list of users we send users to, and this is the first time this has ever happened. The few times that I ran in to this type of problem in the past were not Mailman issues at all. Rather they were symptoms of underlying SMTP issues. My clue when I fought this battle before was that the messages IDs down stream of my server(s) were different in each copy of the message. When investigating in my SMTP logs, I found that the delivery attempts were failing in some manner and my SMTP server was considering the delivery a failure and would retry until it saw the expected response. However, the receiving server did considered the delivery to be successful, and as such treated the message(s) as valid. Ultimately, causing duplicated messages. When investigating the SMTP issue, I found that the problem was related to network connectivity issues, specifically saturated connection on the receiving end. - Once I addressed (worked around) the connectivity issues, the duplicate messages cleared up immediately. -- Grant. . . . unix || die -- 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
