[Mailman-Users] Question about rejection messages.
I am the site admin of a server that hosts a bunch of Mailman lists and on the 1st of the month Mailman sends out its monthly reminder messages. Some of these messages are bouncing. Some are *obviously* for people who have changed E-Mail providers (the bunces say 'User Unknown' or 'Mailbox full'). But some have 'odd' rejection reasons and I wonder what it really going on. Comcast is bouncing with the message: reason: 554 Transaction Failed Spam Message not queued. Is this Comcast's way of 'hiding' the fact that the E-Mail address is no longer valid? That is, does Comcast consider E-Mail to unknown users spam? -- Robert Heller -- 978-544-6933 / hel...@deepsoft.com Deepwoods Software-- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments -- 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] Installing v3.0.0b4 on Debian 7
Thanks, I used now pip install to install the zope interface and it worked, I had the debian package's version installed and that did not work well along. On Monday, June 30, 2014 4:20 PM, Mark Sapiro m...@msapiro.net wrote: On 06/29/2014 01:35 PM, ML mail wrote: Hi, I am trying to install version 3.0.0b4 of Mailman on Debian 7 and for that purpose I took the original tar.gz file and ran: sudo python setup.py install There was an issue with the version of zope.interface which I resolved by running the following command: sudo pip install -U zope.interface Now Mailman got correctly installed but when doesn't seem to run. This is the output when I run the mailman command on its own: I saw a similar issue at one point. I *think* I fixed it by completely removing zope.interface and rerunning python setup.py install, letting it install the zope.interface package it wanted. That said, I'm not really working on MM 3 at this point and most of the MM 3 folks are better found on mailman-develop...@python.org. -- Mark Sapiro m...@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better 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/mlnospam%40yahoo.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
[Mailman-Users] Mailman v3 how to create new user
Hi, I installed Mailman 3 and Postorius all working fine so far but I have a question regarding user management. I got one admin user created while running the syncdb command in Django, but how do I now create additional users? Ideally I would like one domain admin user who can manage mailing lists for a specific domain, is this possible? Regards, ML -- 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] Question about rejection messages.
Robert Heller writes: Comcast is bouncing with the message: reason: 554 Transaction Failed Spam Message not queued. Is this Comcast's way of 'hiding' the fact that the E-Mail address is no longer valid? That is, does Comcast consider E-Mail to unknown users spam? How would anybody except a Comcast postmaster know? If they're doing something that antisocial, would they admit it publicly? To diagnose, I suggest investigating questions like the following: - Are other Comcast addresses being accepted for delivery? - Is it concentrated on a particular list (vs. there is a subset of addresses being bounced that way for all lists)? - Are any of them members you recognize as being recently active? - Are any Comcast addresses bouncing as non-existent? (Note that RFC 5321 itself gives no valid recipients as a reason for a 554 status return, vs. 550, which is a generic I can't/won't do that status.) If you have strong evidence that it's true (the answers are yes, no, no, and no), my suggestion is to post to your lists explaining the situation and your conclusion that such failures mean a non-existent subscriber, and that to protect your lists from being put on a Comcast known spammer list, you are disabling/unsubscribing all such addresses immediately. Direct those suffering from collateral damage to talk to their ISP about mending its evil ways (after reinstating them, of course). -- 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] We're sorry, we hit a bug!
L.S. Bug in Mailman version 2.1.15 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. The above message shows up on the web pages, unfortunately the last log written to is qrunner, error is empty, so no info on what it is about. The last thing changed is the adres of the main pages. It looks like the mail-system is not affected, any idea what is going on? Would like to show some logging, but it simply is not there. -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? Why be difficult, when with a bit of effort, you can be impossible? -- 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] We're sorry, we hit a bug!
On 07/01/2014 07:08 AM, Roel Wagenaar wrote: L.S. Bug in Mailman version 2.1.15 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in theMailman error logs. The above message shows up on the web pages, unfortunately the last log written to is qrunner, error is empty, so no info on what it is about. The above message indicates the traceback was written to some 'error' log, just not the one you're looking at. You can always edit (temporarily) Mailman's scripts/driver and at line 33 change STEALTH_MODE = 1 to STEALTH_MODE = 0 and that will allow the traceback and other diagnostic info to be displayed instead of the We're sorry, we hit a bug! message. Would like to show some logging, but it simply is not there. It was successfully written to an 'error' log somewhere or the We're sorry, we hit a bug! message would say: Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. -- 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] We're sorry, we hit a bug!
Mark Sapiro m...@msapiro.net wrote: The above message indicates the traceback was written to some 'error' log, just not the one you're looking at. You can always edit (temporarily) Mailman's scripts/driver and at line 33 change STEALTH_MODE = 1 to STEALTH_MODE = 0 and that will allow the traceback and other diagnostic info to be displayed instead of the We're sorry, we hit a bug! message. Would like to show some logging, but it simply is not there. It was successfully written to an 'error' log somewhere or the We're sorry, we hit a bug! message would say: Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. Thanks Mark, the page is showing that the log location was not writeable, must be the bug. Resetting the LOG_DIR to default saved me. Apologies for the noise. -- Roel Wagenaar, Linux-User #469851 with the Linux Counter; http://linuxcounter.net/ Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen. Vraag: Waarom is top-posting een slechte gewoonte? Antw.: Top-posting. Vraag: Wat is het meest ergerlijke in e-mail? Ignorence is when you don't know anything and somebody finds out. -- 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] Question about rejection messages.
On 7/1/2014 6:50 AM, Robert Heller wrote: I am the site admin of a server that hosts a bunch of Mailman lists and on the 1st of the month Mailman sends out its monthly reminder messages. Some of these messages are bouncing. Some are *obviously* for people who have changed E-Mail providers (the bunces say 'User Unknown' or 'Mailbox full'). But some have 'odd' rejection reasons and I wonder what it really going on. Comcast is bouncing with the message: reason: 554 Transaction Failed Spam Message not queued. Is this Comcast's way of 'hiding' the fact that the E-Mail address is no longer valid? That is, does Comcast consider E-Mail to unknown users spam? My interpretation of the message is this - Comcast, for some unstated reason, thinks that this mail is spam, so it is not going to accept the message. Without seeing the exact mail that was being sent, I cannot tell what Comcast might have thought objectionable. --Barry Finkel -- 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] Question about rejection messages.
On Jul 1, 2014, at 11:42 AM, Barry S. Finkel bsfin...@att.net wrote: On 7/1/2014 6:50 AM, Robert Heller wrote: I am the site admin of a server that hosts a bunch of Mailman lists and on the 1st of the month Mailman sends out its monthly reminder messages. Some of these messages are bouncing. Some are *obviously* for people who have changed E-Mail providers (the bunces say 'User Unknown' or 'Mailbox full'). But some have 'odd' rejection reasons and I wonder what it really going on. Comcast is bouncing with the message: reason: 554 Transaction Failed Spam Message not queued. Is this Comcast's way of 'hiding' the fact that the E-Mail address is no longer valid? That is, does Comcast consider E-Mail to unknown users spam? Comcast* will reject all list mail from a Yahoo or AOL member post based on those ISP’s DMARC p=reject policy. In other words, they honor the p=reject. Could this be your issue? best regards, Larry *So will many other ISPs: SBC Global, ATT, Rogers, Earthlink, etc. -- Larry Finch finc...@portadmiral.org -- 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] Question about rejection messages.
At Tue, 01 Jul 2014 10:42:13 -0500 Barry S. Finkel bsfin...@att.net wrote: On 7/1/2014 6:50 AM, Robert Heller wrote: I am the site admin of a server that hosts a bunch of Mailman lists and on the 1st of the month Mailman sends out its monthly reminder messages. Some of these messages are bouncing. Some are *obviously* for people who have changed E-Mail providers (the bunces say 'User Unknown' or 'Mailbox full'). But some have 'odd' rejection reasons and I wonder what it really going on. Comcast is bouncing with the message: reason: 554 Transaction Failed Spam Message not queued. Is this Comcast's way of 'hiding' the fact that the E-Mail address is no longer valid? That is, does Comcast consider E-Mail to unknown users spam? My interpretation of the message is this - Comcast, for some unstated reason, thinks that this mail is spam, so it is not going to accept the message. Without seeing the exact mail that was being sent, I cannot tell what Comcast might have thought objectionable. It was the monthly Mailman reminder message. --Barry Finkel -- 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/heller%40deepsoft.com -- Robert Heller -- 978-544-6933 / hel...@deepsoft.com Deepwoods Software-- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments -- 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] Question about rejection messages.
At Tue, 1 Jul 2014 12:16:44 -0400 Larry Finch finc...@portadmiral.org wrote: On Jul 1, 2014, at 11:42 AM, Barry S. Finkel bsfin...@att.net wrote: On 7/1/2014 6:50 AM, Robert Heller wrote: I am the site admin of a server that hosts a bunch of Mailman lists and on the 1st of the month Mailman sends out its monthly reminder messages. Some of these messages are bouncing. Some are *obviously* for people who have changed E-Mail providers (the bunces say 'User Unknown' or 'Mailbox full'). But some have 'odd' rejection reasons and I wonder what it really going on. Comcast is bouncing with the message: reason: 554 Transaction Failed Spam Message not queued. Is this Comcast's way of 'hiding' the fact that the E-Mail address is no longer valid? That is, does Comcast consider E-Mail to unknown users spam? Comcast* will reject all list mail from a Yahoo or AOL member post based on those ISP´s DMARC p=reject policy. In other words, they honor the p=reject. Could this be your issue? No. As I stated above, it was a Mailman monthly reminder message. best regards, Larry *So will many other ISPs: SBC Global, ATT, Rogers, Earthlink, etc. -- Larry Finch finc...@portadmiral.org -- 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/heller%40deepsoft.com -- Robert Heller -- 978-544-6933 / hel...@deepsoft.com Deepwoods Software-- http://www.deepsoft.com/ () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments -- 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] Question about rejection messages.
Do you know if any of the reminders to Comcast addresses are getting through? Peter Shute -Original Message- From: Mailman-Users [mailto:mailman-users-bounces+pshute=nuw.org...@python.org] On Behalf Of Robert Heller Sent: Tuesday, 1 July 2014 9:50 PM To: Mailman Users Subject: [Mailman-Users] Question about rejection messages. I am the site admin of a server that hosts a bunch of Mailman lists and on the 1st of the month Mailman sends out its monthly reminder messages. Some of these messages are bouncing. Some are *obviously* for people who have changed E-Mail providers (the bunces say 'User Unknown' or 'Mailbox full'). But some have 'odd' rejection reasons and I wonder what it really going on. Comcast is bouncing with the message: reason: 554 Transaction Failed Spam Message not queued. Is this Comcast's way of 'hiding' the fact that the E-Mail address is no longer valid? That is, does Comcast consider E-Mail to unknown users spam? -- 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] Question about rejection messages.
On 07/01/2014 03:07 PM, Peter Shute wrote: Do you know if any of the reminders to Comcast addresses are getting through? At 05:00 local time this morning my Mailman installation sent password reminders to 65 comcast.net addresses. Of these, exactly 1 bounced with 550 5.1.1 u...@comcast.net Account not available (in reply to RCPT TO command) and this was for a known bad address that's been bouncing password reminders for at least two months prior to today. -- 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] Question about rejection messages.
Mark Sapiro writes: At 05:00 local time this morning my Mailman installation sent password reminders to 65 comcast.net addresses. Of these, exactly 1 bounced with 550 5.1.1 u...@comcast.net Account not available (in reply to RCPT TO command) OK, so we know Comcast will admit that a user doesn't exist. Is this a personalized list? Maybe Comcast does something different with a multiple recipient RCPT TO that contains multiple invalid users? Also, note that this message, presumably a quote from comcast.net up to the open paren, includes an extended status code whereas the OP's error did not. I wonder if his MTA was actually talking to comcast.net? Maybe somebody gave him a comcast.com address by mistake or something like that? -- 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] Question about rejection messages.
On 07/01/2014 07:12 PM, Stephen J. Turnbull wrote: Mark Sapiro writes: At 05:00 local time this morning my Mailman installation sent password reminders to 65 comcast.net addresses. Of these, exactly 1 bounced with 550 5.1.1 u...@comcast.net Account not available (in reply to RCPT TO command) OK, so we know Comcast will admit that a user doesn't exist. Is this a personalized list? Maybe Comcast does something different with a multiple recipient RCPT TO that contains multiple invalid users? These and the OP's were all password reminders which are all 'personalized' and sent to a single RCPT TO Also, note that this message, presumably a quote from comcast.net up to the open paren, includes an extended status code whereas the OP's error did not. I wonder if his MTA was actually talking to comcast.net? Maybe somebody gave him a comcast.com address by mistake or something like that? Good observation. -- 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
