Re: [Mailman-Users] AOL's Client TOS Notification
* Brad Knowles [EMAIL PROTECTED]: On 7/14/07, Zbigniew Szalbot wrote: Simple - yes. Effective? Depends on what you are after. By doing it this way you are not really different from AOL, are you? You punish many users just because some other are thoughtless and lazy. When I offer something, I want people to use it, not ban it. You're not punishing these other users -- AOL and the other clueless users are. If AOL didn't shoot first and ask questions later, then these problems wouldn't exist. What this system is lacking is a I dispute this-method. That way the reports by stupid users wouldn't be sent out by AOL. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBFsend no mail to [EMAIL PROTECTED] -- 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
Re: [Mailman-Users] AOL's Client TOS Notification
* Dave Dewey [EMAIL PROTECTED]: Do you use VERP to send out the mails? If you do that you can see who the culprit is. VERP doesn't work any longer for these, as of a couple months ago. Damn! My last TOS notification dates back quite some time... They now redact ALL information that can be used to identify the user, including verp'd addresses. Great. Messageid still works, for whatever reason it's the one piece of header info that isn't redacted at this point. OK, so VERP is still the way to go, since the message-id is always different -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBFsend no mail to [EMAIL PROTECTED] -- 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
Re: [Mailman-Users] Messages not being delivered.
Brandon Slaten wrote: I just moved our Mailman lists to a new server. Accessing the listinfo and admin pages works fine. After creating a new list mail sent to that list is delivered. However mail set to the old lists, the ones that were moved to this server, is not delivered. What happens to mail to the old lists (after delivery to Mailman - see below)? See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.078.htp. I do however get moderation and bounce notices from those lists. I ran check_perms to see if there were any problems with permissions and got the following: file permissions must be at least 660: /var/lib/mailman/lists/ofap_mgrs/config.db (fixing) file permissions must be at least 660: /var/lib/mailman/lists/ofap_mgrs/config.db.last (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/config.db (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/config.db.last (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/next-digest (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/next-digest-topics (fixing) The log entry below (delivered to command: /usr/lib/mailman/mail/mailman post listname) says you are running Mailman 2.1.x. These residual 2.0.x files were converted to config.pck and digest.mbox files when the installation was upgraded to 2.1. They should now be deleted (assuming they are old and there are current config.pck* files. I also have this from the logs. Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: from=[EMAIL PROTECTED], size=629, nrcpt=1 (queue active) Jul 14 14:25:36 chandon postfix/smtpd[9619]: disconnect from host2.atd.ucar.edu[128.117.80.16] Jul 14 14:25:36 chandon postfix/local[9833]: C13DF3793B: to=[EMAIL PROTECTED], relay=local, delay=0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post listname) Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: removed Assuming 'listname' above is one of the affected lists, the message is being delivered to Mailman so the Postfix Aliases are OK. Refer to the FAQ above (items 6-8 in particular) for other things which might be wrong. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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
Re: [Mailman-Users] Messages not being delivered.
Some additional information: The old server: Using Mailman version: 2.1.6 Compiled from src. SunOS 5.8 Generic_117350-14 sun4u sparc SUNW,Ultra-4 The new server: Using Mailman version: 2.1.5 Installed from mailman-2.1.5.1-34.rhel4.5 Linux 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:59:08 EDT 2007 i686 i686 i386 GNU/Linux Since it looks like the mail server is handing off to the mailman script, I have been looking for some sort of log or error messages in the various system logs, with out luck so far. Brandon Slaten wrote: Greetings, Thanks for any time you can give this problem. I just moved our Mailman lists to a new server. Accessing the listinfo and admin pages works fine. After creating a new list mail sent to that list is delivered. However mail set to the old lists, the ones that were moved to this server, is not delivered. I do however get moderation and bounce notices from those lists. I ran check_perms to see if there were any problems with permissions and got the following: file permissions must be at least 660: /var/lib/mailman/lists/ofap_mgrs/config.db (fixing) file permissions must be at least 660: /var/lib/mailman/lists/ofap_mgrs/config.db.last (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/config.db (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/config.db.last (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/next-digest (fixing) file permissions must be at least 660: /var/lib/mailman/lists/python/next-digest-topics (fixing) A second run showed no errors yet still not message being delivered when sent to the older lists. I also have this from the logs. Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: from=[EMAIL PROTECTED], size=629, nrcpt=1 (queue active) Jul 14 14:25:36 chandon postfix/smtpd[9619]: disconnect from host2.atd.ucar.edu[128.117.80.16] Jul 14 14:25:36 chandon postfix/local[9833]: C13DF3793B: to=[EMAIL PROTECTED], relay=local, delay=0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman post listname) Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: removed -- 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/brandon%40ucar.edu Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- 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
Re: [Mailman-Users] Messages not being delivered.
Brandon Slaten wrote: Mark Sapiro wrote: Brandon Slaten wrote: ~mailman - /usr/lib/mailman There is no lock, qfiles, or log directories there to look at to assess items 6-8 in the link above. In redhat 2.1.5, they may be in /var/mailman (see below) I did find the mentioned mailman logs in /var/logs/mailman Here is the most recent entry in the errors log. atd_systems_notes is one of the lists moved over from the old server and one I have been testing with. Jul 15 08:38:21 2007 (26407) No such list aa-optical: Jul 15 08:40:42 2007 (26482) No such list aa-hygro-growth: Jul 15 08:52:45 2007 (26737) No such list aa-phys-size: Jul 15 09:02:44 2007 (27140) No such list aa-satellite: Jul 15 09:09:19 2007 (4397) Uncaught runner exception: [Errno 13] Permission denied:'/var/lib/mailman/lists/atd_systems_notes/digest.mbox' Jul 15 09:09:19 2007 (4397) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 76, in process mboxfp = open(mboxfile, 'a+') IOError: [Errno 13] Permission denied: '/var/lib/mailman/lists/atd_systems_notes/digest.mbox' Jul 15 09:09:19 2007 (4397) SHUNTING: 1184512159.0603149+56cd041d3f9dcb1c15807c25c069d965 53d266da Jul 15 09:22:48 2007 (27873) No such list aa-model: Jul 15 09:31:34 2007 (28149) No such list esigupcoming: The permissions on the digest.mbox seems to be the issue, after changing it to be the same as the digest.mbox for the newly created list (660) all seems to be working. I am surprised that the check_perms script did not catch that. It's a recently discovered bug in check_perms fixed for 2.1.10. See http://mail.python.org/pipermail/mailman-users/2007-June/057487.html. You can now run bin/unshunt to reprocess the shunted messages, but first look at the files in qfiles/shunt to make sure there aren't unwanted stale messages there. You can use bin/dumpdb or bin/show_qfiles (although there is a bug in 2.1.5 show_qfiles that affects some entries, but probably not these) to look at the individual *.pck files in qfiles/shunt and can just remove unwanted ones before running bin/unshunt. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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
[Mailman-Users] Failures showing in the log file?
OK, something I notice in my posts log is a message not entirely unlike the following: Jul 15 09:27:31 2007 (32571) post to list from [EMAIL PROTECTED], size=5706, message-id=redacted, 557 failures Now, as time progresses, that failures number counts down, and ultimately, there is a success asociated with that number. sWhat, precisely, does this message mean? -Dennis Carr -- 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
[Mailman-Users] (no subject)
unsubscribe -- 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
Re: [Mailman-Users] AOL's Client TOS Notification
Quoting Christopher X. Candreva ([EMAIL PROTECTED]): On Sat, 14 Jul 2007, Dave Dewey wrote: Return-Path: [EMAIL PROTECTED] Wow, maybe I'm just lucky. Is your server on the AOL whitelist ? Yep. I get very few complaints, 99% of them accidental, so for me it's just a way to contact my subscribers and tell them to stay away from that damn spam button. -- 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
Re: [Mailman-Users] Failures showing in the log file?
Dennis Carr wrote: OK, something I notice in my posts log is a message not entirely unlike the following: Jul 15 09:27:31 2007 (32571) post to list from [EMAIL PROTECTED], size=5706, message-id=redacted, 557 failures Now, as time progresses, that failures number counts down, and ultimately, there is a success asociated with that number. sWhat, precisely, does this message mean? Look in the smtp-failure log for a more informative message including a reason. What is happening is the outgoing SMTP server (MTA) is accepting only a fraction of the recipients. The rest are queued for retry. Some more recipients are accepted on the retry, and the rest are queued, and so on. It may or may not help to set SMTP_MAX_RCPTS to a number smaller that the number that gets accepted each time (in mm_cfg.py), but first get the reason from the smtp-failure log. The best solution depends on the reason. It may be that something in the outgoing MTA needs to be changed. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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
Re: [Mailman-Users] Messages not being delivered.
Mark Sapiro wrote: Brandon Slaten wrote: Mark Sapiro wrote: Brandon Slaten wrote: ~mailman - /usr/lib/mailman There is no lock, qfiles, or log directories there to look at to assess items 6-8 in the link above. In redhat 2.1.5, they may be in /var/mailman But OTOH, the fact that the lists are in /var/lib/mailman/lists/* and The python Modules are in /usr/lib/mailman/Mailman says that this is RedHat's FHS compliant scheme. There should be an INSTALL.REDHAT document somewhere in your installation that tells you how to map various old RedHat locations (mostly /var/mailman/*) into the FHS locations. If you can't find this document, the mapping is in the online version at http://cvs.fedora.redhat.com/viewcvs/*checkout*/rpms/mailman/F-7/mailman.INSTALL.REDHAT.in and also in a post at http://mail.python.org/pipermail/mailman-developers/2004-October/017343.html. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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
Re: [Mailman-Users] AOL's Client TOS Notification
Ralf Hildebrandt wrote: OK, so VERP is still the way to go, since the message-id is always different Do you mean the SMTP id in the first Received: (from Mailman) header? You can get the recipient from your MTA log using this, but the Message-ID: header is normally unchanged from the incoming post and is not different for different recipients. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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
