[Mailman-Users] List blocking due to bounces
Is there a possibility that a whole lists get blocked for a certain number of bounces recievied? Or any other way? Generally, what are the ways of automatic list blocking? We're on cpanel and yet cant get it working properly. -- 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] List blocking due to bounces
At 10:45 AM +0400 2005-10-18, =?Windows-1251?B?yu7i4Ovl7eruIMji4O0=?= wrote: Is there a possibility that a whole lists get blocked for a certain number of bounces recievied? Or any other way? Number of bounces? I don't think so, at least not with the standard Mailman code. Generally, what are the ways of automatic list blocking? The versions of Mailman prior to 2.1.6 could get into some problems where messages that are illegally formatted could wind up blocking an entire list. Mailman would try to process the messages, be unable to do so, and then fail to proceed to the next message for that list. Version 2.1.6 significantly increased the probability that such problems would not block an entire list, but of course there's always a chance that something really strange could happen. We're on cpanel and yet cant get it working properly. CPanel may have added some code to Mailman to block lists that are causing excessive bounces, and if that feature is available, your supplier may have enabled it for your list. Unfortunately, the Mailman FAQ Wizard is down right now, otherwise I would point you at the FAQ entry which addresses the issue of the changes that CPanel has made to the code, etc However, you can see the Google cache version of the page at http://66.249.93.104/search?q=cache:y4M8jCXL-L8J:www.python.org/cgi-bin/faqw-mm.py%3Freq%3Dshow%26file%3Dfaq06.011.htp+hl=en, or http://tinyurl.com/at7h2. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] Migrating Lists to a new server
That was exactly what I was looking for. Thanks. On Oct 17, 2005, at 2:34 PM, Carl Zwanzig wrote: In a flurry of recycled electrons, Dennis Putnam wrote: Can someone point me to some documentation for migrating mailman lists and archives to a new server? Thanks. Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py While the search engine appears to be out of service, the index isn't. Searchable Archives: http://www.mail-archive.com/mailman-users% 40python.org/ Start with http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.004.htp z! Dennis Putnam Sr. IT Systems Administrator AIM Systems, Inc. 11675 Rainwater Dr., Suite 200 Alpharetta, GA 30004 Phone: 678-240-4112 Main Phone: 678-297-0700 FAX: 678-297-2666 or 770-576-1000 The information contained in this e-mail and any attachments is strictly confidential. If you are not the intended recipient, any use, dissemination, distribution, or duplication of any part of this e-mail or any attachment is prohibited. If you are not the intended recipient, please notify the sender by return e-mail and delete all copies, including the attachments. -- 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] Strange errors
Mark Sapiro wrote: Dan Szkola wrote: I am running a Solaris 10 box, with mailman-2.1.6rc4 and sendmail version 8.13.3. Python version is 2.4.1. I run sendmail in the following ways: A normal sendmail daemon listening on port 25: /usr/lib/sendmail -bd -q15m A persistent queue runner: /usr/lib/sendmail -qp1m -OPidFile=/var/run/sendmail-qrun.pid A sendmail with submit.cf config: /usr/lib/sendmail -Ac -q5m A sendmail for smtp-auth listening on port 587: /usr/lib/sendmail -bd -C/etc/mail/sendmail-auth.cf -q15m Anyway, the problem we are having is this: After running for several days with no errors, we suddenly start seeing this error: Mail Delivery Subsystem [EMAIL PROTECTED] 10/17/2005 9:18:52 AM The original message was received at Mon, 17 Oct 2005 09:18:21 -0500 (CDT) from .xxx.xxx.xxx [131.156.xxx.xxx] - The following addresses had permanent fatal errors - |/usr/local/mailman/mail/mailman post testlist (reason: 1) (expanded from: [EMAIL PROTECTED]) - Transcript of session follows - Traceback (most recent call last): File /usr/local/mailman/scripts/post, line 35, in ? from Mailman.Queue.sbcache import get_switchboard File /usr/local/mailman/Mailman/Queue/sbcache.py, line 19, in ? from Mailman.Queue.Switchboard import Switchboard File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 47, in ? from Mailman.Logging.Syslog import syslog File /usr/local/mailman/Mailman/Logging/Syslog.py, line 22, in ? from Mailman.Logging.StampedLogger import StampedLogger File /usr/local/mailman/Mailman/Logging/StampedLogger.py, line 20, in ? from Mailman.Logging.Logger import Logger File /usr/local/mailman/Mailman/Logging/Logger.py, line 25, in ? from Mailman.Logging.Utils import _logexc File /usr/local/mailman/Mailman/Logging/Utils.py, line 18, in ? import traceback ImportError: No module named traceback 554 5.3.0 unknown mailer error 1 Has anyone seen this? Should I file a bug on this or send it along to the developers list? Restarting sendmail seems to get rid of the problem for a day or two. All sendmail configs have the mailman alias file included and we run newaliases to update it on every new list creation. This is curious indeed for at least two reasons. It is not a sendmail alias problem, nor does it seem on the face to be a sendmail problem at all. The post is received by sendmail and piped to the wrapper with the appropriate arguments. The wrapper invokes the post script as it should. The post script then does some imports one of which is from Mailman.Queue.sbcache import get_switchboard sbcache does from Mailman.Queue.Switchboard import Switchboard and so on until Mailman.Logging.Utils does import traceback which results in ImportError: No module named traceback Now this is really strange because traceback is a Python library module and this chain of imports leading to 'import traceback' occurs with every post, so why does it fail now and why does restarting sendmail fix it? I built Python from source on a Solaris 10 box. Could it be a problem with the way it was built? I'm doubting it, but I don't use python all that often. What happens if you restart Mailman (bin/mailmanctl restart) without restarting sendmail? Does that fix it? Or do all the qrunners die with the same ImportError? I was just notified by our helpdesk that it is failing again. I will restart only mailman and see if that fixes the issue. I have no reason other than superstition for the following suggestion, but try SMTP_MAX_SESSIONS_PER_CONNECTION = 1 in mm_cfg.py and see if that helps. This will cause Mailman to close the SMTP connection to sendmail after each transaction. This might avoid the problem, but since I have no idea what the problem is, I have no idea if this will help. I'll try that after a while as well. Is there somewhere I can enable more debugging to help get to the bottom of this issue? I'm finding next to nothing in the logs that is helpful. -- Dan Szkola Sr Unix Systems Programmer Northern Illinois University -- 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] Strange errors
At 8:37 AM -0500 2005-10-18, Dan Szkola wrote: Is there somewhere I can enable more debugging to help get to the bottom of this issue? I'm finding next to nothing in the logs that is helpful. There is no additional debugging that can be enabled. Assuming you're looking in the right places, you're already seeing everything that is available. You can always put in additional code to create additional debugging that you may find useful, but that's about it. If you decide to go this route, you will need to be careful about indentation and other aspects of the Python programming language, otherwise you're likely to cause more damage than you're trying to cure. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- 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] Strange errors
Mark Sapiro wrote: Dan Szkola wrote: I am running a Solaris 10 box, with mailman-2.1.6rc4 and sendmail version 8.13.3. Python version is 2.4.1. I run sendmail in the following ways: A normal sendmail daemon listening on port 25: /usr/lib/sendmail -bd -q15m A persistent queue runner: /usr/lib/sendmail -qp1m -OPidFile=/var/run/sendmail-qrun.pid A sendmail with submit.cf config: /usr/lib/sendmail -Ac -q5m A sendmail for smtp-auth listening on port 587: /usr/lib/sendmail -bd -C/etc/mail/sendmail-auth.cf -q15m Anyway, the problem we are having is this: After running for several days with no errors, we suddenly start seeing this error: Mail Delivery Subsystem [EMAIL PROTECTED] 10/17/2005 9:18:52 AM The original message was received at Mon, 17 Oct 2005 09:18:21 -0500 (CDT) from .xxx.xxx.xxx [131.156.xxx.xxx] - The following addresses had permanent fatal errors - |/usr/local/mailman/mail/mailman post testlist (reason: 1) (expanded from: [EMAIL PROTECTED]) - Transcript of session follows - Traceback (most recent call last): File /usr/local/mailman/scripts/post, line 35, in ? from Mailman.Queue.sbcache import get_switchboard File /usr/local/mailman/Mailman/Queue/sbcache.py, line 19, in ? from Mailman.Queue.Switchboard import Switchboard File /usr/local/mailman/Mailman/Queue/Switchboard.py, line 47, in ? from Mailman.Logging.Syslog import syslog File /usr/local/mailman/Mailman/Logging/Syslog.py, line 22, in ? from Mailman.Logging.StampedLogger import StampedLogger File /usr/local/mailman/Mailman/Logging/StampedLogger.py, line 20, in ? from Mailman.Logging.Logger import Logger File /usr/local/mailman/Mailman/Logging/Logger.py, line 25, in ? from Mailman.Logging.Utils import _logexc File /usr/local/mailman/Mailman/Logging/Utils.py, line 18, in ? import traceback ImportError: No module named traceback 554 5.3.0 unknown mailer error 1 Has anyone seen this? Should I file a bug on this or send it along to the developers list? Restarting sendmail seems to get rid of the problem for a day or two. All sendmail configs have the mailman alias file included and we run newaliases to update it on every new list creation. This is curious indeed for at least two reasons. It is not a sendmail alias problem, nor does it seem on the face to be a sendmail problem at all. The post is received by sendmail and piped to the wrapper with the appropriate arguments. The wrapper invokes the post script as it should. The post script then does some imports one of which is from Mailman.Queue.sbcache import get_switchboard sbcache does from Mailman.Queue.Switchboard import Switchboard and so on until Mailman.Logging.Utils does import traceback which results in ImportError: No module named traceback Now this is really strange because traceback is a Python library module and this chain of imports leading to 'import traceback' occurs with every post, so why does it fail now and why does restarting sendmail fix it? What happens if you restart Mailman (bin/mailmanctl restart) without restarting sendmail? Does that fix it? Or do all the qrunners die with the same ImportError? I restarted only the mailman processes using bin/mailmanctl restart and post still generate the error above. I will put the line below into the mm_cfg.py file and restart sendmail and watch what happens. I have no reason other than superstition for the following suggestion, but try SMTP_MAX_SESSIONS_PER_CONNECTION = 1 in mm_cfg.py and see if that helps. This will cause Mailman to close the SMTP connection to sendmail after each transaction. This might avoid the problem, but since I have no idea what the problem is, I have no idea if this will help. -- Dan Szkola Sr Unix Systems Programmer Northern Illinois University -- 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] List blocking due to bounces
I am very program illiterate, but have a comment here. We recently started a mailing list using Mailman. Our initial small list test of this program was great. However, the actual list we now have, has nearly 600 members. We had horrid bounce problems and contacted our hosting provider as we could not make sense of these problems from our cPanel. Our hosting was on a shared server and we found out that there is a limit to the number of posts any given account could send per hour - 350 on this server. So, with just one or two posts, we exceeded the limit, got horrendous bounces and automatic suspended accounts. We are now on our own dedicated server and all seems to be working well other than an across the board very long time interval -average 45 to 55 minutes- for mail being sent to as list mail to members after it is sent. Private replies - Reply All - on replies to list mail are sent immediately with the post to the list also delayed. The archives receive posts quickly. So, check to see if you are exceeding a set limit as to the number of emails your account can send per hour. Cathy - Original Message - From: ? [EMAIL PROTECTED] To: Mailman-Users@python.org Sent: Tuesday, October 18, 2005 1:45 AM Subject: [Mailman-Users] List blocking due to bounces Is there a possibility that a whole lists get blocked for a certain number of bounces recievied? Or any other way? Generally, what are the ways of automatic list blocking? We're on cpanel and yet cant get it working properly. -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.12.2/137 - Release Date: 10/16/2005 -- 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] Munged addresses
Robert Morse wrote: I have a list running on our server that when you ask for the entire list the firse 25 or so listed are munged. Here's an example [EMAIL PROTECTED] hsustudent668-1768starif anl Is this on the http://www.example.com/mailman/roster/listname page or somewhere else? What do you see on http://www.example.com/mailman/admin/listname/members? What do you get in reply to an e-mail 'who' command? Is this 'stock' Mailman, or does this list use a custom MemberAdaptor? Are you using a modified roster.html template? You can see that there is an actual email address in there, which when searched on returns a valid address. I would like to get rid of these munged addresses, but when I check the box to unsubscribe them, I get a message back that says the subscriber is not listed. Some are much longer, some ae shorter. Any way I can get rid of these things? Based the fact that part of what's there looks like tel #'s, student/staff classification, ..., I'm guessing this list uses a custom LDAP, MySQL, etc. MemberAdaptor and something in this MemberAdaptor's getRegularMemberKeys(() and/or getDigestMemberKeys() methods is returning the garbled data. -- 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] Munged addresses
On 10/18/05 8:12 AM, Mark Sapiro [EMAIL PROTECTED] wrote: Robert Morse wrote: I have a list running on our server that when you ask for the entire list the firse 25 or so listed are munged. Here's an example [EMAIL PROTECTED] hsustudent668-1768starif anl Is this on the http://www.example.com/mailman/roster/listname page or somewhere else? I get a list of munged addresses which are not on the hidden. What do you see on http://www.example.com/mailman/admin/listname/members? I get the list of munged addresses. What do you get in reply to an e-mail 'who' command? Not sure how to do that. Is this 'stock' Mailman, or does this list use a custom MemberAdaptor? Stock as far as I know. Never heard of MemberAdaptor. It's a cpanel instal of Mailman. Are you using a modified roster.html template? No. You can see that there is an actual email address in there, which when searched on returns a valid address. I would like to get rid of these munged addresses, but when I check the box to unsubscribe them, I get a message back that says the subscriber is not listed. Some are much longer, some ae shorter. Any way I can get rid of these things? Based the fact that part of what's there looks like tel #'s, student/staff classification, ..., I'm guessing this list uses a custom LDAP, MySQL, etc. MemberAdaptor and something in this MemberAdaptor's getRegularMemberKeys(() and/or getDigestMemberKeys() methods is returning the garbled data. -- Bob Morse Morse Media http://www.morsemedia.net 707-444-9566 -- 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] Munged addresses
Robert Morse wrote: On 10/18/05 8:12 AM, Mark Sapiro [EMAIL PROTECTED] wrote: Robert Morse wrote: Is this 'stock' Mailman, or does this list use a custom MemberAdaptor? Stock as far as I know. Never heard of MemberAdaptor. It's a cpanel instal of Mailman. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp You can see that there is an actual email address in there, which when searched on returns a valid address. I would like to get rid of these munged addresses, but when I check the box to unsubscribe them, I get a message back that says the subscriber is not listed. Some are much longer, some ae shorter. Any way I can get rid of these things? I think I understand now. Apparently at one time someone attempted a mass subscribe from a file or list that contained more than just real names and e-mail addresses and you got a bunch of bad addresses subscribed. They appear first in the membership list because they begin with '#' or other characters that sort before 'a'. The actual e-mail address was ultimately subscribed and is a list member, but you still have these other bad member 'addresses'. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.013.htp -- 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] List blocking due to bounces
On Tuesday 18 October 2005 07:50 am, Cathy Slayman wrote: So, check to see if you are exceeding a set limit as to the number of emails your account can send per hour. I had a similar problem to Cathy's. If you can't find a problem in your Mailman setup, you should find out if there's a ceiling on the number of e-mails that you can send in an hour. That ceiling frequently also includes the number of times you use pop to download mail. You might also want to run a report on your IP address at dnsstuff.com to see if there are any problems with its configuration. A lot of mail servers will not accept mail if it comes from an IP address that does not return a correct rDNS, among other things. The DNSStuff report should flag anything about the IP address that could be considered an issue. Sincerely, Diana -- Registered Linux User #327485 WordStar Users Group Community: http://wordstar2.com/WordStar_Users WordStar Linux: http://wordstar2.com Mailing Lists: http://wordstar2.com/mailman/listinfo -- 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 address associated with nodename
Context: I'm BRAND new to configuring mail servers, so go easy! ;^) I'm running Mailman 2.1.6 on a Mac G4 running OS X 10.4.2 using the default Postfix and Python installations (versions 2.1.5 and 2.3.5, respectively). I've read the FAQ and everything else Google could find on the topic, but am still having the problem characterized by the error messages below: From $prefix/logs/post: Oct 18 11:41:08 2005 (92) post to fv-test from [EMAIL PROTECTED], size=1356, message-id=[EMAIL PROTECTED], 1 failures From $prefix/logs/smtp: Oct 18 11:41:08 2005 (92) [EMAIL PROTECTED] smtp to fv-test for 1 recips, completed in 2.918 seconds From $prefix/logs/smtp-failure: Oct 18 11:41:10 2005 (92) Low level smtp error: (7, 'No address associated with nodename'), msgid: [EMAIL PROTECTED] Oct 18 11:41:10 2005 (92) delivery to [EMAIL PROTECTED] failed with code -1: (7, 'No address associated with nodename') I don't see any errors in /var/logs/mail.log around that time. Here are some of my configs (note: I have experimented with lots of settings, but these are the ones that were in effect when the above errors occurred): From /etc/postifx/main.cf owner_request_special = no recipient_delimiter = + unknown_local_recipient_reject_code = 550 alias_maps=hash:/etc/postfix/aliases,hash:/Users/macadmin/Mailman/data/alias es default_process_limit = 150 qmqr_message_active_limit = 4 qmgr_message_recipient_limit = 4 disable_dns_lookups = yes mydomain = familyvoices.org myhostname = lists.familyvoices.org myorigin = $mydomain mydestination = $myhostname relayhost =[relay2.mail.twtelecom.net] mydomain_fallback = lists.familyvoices.org mynetworks_style = host smtpd_recipient_restrictions = permit_mynetworks reject_unauth_destination transport_maps = hash:/etc/postfix/transport From $prefix/Mailman/mm_cfg.py: MTA = Postfix DEFAULT_EMAIL_HOST = 'lists.familyvoices.org' DEFAULT_URL_HOST = 'lists.familyvoices.org' add_virtualhost(DEFAULT_URL_HOST,DEFAULT_EMAIL_HOST) DEFAULT_MAX_MESSAGE_SIZE = 64 # KB SMTPHOST = 'lists' Any help is appreciated! -Andrew PS: As an aside, is it typical for it to take nearly 3 seconds for Mailman to process one, puny message to a list with one, puny recipient? What's the gate on performance? Disk speed? CPU? Network connection? Our lists won't be large (the largest is around 200 members), but we will have about 40 of them. Will this overload my little Mac? - Andrew Hedges Technology Coordinator Family Voices, Inc. 2340 Alamo Ave SE, Suite 102 Albuquerque, NM 87106 505-872-4774 phone 505-872-4780 fax [EMAIL PROTECTED] http://www.familyvoices.org/ -- 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] No address associated with nodename
On Tue, 18 Oct 2005, Andrew Hedges wrote: Context: I'm BRAND new to configuring mail servers, so go easy! ;^) I'm running Mailman 2.1.6 on a Mac G4 running OS X 10.4.2 using the default Postfix and Python installations (versions 2.1.5 and 2.3.5, respectively). I'm one of the resident MacOS X experts here although this appears to be a DNS problem and nothing MacOS X or mailman specific. From $prefix/logs/smtp-failure: Oct 18 11:41:10 2005 (92) Low level smtp error: (7, 'No address associated with nodename'), msgid: [EMAIL PROTECTED] Oct 18 11:41:10 2005 (92) delivery to [EMAIL PROTECTED] failed with code -1: (7, 'No address associated with nodename') A cryptic message to be sure but I think it's trying to tell you it can't resolve lists.familyvoices.org. When I try to lookup that name, I get a SERVFAIL error which means your DNS is not set up correctly and the server is encountering an error when trying to resolve lists.familyvoices.org. Fix that, then see what happens. -- Larry Stone [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] No address associated with nodename
Oops, forgot to anwer the second part. On Tue, 18 Oct 2005, Andrew Hedges wrote: Context: I'm BRAND new to configuring mail servers, so go easy! ;^) I'm running Mailman 2.1.6 on a Mac G4 running OS X 10.4.2 using the default Postfix and Python installations (versions 2.1.5 and 2.3.5, respectively). PS: As an aside, is it typical for it to take nearly 3 seconds for Mailman to process one, puny message to a list with one, puny recipient? What's the gate on performance? Disk speed? CPU? Network connection? It depends, as always. I think the delay may be related to the DNS error. Whatever time you do see will break down to a large per message overhead with a small per recipient time - in other words, just because to send to one recipient takes X seconds does not mean 100 reipients will take 100X seconds. Our lists won't be large (the largest is around 200 members), but we will have about 40 of them. Will this overload my little Mac? How much traffic? You should be fine. I'm running mailman on a half-dome iMac - two major lists - one has about 50 members and gets 100 or so small (under 5k) messages per day and the other has about 150 members and 1 100k message per day. DSL at 384kbps upstream. I don't notice the effect of either list on computer performance. I would notice the second on DSL bandwidth if I were up at 2am when that message gets sent - it ties up the connection for about five minutes (I VERP all messages so to send to those 150 members means 150 seperate messages going up the DSL line). -- Larry Stone [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] Munged addresses
Thanks. I'm not sure I feel comfortable dinking around in those files. I guess the user will have to live with those addresses for now. On 10/18/05 8:53 AM, Mark Sapiro [EMAIL PROTECTED] wrote: Robert Morse wrote: On 10/18/05 8:12 AM, Mark Sapiro [EMAIL PROTECTED] wrote: Robert Morse wrote: Is this 'stock' Mailman, or does this list use a custom MemberAdaptor? Stock as far as I know. Never heard of MemberAdaptor. It's a cpanel instal of Mailman. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp You can see that there is an actual email address in there, which when searched on returns a valid address. I would like to get rid of these munged addresses, but when I check the box to unsubscribe them, I get a message back that says the subscriber is not listed. Some are much longer, some ae shorter. Any way I can get rid of these things? I think I understand now. Apparently at one time someone attempted a mass subscribe from a file or list that contained more than just real names and e-mail addresses and you got a bunch of bad addresses subscribed. They appear first in the membership list because they begin with '#' or other characters that sort before 'a'. The actual e-mail address was ultimately subscribed and is a list member, but you still have these other bad member 'addresses'. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.013.htp - Bob Morse Morse Media Video Production * Web Development * Web Hosting http://morsemedia.net (Phone) 707-444-9566 (Fax) 707-476-8049 (Cell) 707-496-9191 -- 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] Strange errors
Dan Szkola wrote (in separate posts): Is there somewhere I can enable more debugging to help get to the bottom of this issue? I'm finding next to nothing in the logs that is helpful. As Brad replied, there are no debugging switches, but I'm not sure that this would be helpful in this case anyway. The traceback you get in sendmail's DSN tells us what happens, and the why doesn't seem to be Mailman. Also, the error occurs in the import of the logging module so there is a catch 22 in trying to log information about the error. Next time this occurs, you could look to see if Python's traceback.py is actually in the library. Normally, there will be a traceback.py, traceback.pyc and traceback.pyo in /usr/lib/python2.4, but only the traceback.py should be necessary. The others are compiled versions that will be (re)created as needed. I restarted only the mailman processes using bin/mailmanctl restart and post still generate the error above. This is further confirmation that the problem isn't Mailman per se. The only thing I can think is that somehow something that affects Python is being set by sendmail in the environment that it passes to the wrapper, and that this only happens after a number of posts. Environment variables that affect Python should begin with 'PYTHON' and are described on the python man page. You could try the following patch to the $prefix/scripts/post script to print the environment each time it is invoked. Assuming sendmail doesn't choke on this in the normal case, it should appear in the DSN in the error case. Patch- --- scripts/post2005-10-14 16:31:41.93750 -0700 +++ scripts/post_patched2005-10-18 12:14:18.03125 -0700 @@ -27,6 +27,9 @@ import sys +from os import environ +for env_var in environ: +print env_var, environ[env_var] import paths from Mailman import mm_cfg End Patch- Perhaps a better plan would be to patch the $prefix/scripts/admin script instead (same patch). Presumably mail to the listname-admin address will bounce the same way when the problem occurs because it begins with the same imports, but listname-admin is a deprecated name and shouldn't be receiving mail normally, so patching the admin script and sending mail to listname-admin should get the information you want in the DSN without possibly choking sendmail in the 'normal' case. I will put the line below into the mm_cfg.py file and restart sendmail and watch what happens. I have no reason other than superstition for the following suggestion, but try SMTP_MAX_SESSIONS_PER_CONNECTION = 1 in mm_cfg.py and see if that helps. This will cause Mailman to close the SMTP connection to sendmail after each transaction. This might avoid the problem, but since I have no idea what the problem is, I have no idea if this will help. OK. Let us know. -- 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] No address associated with nodename
Andrew Hedges wrote: Oct 18 11:41:10 2005 (92) Low level smtp error: (7, 'No address associated with nodename'), msgid: [EMAIL PROTECTED] Oct 18 11:41:10 2005 (92) delivery to [EMAIL PROTECTED] failed with code -1: (7, 'No address associated with nodename') snip From $prefix/Mailman/mm_cfg.py: MTA = Postfix DEFAULT_EMAIL_HOST = 'lists.familyvoices.org' DEFAULT_URL_HOST = 'lists.familyvoices.org' add_virtualhost(DEFAULT_URL_HOST,DEFAULT_EMAIL_HOST) DEFAULT_MAX_MESSAGE_SIZE = 64 # KB SMTPHOST = 'lists' The problem is Python's smtplib is not able to find the domain 'lists' to connect to. Remove SMTPHOST = 'lists' from mm_cfg.py and let this default to 'localhost'. PS: As an aside, is it typical for it to take nearly 3 seconds for Mailman to process one, puny message to a list with one, puny recipient? No, but this probably reflects the time required to determine that the DNS lookup of 'lists' is unsuccessful. -- 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] No address associated with nodename
On Tue, 18 Oct 2005, Larry Stone wrote: A cryptic message to be sure but I think it's trying to tell you it can't resolve lists.familyvoices.org. When I try to lookup that name, I get a SERVFAIL error which means your DNS is not set up correctly and the server is encountering an error when trying to resolve lists.familyvoices.org. Disregard this. DNS appears fine now. Perhaps a transient problem at your ISP or perhaps I mistyped the name when checking. -- Larry Stone [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] No address associated with nodename
YES! That was exactly it. I commented out the SMTPHOST line (letting it default to localhost) and all's well. Thanks! -Andrew - Andrew Hedges Technology Coordinator Family Voices, Inc. 2340 Alamo Ave SE, Suite 102 Albuquerque, NM 87106 505-872-4774 phone 505-872-4780 fax [EMAIL PROTECTED] http://www.familyvoices.org/ -Original Message- From: Larry Stone [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 18, 2005 1:57 PM To: Andrew Hedges Subject: RE: [Mailman-Users] No address associated with nodename On Tue, 18 Oct 2005, Andrew Hedges wrote: Thanks for your reply, Larry! To make sure I understand (so I can hassle my ISP), is it Mailman that's having trouble looking up lists.familyvoices.org? Is it Postfix? I *guess* they use some system-level service for DNS lookups, right, like the DNS servers saved in my Network prefs? I've had A and MX records setup with my ISP for several days, so propogation shouldn't be the problem. See Mark Sapiro's reply sent almost at the same time as yours. He's probably closer that you have a bad value for SMTPHOST. Just let it default to localhost. I checked the addresses again and now all seems fine. Perhaps a transient problem with your ISP or maybe I fat-fingered the name. Yes, eveything uses the same low level stuff to do DNS lookups (lookupd). -- Larry Stone [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
[Mailman-Users] Cannot View Subscribers' List - Mailman 2.1.5
Hi, This is my first time posting to this list; I hope someone can help me. One of our clients is unable to view their subscriber list via the listinfo page; the result insists on a valid email address. The client *is* using a valid address and I have confirmed that she has the correct password. I have also failed to log in via our master user-name and I have re-set the password. Does anyone have any ideas about solving this? Many thanks, Geoff Geoffrey Dow, Support Team Leader/Dirigeant de l'équipe du soutien [EMAIL PROTECTED] 416.596.0212 x2 - 1.800.932.7003 x2 Fax: 416-596-1374 401 Richmond St. West, Suite 384, Toronto, ON M5V 3A8 www.web.ca support.web.ca community.web.ca *Website services for socially committed organizations* -- 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] Exporting subscribers list
Hello. I am tring your mailman-subscribers.py script using ActiveState Python 2.4 with ClientCookie enabled. I am trying to fetch the subscribers list from my WindowsXP box to a hosting service where I have 2000+ subscribers I type: python.exe mailman-subscribers.py -v sg-guarani.org newsletter mypassword And I get a 0 What am I doing wrong? Thanks in advance. On 19/11/2004 21:35, Jim Tittsler wrote: On Fri, Nov 19, 2004 at 01:52:36PM -0300, Arlequín wrote: I am using MailMain trough its web-based interface. I don't have access to the server where its runs, because it's a third-party hosting company which provides me the MailMan service. I want to export the subscribers list in a format like this: [EMAIL PROTECTED] [EMAIL PROTECTED] mailman-subscribers.py is example program showing how you can get that sort of list through the web interface. It is available from; http://starship.python.net/crew/jwt/mailman/#throughtheweb -- Arlequín _o) amahoro_AT_adinet_DOT_com_DOT_uy / \\ http://counter.li.org/ _(___V Linux Registered User #207262 -- 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] adding list on virtual domain
I want to change a list I added to the main domain on the list server to the equivalent of having added the list as [EMAIL PROTECTED] I would have thought this was the preferred domain variable in the general options, but it's still taking me to http://maindomain.com/mailman/admin/listname/members etc instead of http://www.myotherdomain.com/mailman/admin/listname/members ? Anne -- 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] Munged addresses
Bob Morse wrote:
Thanks. I'm not sure I feel comfortable dinking around in those files. I
guess the user will have to live with those addresses for now.
OK. Here are some other things you might feel comfortable with. I
suspect the first two won't work, but they are worth a try.
1) click on the bad address link on the member list. if this gets you
to an options page for the bad address, check the 'Yes, I really want
to unsubscribe' box and click 'Unsubscribe'.
2a) if 1) doesn't work, try
bin/list_members --output bad_member_file --invalid list_name
Check the contents of bad_member_file to make sure it doesn't contain
any good entries. It may not contain all the bad ones either. If it
doesn't, you could do
bin/list_members --output member_file list_name
and edit that to remove the good ones or copy/paste the missing bad
ones.
2b) Then try
bin/remove_members --file=bad_member_file list_name
3) You may not be comfortable with this one, but if 2b) doesn't work,
try this:
$ bin/withlist -l listname
Loading list listname (locked)
The variable `m' is the listname MailList instance
fp = open('bad_address_file', 'r')
for address in fp.readlines():
... addr = address.strip()
... try:
... m.removeMember(addr)
... print 'Removed', addr
... except Errors.NotAMemberError:
... print 'Not a member', addr
...
Not a member [EMAIL PROTECTED]
Not a member [EMAIL PROTECTED]
Not a member [EMAIL PROTECTED]
m.Save()
Unlocking (but not saving) list: listname
Finalizing
$
In the above, '$' is a shell prompt; '' and '...' are Python
prompts; other lines are responses from Python. The input to the final
... prompt is a new-line (CR or Enter) and the input to the final
prompt is control-D (Unix end of file). The indentation on the ...
prompted lines is important.
In my case, bad_address_file contained the 3 addresses [EMAIL PROTECTED],
[EMAIL PROTECTED] and
[EMAIL PROTECTED], none of which were list members.
If you are not happy with what you see at any point, you can just type
the control-D without first entering m.Save() and the list will not 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] Cannot View Subscribers' List - Mailman 2.1.5
Web User Support wrote: One of our clients is unable to view their subscriber list via the listinfo page; the result insists on a valid email address. The client *is* using a valid address and I have confirmed that she has the correct password. I have also failed to log in via our master user-name and I have re-set the password. Does anyone have any ideas about solving this? Is the roster available to list members or only to the admin? (it says on the listinfo page) See private roster on Privacy options...Subscription rules. Not that if it is a private roster, even if she is the list admin, she must use the list admin password to view the roster. Her member password won't work unless the roster is available to members. -- 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] adding list on virtual domain
Anne Ramey wrote: I want to change a list I added to the main domain on the list server to the equivalent of having added the list as [EMAIL PROTECTED] I would have thought this was the preferred domain variable in the general options, but it's still taking me to http://maindomain.com/mailman/admin/listname/members etc instead of http://www.myotherdomain.com/mailman/admin/listname/members Presumably you're talking about host_name which is the e-mail domain but not the web domain. What you need to change is web_page_url which is not visible in the admin interface. The preferred way to change this is via the fix_url script. Run bin/fix_url.py for instructions. -- 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] Exporting subscribers list
Arlequín wrote: I am tring your mailman-subscribers.py script using ActiveState Python 2.4 with ClientCookie enabled. I am trying to fetch the subscribers list from my WindowsXP box to a hosting service where I have 2000+ subscribers I type: python.exe mailman-subscribers.py -v sg-guarani.org newsletter mypassword And I get a 0 Granted the script should be more robust, but it's only an example... First, what version of mailman-subscribers.py do you have? The latest is 2005-06-14. There have been at least 5 revisions since November 2004. The current version when run with the -v option emits '0(0)' as it retrieves the first page of the member list and then perhaps 'a(0)' as it gets the first page of 'a' and 'a(1)' for the second page of a and so on. I can make it emit '0(0)' and nothing more if I misspell the listname or the list password, but I am running the latest version with Python 2.4.1 so it uses Python's cookielib instead of ClientCookie. I seem to remember that -v used to work differently, but I don't recall the details and no longer have any old versions. If you literally mean it prints '0' and then slowly adds '.', it is probably printing one '.' per page of admin_member_chunksize or less members which would be 70+ dots for 2000+ members with the standard default of 30 for admin_member_chunksize. -- 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
