[Mailman-Users] Mails not writing to archive immediately
I've just been mailed by one of my users to say that the archive for my list is not up to date. Having just checked prior to sending this, I found that by clicking on the Date link for this month, the last message written to it is nearly a week old. Downloading the Gzip'd text file (which never actually shows the correct size - any ideas?) brings me forward to only approximately 24 hours behind. Does anybody know why this is - I'm assuming messages that get posted to the list should also hit the archive at the same time. Rgds MD -- 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] Mails not writing to archive immediately
Martin Dennett wrote: I've just been mailed by one of my users to say that the archive for my list is not up to date. Having just checked prior to sending this, I found that by clicking on the Date link for this month, the last message written to it is nearly a week old. Downloading the Gzip'd text file (which never actually shows the correct size - any ideas?) brings me forward to only approximately 24 hours behind. The .txt.gz file is essentially up to date (it is only updated once daily when cron/nightly_gzip runs). If you remove the .gz from the URL that accesses the gzipped text, you will see the ungzipped text, and it should be completely up to date. Thus the problem is *not* that ArchRunner isn't running, but rather it is in the archiving process itself. You need to check Mailman's 'error' log which will contain error reports and tracebacks of the exception that causes the problem. Also, the messages have probably been placed in Mailman's 'shunt' queue and can be reprocessed for the archive by bin/unshunt, but the problem has to be fixed first, or they will just be shunted again. If you don't have access to the logs, you'll have to enlist the help of whoever does. -- 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] How does mailman/mail/wrapper get created?
I am working with my ISP to get Mailman installed on a private domain. I believe we have followed all of the Mailman setup instructions correctly. We are at the point where we mail lists with subscribers. However, when attempted to send email to one of the lists (e.g., [EMAIL PROTECTED]), we are now getting an error message that says: sh: line 1: /home/bar/mailman/mail/wrapper: No such file or directory Looking at my installation, there is no mail/main/wrapper file. Should there be one? Should it have been created by make install or is this something that needs to be created manually? Thanks. Jon Ferraiolo [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] How does mailman/mail/wrapper get created?
Jon Ferraiolo wrote: We are at the point where we mail lists with subscribers. However, when attempted to send email to one of the lists (e.g., [EMAIL PROTECTED]), we are now getting an error message that says: sh: line 1: /home/bar/mailman/mail/wrapper: No such file or directory Looking at my installation, there is no mail/main/wrapper file. Should there be one? Should it have been created by make install or is this something that needs to be created manually? It looks like you have installed aliases or other MTA configuration for Mailman 2.0.x. In 2.1 the mail wrapper is /usr/local/mailman/mail/mailman (or whatever the path is). It is named 'mailman', not 'wrapper'. See item 2 in http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.014.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
[Mailman-Users] LDAP auth for admins
Has anyone done this already: change the login page to accept email address and password and then (1) check to be sure the email address is an owner of the list then (2) if so, authenticate them off an LDAP? This would really reduce our forgot password type support calls. -- 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
[Mailman-Users] Still can't send out from Mailman
AFAIK, my mailman failure to send out issue, resides solely at the pathway from mailman - exim. All other email traffic, i.e., exim-mailman and all other email traffic, seems to work just fine. I have included the debug line in my SMTPDirect.py file, and yet nothing shows up in /var/log/mailman/error, i.e., no debug messages. Scott -- 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] Still can't send out from Mailman
Dr. Scott S. Jones wrote: AFAIK, my mailman failure to send out issue, resides solely at the pathway from mailman - exim. All other email traffic, i.e., exim-mailman and all other email traffic, seems to work just fine. I have included the debug line in my SMTPDirect.py file, and yet nothing shows up in /var/log/mailman/error, i.e., no debug messages. If you have restarted Mailman after adding the set_debuglevel(1) call, you should at least see the connect attempt logged. You can try the following: Give the command /usr/lib/python2.x/smtplib.py It will prompt you for a To: and From: address and a message body and then attempt to send that via 'localhost' port 25 and print all the debugging info. Note that the /usr/lib/python2.x part of the above needs to be adjusted, but it is the path to your installed Python library. It is usually /usr/lib/python2.x where 2.x is your Python version. -- 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] undelivered mail, but only to some
I am having a baffling problem with Mailman. Suddenly the list that I am administrating has stopped delivering mail to a subset of the subscribers. It's not readily apparent what those that are not receiving the mails have in common - the domains that I know of include mac.com, yahoo.com, av8inc.com. It also seems that anyone new added to the list does not receive emails, though they do receive the initial subscripion notice and the monthly reminders. I have seen once that someone newly subscribed received one posting and has not received another since. This list is provided to me by my web hosting provider, who is also baffled. The Mailman installation is version 2.1.5. The sendmail logs show successful transmissions to the users in question, at the correct time, so it appears Mailman is sending something, but the receiving end must be discarding it. I'm one of those not receiving the emails. I've contacted my mail provider, mac.com, but they want a copy of the email being sent with complete headers. Since any new subscribers I've added aren't getting emails I'm having trouble doing this. We set up a test list. I've found that the test list works if I subscribe only myself. However, if I mass subscribe all the subscribers of the malfunctioning list to the test list, it appears to behave in the same manner as the malfunctioning list. That seems to imply that it is either the number of subscribers or that one bad entry in the list is creating the problem. It can't be the number of subscribers, there are other, bigger Mailman lists on this same host that seem to be working correctly. There are less than 100 subscribers to my list. In examining the list that I am subscribing I can find no entries that appear malformed. Does anyone have any suggestions? TIA. Alan -- 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] trying to change default_url_pattern
I put this setting in my mm_cfg.py: DEFAULT_URL_PATTERN = 'http://%s/mailman_ldap/' and my httpd.conf contains this: # This alias is for mailman mailing lists ScriptAlias /mailman_ldap/ /usr/local/mailman_ldap/cgi-bin/ I can log into the list fine, but all of the links on that page are /mailman/ not /mailman_ldap/ and if I try and type in the correct link it works. How do I change this so that it changes what links it creates in my web interface?* * -- 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] trying to change default_url_pattern
Anne Ramey sent the message below at 12:31 10/26/2006: I put this setting in my mm_cfg.py: DEFAULT_URL_PATTERN = 'http://%s/mailman_ldap/' and my httpd.conf contains this: # This alias is for mailman mailing lists ScriptAlias /mailman_ldap/ /usr/local/mailman_ldap/cgi-bin/ I can log into the list fine, but all of the links on that page are /mailman/ not /mailman_ldap/ and if I try and type in the correct link it works. How do I change this so that it changes what links it creates in my web interface?* * End original message. - Did you make these changes before or after setting up the list(s)? If after, did you run fix_url on the list(s) to update their configuration? Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- 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] trying to change default_url_pattern
I thought that was just for the hostname. Worked like a charm! Thanks Anne Dragon wrote: Anne Ramey sent the message below at 12:31 10/26/2006: I put this setting in my mm_cfg.py: DEFAULT_URL_PATTERN = 'http://%s/mailman_ldap/' and my httpd.conf contains this: # This alias is for mailman mailing lists ScriptAlias /mailman_ldap/ /usr/local/mailman_ldap/cgi-bin/ I can log into the list fine, but all of the links on that page are /mailman/ not /mailman_ldap/ and if I try and type in the correct link it works. How do I change this so that it changes what links it creates in my web interface?* * End original message. - Did you make these changes before or after setting up the list(s)? If after, did you run fix_url on the list(s) to update their configuration? Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- 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] trying to change default_url_pattern
Anne Ramey wrote re: fix_url: I thought that was just for the hostname. Worked like a charm! Thanks Actually, you can change host_name (email host) from the web interface so fix_url isn't really needed for that. What fix_url updates in addition to host_name is the hidden attribute web_page_url which is made from DEFAULT_URL_PATTERN with the substitution of the web host, See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.069.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] undelivered mail, but only to some
D. Alan Stewart wrote: This list is provided to me by my web hosting provider, who is also baffled. The Mailman installation is version 2.1.5. The sendmail logs show successful transmissions to the users in question, at the correct time, so it appears Mailman is sending something, but the receiving end must be discarding it. I'm one of those not receiving the emails. I've contacted my mail provider, mac.com, but they want a copy of the email being sent with complete headers. Since any new subscribers I've added aren't getting emails I'm having trouble doing this. If the sendmail log says the post is sent to the user in question, Mailman delivered it to sendmail for the user, and it's not Mailman's problem. Here are things you can check. Mailman's 'smtp' log. This will tell you how many recipients the post was sent to. Also check if the list is personalized. You may not even have personalization options on your Non-digest options page which means that OWNERS_CAN_ENABLE_PERSONALIZATION is not set to Yes in mm_cfg.py and delivery is almost certainly not personailzed. Check the settings of VERP_DELIVERY_INTERVAL and SMTP_MAX_RCPTS if any in mm_cfg.py If the list is not personalized and delivery is not 'VERP like' because VERP_DELIVERY_INTERVAL has its default value of 0, and SMTP_MAX_RCPTS has its default value of 500, then all 100 or less recipients receive the identical message sent by Mailman in the same SMTP transaction (with each recipient specified in a RCPT TO command). You should also see this in the sendmail log, i.e. that the mail was delivered to sendmail in one transaction. Thus, if you can get copy of a received post from anyone, all the initial headers (those that aren't Received: headers added by MTA's outbound of your sendmail or other headers added by MDA's or receiving MUA's) will be identical to those of the missing deliveries. We set up a test list. I've found that the test list works if I subscribe only myself. However, if I mass subscribe all the subscribers of the malfunctioning list to the test list, it appears to behave in the same manner as the malfunctioning list. That seems to imply that it is either the number of subscribers or that one bad entry in the list is creating the problem. It can't be the number of subscribers, there are other, bigger Mailman lists on this same host that seem to be working correctly. Can you add yourself to one of these lists? There are less than 100 subscribers to my list. In examining the list that I am subscribing I can find no entries that appear malformed. Does anyone have any suggestions? Sendmail claims it sent the mail to the users who didn't get it. I recognize the symptoms say that Mailman is somehow involved, but I don't see how. -- 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] undelivered mail, but only to some
In what order does Mailman process subscribers when it is transmitting to the list? The order in which they are subscribed? Alphabetical by email address? Random? On Oct 26, 2006, at 2:55 PM, D. Alan Stewart wrote: I am having a baffling problem with Mailman. Suddenly the list that I am administrating has stopped delivering mail to a subset of the subscribers. It's not readily apparent what those that are not receiving the mails have in common - the domains that I know of include mac.com, yahoo.com, av8inc.com. It also seems that anyone new added to the list does not receive emails, though they do receive the initial subscripion notice and the monthly reminders. I have seen once that someone newly subscribed received one posting and has not received another since. This list is provided to me by my web hosting provider, who is also baffled. The Mailman installation is version 2.1.5. The sendmail logs show successful transmissions to the users in question, at the correct time, so it appears Mailman is sending something, but the receiving end must be discarding it. I'm one of those not receiving the emails. I've contacted my mail provider, mac.com, but they want a copy of the email being sent with complete headers. Since any new subscribers I've added aren't getting emails I'm having trouble doing this. We set up a test list. I've found that the test list works if I subscribe only myself. However, if I mass subscribe all the subscribers of the malfunctioning list to the test list, it appears to behave in the same manner as the malfunctioning list. That seems to imply that it is either the number of subscribers or that one bad entry in the list is creating the problem. It can't be the number of subscribers, there are other, bigger Mailman lists on this same host that seem to be working correctly. There are less than 100 subscribers to my list. In examining the list that I am subscribing I can find no entries that appear malformed. Does anyone have any suggestions? TIA. Alan -- 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/ d.alan.stewart%40mac.com 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] undelivered mail, but only to some
D. Alan Stewart wrote: In what order does Mailman process subscribers when it is transmitting to the list? The order in which they are subscribed? Alphabetical by email address? Random? It's a two step process. In the first step the CalcRecips handler builds a recipient list. Assuming you don't have a custom MemberAdaptor, and you probably don't, this list is in a hashed order, i.e. pseudo random. Step 2 occurs in the delivery handler, SMTPDirect. Here the above list is split into up to 4 sublists containing 1 - all the addresses in the .com domain 2 - all the addresses in the .net and .org domains 3 - all the addresses in the .edu, .us and .ca domains 4 - all other addresses Within these sublists, the original pseudo random order is preserved. Then the sublists are processed in a hashed order, but since we know the keys in this case, we know the order (at least with python 2.4), and it is 4, 1, 2, 3. So basically the recipient addresses are all the 'other' domain addresses in a pseudo random order followed by all the .com addresses in a pseudo random order followed by all the .net and .org addresses in a pseudo random order followed by all the .edu, .us and .ca addresses in a pseudo random order. -- 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] Still can't send out from Mailman
Dr. Scott S. Jones wrote:
You can try the following:
Give the command
/usr/lib/python2.x/smtplib.py
fyrenice:/var/log/mailman# /usr/lib/python2.3/smtplib.py
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Enter message, end with ^D:
this is a test message, at M. Sapiro's suggestions.
This is only a test.
Message length is 74
send: 'ehlo localhost.localdomain\r\n'
reply: '250-fyrenice.com Hello localhost [127.0.0.1]\r\n'
reply: '250-SIZE 52428800\r\n'
reply: '250-PIPELINING\r\n'
reply: '250 HELP\r\n'
reply: retcode (250); Msg: fyrenice.com Hello localhost [127.0.0.1]
SIZE 52428800
PIPELINING
HELP
send: 'mail FROM:[EMAIL PROTECTED] size=74\r\n'
reply: '250 OK\r\n'
reply: retcode (250); Msg: OK
send: 'rcpt TO:[EMAIL PROTECTED]\r\n'
reply: '250 Accepted\r\n'
reply: retcode (250); Msg: Accepted
send: 'data\r\n'
reply: '354 Enter message, ending with . on a line by itself\r\n'
reply: retcode (354); Msg: Enter message, ending with . on a line by itself
data: (354, 'Enter message, ending with . on a line by itself')
send: this is a test message, at M. Sapiro's suggestions. \r\nThis is only
a test.\r\n.\r\n
reply: '250 OK id=1GdCfZ-0002XR-Fc\r\n'
reply: retcode (250); Msg: OK id=1GdCfZ-0002XR-Fc
data: (250, 'OK id=1GdCfZ-0002XR-Fc')
send: 'quit\r\n'
reply: '221 fyrenice.com closing connection\r\n'
reply: retcode (221); Msg: fyrenice.com closing connection
From all the OK items, is it safe to say that worked correctly, aside from
my failure to end with a '.' on a line by itself?
Actually, you did just what you were supposed to do. Terminating the
data with '.' on a line by itself is part of the protocol and smtplib
did that - that's the '\r\n.\r\n' at the end of the data.
So the above test worked. Now the question is why doesn't it work when
Mailman does it.
Things to check/try.
Defaults.py should have
SMTPHOST = 'localhost'
SMTPPORT = 0
These should not be changed in mm_cfg.py.
If the above test was not run as the Mailman user, run it as the
Mailman user ('mailman' or what ever it is on your system).
Try the above as an ordinary user, not root, no special permissions.
BTW, is Mailman using Python 2.3? I.e. is there another Python version
on the machine that Mailman might be using?
--
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] Still can't send out from Mailman
Dr. Scott S. Jones wrote: I changed my mm_cfg.py to read as last two lines: SMTPHOST = 'localhost' SMTPPORT = 0 This does no harm, but putting those lines in mm_cfg.py doesn't really do anything as you are just resetting them to the same values they already have from Defaults.py. I have since run /etc/init.d/mailman restart, which responded as follows: fyrenice:/etc# /etc/init.d/mailman restart Restarting mailman queue runner: mailmanShutting down Mailman's master qrunner No child with pid: 17469 [Errno 3] No such process Stale pid file removed. Starting Mailman's master qrunner. This indicates that Mailman may have been improperly shut down in the past (maybe from your crash?). Now, do 'ps -fAw | grep python' or however you spell that on your system. You should see exactly one mailmanctl process and exactly 8 qrunner processes with names ArchRunner, BounceRunner, CommandRunner, IncomingRunner, NewsRunner, OutgoingRunner, VirginRunner and RetryRunner. If this is not what you see, see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.068.htp for a procedure that will clean things up. Also, are you still getting the same smtp-failure entries when Mailman sends, and are you getting any log messages from smtplib in Mailman's 'error' log? -- 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] Still can't send out from Mailman
Dr. Scott S. Jones wrote: The output from /var/log/mailman/smtp-failures includes the following: Oct 26 17:22:40 2006 (13140) delivery to [EMAIL PROTECTED] failed with code -1: [Errno 9] Bad file descriptor Oct 26 17:22:40 2006 (13140) delivery to [EMAIL PROTECTED] failed with code -1: [Errno 9] Bad file descriptor Oct 26 17:22:41 2006 (13140) Low level smtp error: [Errno 9] Bad file descriptor, msgid: [EMAIL PROTECTED] Oct 26 17:27:41 2006 (13140) delivery to [EMAIL PROTECTED] failed with code -1: [Errno 9] Bad file descriptor Oct 26 17:27:42 2006 (13140) Low level smtp error: [Errno 9] Bad file descriptor, msgid: [EMAIL PROTECTED] Oct 26 17:27:42 2006 (13140) delivery to [EMAIL PROTECTED] failed with code -1: [Errno 9] Bad file descriptor Oct 26 17:27:42 2006 (13140) Low level smtp error: [Errno 9] Bad file descriptor, msgid: [EMAIL PROTECTED] The list, with the first two lines, includes failed attempts to every one of the 280 or so entries on my 'sanchiro-patients' mailing list, all ending with the same error code. See the *entire* thread beginning at http://mail.python.org/pipermail/mailman-users/2006-October/053942.html I think both you guys should be talking to Debian, and if you find a resolution there, post it back here so we know what it is. -- 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
