[Mailman-Users] Public Mailing list
I cannot see how to create a public mailing list. I want to create a list that allows anyone to post a message (non-subscribers) but distribute the message to list members. Can someone point me in the right direction? TIA. 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
[Mailman-Users] Black hole
I am having trouble with my distribution lists (well, only one is currently under test). I can see from the mail.log file that an incoming message was processed and sent to 'mailman'. However, no one on the list received anything and I cannot see anything in the log where it was distributed. The message seems to have gone into a black hole without a trace. The logs have not been updated in a couple of weeks. Did I inadvertently turn off logging somewhere? How do I figure out what is wrong? 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
[Mailman-Users] Message unparsable
I am having a problem with some message not being distributed. When I look at the error file I can see this: Jun 23 11:34:34 2005 (3512) message is unparsable: 1119540873.457257+d314fcd9d886c11a670875a479fab98a5fdbde1e Jun 23 11:34:34 2005 (3512) lost data files for filebase: 1119540873.457257+d314fcd9d886c11a670875a479fab98a5fdbde1e I don't know where the message went so I can look at it but the copy the poster sent direct to me looks fine. How do I figure out what is wrong with either the message or Mailman? TIA. 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] Message Unparsable
After some research I have concluded that the errors I am getting from
Mailman are because of a malformed MIME content. Since I am creating
the message myself with a php page I am not surprised (my first time).
Since this probably is a MIME issue I know this is not the correct
forum. However, I am posting the suspect raw data here in the hopes
someone is familiar enough with MIME to spot the problem. At the very
least perhaps someone can point me to a good MIME forum. TIA.
Here is the MIME format message body for the problem message (I omitted
the routing headers):
MIME-version: 1.0
Content-type: multipart/mixed; boundry=!!!---===123_4567_890===---!!!
Message-Id: [EMAIL PROTECTED]
--!!!---===123_4567_890===---!!!
Content-Type: text/html; x-unix-mode=0644; name=application.html
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; name=application.html
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01
Transitional//ENhtmlheadtitleApplication for
Employment/titlemeta http-equiv=Content-Type content=text/html;
charset=iso-8859-1/headbodybrbr
htmlheadstyle
type=text/css!--body,p,div,span,td,input,textarea { font-family:
Times New Roman, Times, serif;font-size: 10pt;}h4
{ page-break-before: always;}--/style/headbody
onLoad=window.resizeTo(770,920)h2 align=righttest, test
test/h2
.
etc, etc, etc
.
/body/html
--!!!---===123_4567_890===---!!!
Content-Transfer-Encoding: base64
content-type: application/msword; name=IT Labels.doc
0M8R4KGxGuEAPgADAP7/
CQAGAAABKwAA
EAAALQEAAAD+ACoAAAD
/
///
/
///
/
.
etc, etc, etc
.
--!!!---===123_4567_890===---!!!--
End of MIME formatted message body
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] Message Unparsable
This problem seems to be a little more serious then I thought. It appears that no HTML attachments are getting through mailman. In addition to the unparsable error I am also getting a non-text attachment was scrubbed error and one message went into a black hole (no message distributed and nothing in any Mailman logs). There is only a message in the SMTP log showing the message was passed to the Mailman command string. I desperately need some help resolving this problem. Is there some filtering going on here that hoses HTML attachments that needs to be turned off. How can I debug this when there is nothing in the logs? Is there a verbose mode switch I can turn on? TIA. 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] Message Unparsable
Hm.. Shunt queue? Maybe that would at least let me know what Mailman is looking that it can't parse, just in case something unexpected is being inserted along the way. Where is that directory? I see nothing in the /var/mailman path that looks like a shunt queue. I'm not a Python programmer so I am not about to touch that. Thanks for the reply. On Jun 27, 2005, at 8:42 AM, Brad Knowles wrote: At 8:24 AM -0400 2005-06-27, Dennis Putnam wrote: How can I debug this when there is nothing in the logs? Good question. Is there a verbose mode switch I can turn on? TIA. Nope, no verbose mode. One of the problems I've had with Mailman for some time has been the sometimes limited amount of information that it puts into the logs, and the lack of any kind of ability to increase the logging level. You may be forced to use command-line tools to try to identify problematical messages that are sitting in the shunt queue (if any), or going into the Python source code and adding some more of your own logging. 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] Message Unparsable
Thanks. It is in /var/mailman/qfiles but the shunt directory is empty. Rats! On Jun 27, 2005, at 9:07 AM, Brad Knowles wrote: Normally, it would be located under /usr/local/mailman/qfiles/shunt, but it appears that the version of Mailman you're using on your platform has put that directory structure somewhere else. SNIP 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
[Mailman-Users] Fwd: Message Unparsable
I am reposting this previously unanswered request for help to the list
again as I am desperate to get this resolved. Surely there is someone
out there with sufficient MIME expertise to help me. I am unable to
find any MIME specific forms elsewhere. I should note that sending the
MIME message direct rather then through Mailman works and looks just
fine. TIA.
Begin forwarded message:
From: Dennis Putnam [EMAIL PROTECTED]
Date: June 24, 2005 7:32:29 AM EDT
To: Mailman users list list mailman-users@python.org
Subject: Re: Message Unparsable
After some research I have concluded that the errors I am getting from
Mailman are because of a malformed MIME content. Since I am creating
the message myself with a php page I am not surprised (my first time).
Since this probably is a MIME issue I know this is not the correct
forum. However, I am posting the suspect raw data here in the hopes
someone is familiar enough with MIME to spot the problem. At the very
least perhaps someone can point me to a good MIME forum. TIA.
Here is the MIME format message body for the problem message (I
omitted the routing headers):
MIME-version: 1.0
Content-type: multipart/mixed; boundry=!!!---===123_4567_890===---!!!
Message-Id: [EMAIL PROTECTED]
--!!!---===123_4567_890===---!!!
Content-Type: text/html; x-unix-mode=0644; name=application.html
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment; name=application.html
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01
Transitional//ENhtmlheadtitleApplication for
Employment/titlemeta http-equiv=Content-Type content=text/html;
charset=iso-8859-1/headbodybrbr
htmlheadstyle
type=text/css!--body,p,div,span,td,input,textarea { font-family:
Times New Roman, Times, serif; font-size: 10pt;}h4
{ page-break-before: always;}--/style/headbody
onLoad=window.resizeTo(770,920)h2 align=righttest, test
test/h2
.
etc, etc, etc
.
/body/html
--!!!---===123_4567_890===---!!!
Content-Transfer-Encoding: base64
content-type: application/msword; name=IT Labels.doc
0M8R4KGxGuEAPgADAP7/
CQAGAAABKwAA
EAAALQEAAAD+ACoAAAD///
//
//
//
//
//
.
etc, etc, etc
.
AAA
A
--!!!---===123_4567_890===---!!!--
End of MIME formatted message body
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] Fwd: Message Unparsable
DOH! No, I did not see that reply. Thanks. I wonder why it worked OK without going through Mailman? On Jul 12, 2005, at 9:18 AM, Schmitt, Gordon A. wrote: I thought I did see someone respond to you and maybe it wasn't the correct answer but they said that you have the word boundary mispelled, as boundry in the Content-Type line. Gordon Schmitt - System Administrator St. Cloud State University MC 108 St. Cloud, MN 56301 [EMAIL PROTECTED] 320-308-4838 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] Fwd: Message Unparsable
Changing the correct spelling of boundary to the incorrect spelling that MIME wants (whose idea was that anyway) didn't help. Same error. Are there any other correct spellings that need to be made incorrect? :-) On Jul 12, 2005, at 9:18 AM, Schmitt, Gordon A. wrote: I thought I did see someone respond to you and maybe it wasn't the correct answer but they said that you have the word boundary mispelled, as boundry in the Content-Type line. Gordon Schmitt - System Administrator St. Cloud State University MC 108 St. Cloud, MN 56301 [EMAIL PROTECTED] 320-308-4838 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] Fwd: Message Unparsable
Wait a minute. How stupid of me. The incorrect spelling (boundry) is what is wrong not the correct spelling (boundary). Sheesh. Its a pain getting old. Sorry to all. On Jul 12, 2005, at 10:21 AM, Dennis Putnam wrote: Changing the correct spelling of boundary to the incorrect spelling that MIME wants (whose idea was that anyway) didn't help. Same error. Are there any other correct spellings that need to be made incorrect? :-) On Jul 12, 2005, at 9:18 AM, Schmitt, Gordon A. wrote: I thought I did see someone respond to you and maybe it wasn't the correct answer but they said that you have the word boundary mispelled, as boundry in the Content-Type line. Gordon Schmitt - System Administrator St. Cloud State University MC 108 St. Cloud, MN 56301 [EMAIL PROTECTED] 320-308-4838 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/ dennis.putnam%40aimaudit.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp; file=faq01.027.htp 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
[Mailman-Users] Appendage problem
This time I think I have a legitimate question (that is not to say I didn't do something stupid again) with respect to the appendage of administrivia that Mailman puts at the end of each message. It seems that (at least) when the message is MIME format the separator (...) begins on the same line as the last attachment icon. Is this a mail reader quirk? Mailman is smart enough to use the boundary (sp?) from the original message but it doesn't add any newlines to separate its appendage from the original content. 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
[Mailman-Users] Migrating Lists to a new server
Can someone point me to some documentation for migrating mailman lists and archives to a new server? Thanks. 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] 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
[Mailman-Users] Need some migration help on OS X
I asked this a couple of weeks ago and did not get a response so I apologize for reposting but I need to get this fixed. I migrated my mailing lists to a new server following the instructions on the mailman web site. The problem I am having is that all messages posted to lists on the new server are forwarded to the old server for some reason (which, of course, prevents distribution since the old server is gone). I cannot find why but it has to be some kind of config issue. Could someone please point me in the right direction on this? TIA. 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
[Mailman-Users] Mailman server migration problem
I have migrated my mailman database according to directions indicated on the Mailman web site from one OS X server to another. Although the lists show up on the new server nothing works. In looking at the logs, it appears that each time a member posts a message, it gets processed by the new server and sent to mailman-bounces on the old server. That server bounces the mail and some ping-pong occurs for a while. Obviously there is some address somewhere about the list owner that the instructions did not mention needs to be changed. Can some one tell me were I can check this configuration problem? I cannot find any config files for mailman in any of the usual places. TIA. 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
[Mailman-Users] Documentation
Is there a document somewhere, online, that details all the variables so templates can be customized? Thanks. 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] is it possible to set up mailman on a host without a MTA?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 06:36 AM 10/20/2007, you wrote: Is it possible to set up mailman on a host without a MTA? I imagine mailman could easily send emails through an external MTA, and receive email using externam pop3 or imap account - however, I didn't find many hints about such setup in the fine documentation. Any clues? I'm not exactly sure what you are asking for but I have a Mandrake system on my DSL connected line without a static IP address. I have a couple of mailing lists running and use 'fetchmail'. I have mail boxes set up with my ISP and run 'fetchmail' via 'cron' to get the incoming messages. My SMTP sever is configured to use my ISPs mail server for the outgoing messages. If this is the kind of thing you are looking for let me know and we can discuss it further. -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.5.8 for non-commercial use http://www.pgp.com iQA/AwUBRxoTD/34lmKmdrVUEQLX+ACeP8z/0SPS3mozbIS2GkKhYERiSD8An2AY D3re3u6cgNnnFVAK3xujtqsA =XgTZ -END PGP SIGNATURE- -- 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] is it possible to set up mailman on a host without a MTA?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 02:32 PM 10/20/2007, you wrote: All right, I forgot about fetchmail. Was something non-standard needed to make mailman work with fetchmail/cron? -- Tomasz Chmielewski http://wpkg.org No. It was a little tricky to set things up so my ISP would accept mail from my SMTP server. The main problem was getting it configured so my ISP could recognize it as a legitimate customer sending mail. The 'fetchmail' part was cake. -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.5.8 for non-commercial use http://www.pgp.com iQA/AwUBRxpsmP34lmKmdrVUEQKyTQCfXmtDGOIr/TarRTAG84tUtQnE3m0AoJ4o YKWdPqgicH+S23dEj+d7UIEs =vQ+v -END PGP SIGNATURE- -- 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] is it possible to set up mailman on a hostwithout a MTA?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 11:56 AM 11/7/2007, you wrote: So, I started to put the things together. As you said, outgoing mail is easy, and incoming mail is harder (but can be done with fetchmail). So, considering no MTA is running on a machine which runs mailman - how do I go through this part: http://www.gnu.org/software/mailman/mailman-install/node13.html Putting this into aliases file on a mail server surely wouldn't make any sense: # bin/genaliases To finish creating your mailing list, you must edit your /etc/aliases (or equivalent) file by adding the following lines, and possibly running the `newaliases' program: ## some-list mailing list some-list: |/path/mailman/mail/mailman post some-list some-list-admin:|/path/mailman/mail/mailman admin some-list some-list-bounces: |/path/mailman/mail/mailman bounces some-list some-list-confirm: |/path/mailman/mail/mailman confirm some-list some-list-join: |/path/mailman/mail/mailman join some-list some-list-leave:|/path/mailman/mail/mailman leave some-list some-list-owner:|/path/mailman/mail/mailman owner some-list some-list-request: |/path/mailman/mail/mailman request some-list some-list-subscribe:|/path/mailman/mail/mailman subscribe some-list some-list-unsubscribe: |/path/mailman/mail/mailman unsubscribe some-list Should I just deliver all emails to one mailbox ([EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] etc.), and fetchmail should fetch it to: /path/mailman/archives/private/some-list.mbox/ ? That won't work. You need to create each one of those aliases as a mailbox at your ISP. Then do a fetchmail on each one. -BEGIN PGP SIGNATURE- Version: PGPfreeware 6.5.8 for non-commercial use http://www.pgp.com iQA/AwUBRzIwJf34lmKmdrVUEQJaGQCeLO0s9sWQX4Qs//b2Ux1wXdOdpAwAn1Yr m92Mxi3gtysyEqWIjtehdQ3T =1HqL -END PGP SIGNATURE- -- 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] Restoring Lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I had a disk failure and had to restore my Mandriva system from backup. Everything seems to work except Mailman. Well, mailman works but it does not recognize any of my old lists. How do I get Mailman to see the lists again? TIA. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFHeWGB/fiWYqZ2tVQRAvE+AJ9eBhtqYK7Jwg3oIdb/EyF5j5ERZACgvfyh 6J2L47K02sEJ/NHazJhVOwk= =puOi -END PGP SIGNATURE- -- 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] Restoring Lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 06:03 PM 1/1/2008, you wrote: On 1/1/08, Dennis Putnam wrote: You're missing the Python pickles which define which list(s) exist and what its/their configuration(s) is/are. Those should presumably be somewhere under /var/*/mailman/*, and you'd need to restore them as well. You'd need to stop Mailman, do the restore, then restart Mailman. Thanks for the reply but the only pickles I know of are made from cucumbers and vinegar. :-) What file name or type should I be looking for? If you've already done that, then I'm not sure that I can give you any more help -- in that case, you may have to wait for an answer from Mark Sapiro or someone else who knows the code better than I do. I thought I restored everything but since I don't know what to look for I can't really tell. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFHfBpu/fiWYqZ2tVQRAhO+AJ0fbSKKHMebFxhnc1qTYg9cGLLsGACg0SAl u55BQPPqLPWCq35JtZ02YRQ= =kmZA -END PGP SIGNATURE- -- 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] Restoring Lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 06:42 PM 1/2/2008, you wrote: Dennis Putnam wrote: Thanks for the reply but the only pickles I know of are made from cucumbers and vinegar. :-) What file name or type should I be looking for? lists/listname/config.pck - -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Thanks for the reply. I do indeed see .pck files. They are in /var/lib/mailman/lists/listname. It has always bothered me that Mandriva, for whatever reason, did not follow the mailman standard directories. My question now is how do I know mailman is looking in the correct place. I cannot find where the paths are defined in the cfg.py file. Do they exist somewhere else? This all worked until I had to do a restore. Obviously something is out of place but I just don't know enough about mailman to even start trying to figure out what. Just in case I forgot to mention the code is in /usr/local/lib/mailman. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFHfsjM/fiWYqZ2tVQRArYcAJ92KQ5hnW/ZPwS6M0eZV2sjw+kMYwCfdd0t w3RnzI9GMAXahXf10Pq5Eog= =ca7t -END PGP SIGNATURE- -- 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] Restoring Lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 02:32 PM 1/5/2008, you wrote: Look in Defaults.py for things like PREFIX, EXEC_PREFIX and VAR_PREFIX, and then for things defined in terms of these such as LIST_DATA_DIR, LOG_DIR, etc. Then look in mm_cfg.py for possible overrides. - -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Thanks again for the help. I knew it wasn't going to be that easy. Everything you mentioned seems copacetic. I guess the next question is, can I set some kind of debug that will give me some useful information in the logs? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFHgrjO/fiWYqZ2tVQRAn+0AKDEE1wSwnEYAQzcI1JcSEb0LQw4AgCg0E5E nIyqWFlpGkbwdscwloXv1+U= =oC+3 -END PGP SIGNATURE- -- 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] Restoring Lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks again. Please see the embedded responses. At 07:10 PM 1/7/2008, you wrote: What does Mailman's bin/list_lists show? It shows my lists correctly. What exactly is in mm_cfg.py and Defaults.py for VAR_PREFIX and LIST_DATA_DIR. Note that if LIST_DATA_DIR is defined in Defaults.py as os.path.join(VAR_PREFIX, 'lists'), redefining VAR_PREFIX in mm_cfg.py will not change the location of LIST_DATA_DIR unless it is also redefined in mm_cfg.py subsequent to the redefinition of VAR_PREFIX. None are overridden in mm_cfg.py. VAR_PREFIX = /var/lib/mailman What happens if you do [EMAIL PROTECTED] mailman]# bin/withlist -i No list name supplied. Python 2.4.3 (#1, Mar 14 2007, 18:51:08) [GCC 4.1.1 20070105 (Red Hat 4.1.1-52)] on linux2 Type help, copyright, credits or license for more information. (InteractiveConsole) from Mailman import mm_cfg mm_cfg.LIST_DATA_DIR '/usr/local/mailman/lists' It shows my correct path /var/lib/mailman/lists [EMAIL PROTECTED] mailman]# (the lines are where you enter things. A control-D is entered on the last line to quit) Then do ls -l /usr/local/mailman/lists or whatever the output from the above was. - -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan It shows my mailing lists. I guess the implication is that something else is wrong. Maybe some sub-process of mailman is not running? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFHgsQe/fiWYqZ2tVQRAvw/AJ4n2Edpj9EhCBmnDBs4UpU9RTqtBACg/iaA 9OnhEdCeFXfvsevEWkAL9xk= =ybEP -END PGP SIGNATURE- -- 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] Restoring Lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I just discovered something that may or may not be useful. Just for grins I tried sending a request to the request mail box. I saw some errors in the syslog but the main one is that there is a group error. The mailman wrapper expected to be run as group 'mail' but ran as group 'mailman' instead. This sounds like and ownership issue now. Everything is owned by 'mailman; and has group 'mail'. The mailman user is a member of both groups with 'mailman' as the primary. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFHgskd/fiWYqZ2tVQRAjRoAJ0XvyoP0aDSfXFghjE7NzQ/aIdgQQCfX5bv 080pVDToc203/slOrqidpw0= =FCch -END PGP SIGNATURE- -- 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] Restoring Lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 08:17 PM 1/7/2008, you wrote: This is a group mismatch error and will prevent any mail from reaching Mailman. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.016.htp . I'm guessing that this is Postfix. I would say, if that is the case, to make the owner of Mailman's aliases* files 'mail' to fix this, but I'm confused as to what in particular the definitions of MAILMAN_USER and MAILMAN_GROUP are (in Defaults.py/mm_cfg.py). It is in Defaluts.py and I see an uh,oh. MAILMAN_USER='mail' MAILMAN_GROUP='mail' What happens if you run bin/check_perms? Lots of uh, ohs here: directory must be at least 02775: /usr/lib/mailman directory permissions must be 02775: /usr/lib/mailman/Mailman directory permissions must be 02775: /usr/lib/mailman/bin directory permissions must be 02775: /usr/lib/mailman/cgi-bin directory permissions must be 02775: /usr/lib/mailman/cron directory permissions must be 02775: /usr/lib/mailman/mail directory permissions must be 02775: /usr/lib/mailman/messages directory permissions must be 02775: /usr/lib/mailman/pythonlib directory permissions must be 02775: /usr/lib/mailman/scripts directory permissions must be 02775: /usr/lib/mailman/templates directory permissions must be 02775: /usr/lib/mailman/tests directory permissions must be 02775: /usr/lib/mailman/Mailman/Archiver directory permissions must be 02775: /usr/lib/mailman/Mailman/Bouncers directory permissions must be 02775: /usr/lib/mailman/Mailman/Cgi directory permissions must be 02775: /usr/lib/mailman/Mailman/Commands directory permissions must be 02775: /usr/lib/mailman/Mailman/Gui directory permissions must be 02775: /usr/lib/mailman/Mailman/Handlers directory permissions must be 02775: /usr/lib/mailman/Mailman/Logging directory permissions must be 02775: /usr/lib/mailman/Mailman/MTA directory permissions must be 02775: /usr/lib/mailman/Mailman/Queue directory permissions must be 02775: /usr/lib/mailman/messages/ar directory permissions must be 02775: /usr/lib/mailman/messages/ca directory permissions must be 02775: /usr/lib/mailman/messages/cs directory permissions must be 02775: /usr/lib/mailman/messages/da directory permissions must be 02775: /usr/lib/mailman/messages/de directory permissions must be 02775: /usr/lib/mailman/messages/es directory permissions must be 02775: /usr/lib/mailman/messages/et directory permissions must be 02775: /usr/lib/mailman/messages/eu directory permissions must be 02775: /usr/lib/mailman/messages/fi directory permissions must be 02775: /usr/lib/mailman/messages/fr directory permissions must be 02775: /usr/lib/mailman/messages/hr directory permissions must be 02775: /usr/lib/mailman/messages/hu directory permissions must be 02775: /usr/lib/mailman/messages/ia directory permissions must be 02775: /usr/lib/mailman/messages/it directory permissions must be 02775: /usr/lib/mailman/messages/ja directory permissions must be 02775: /usr/lib/mailman/messages/ko directory permissions must be 02775: /usr/lib/mailman/messages/lt directory permissions must be 02775: /usr/lib/mailman/messages/nl directory permissions must be 02775: /usr/lib/mailman/messages/no directory permissions must be 02775: /usr/lib/mailman/messages/pl directory permissions must be 02775: /usr/lib/mailman/messages/pt directory permissions must be 02775: /usr/lib/mailman/messages/pt_BR directory permissions must be 02775: /usr/lib/mailman/messages/ro directory permissions must be 02775: /usr/lib/mailman/messages/ru directory permissions must be 02775: /usr/lib/mailman/messages/sl directory permissions must be 02775: /usr/lib/mailman/messages/sr directory permissions must be 02775: /usr/lib/mailman/messages/sv directory permissions must be 02775: /usr/lib/mailman/messages/tr directory permissions must be 02775: /usr/lib/mailman/messages/uk directory permissions must be 02775: /usr/lib/mailman/messages/vi directory permissions must be 02775: /usr/lib/mailman/messages/zh_CN directory permissions must be 02775: /usr/lib/mailman/messages/zh_TW directory permissions must be 02775: /usr/lib/mailman/messages/ar/LC_MESSAGES directory permissions must be 02775: /usr/lib/mailman/messages/ca/LC_MESSAGES directory permissions must be 02775: /usr/lib/mailman/messages/cs/LC_MESSAGES directory permissions must be 02775: /usr/lib/mailman/messages/da/LC_MESSAGES directory permissions must be 02775: /usr/lib/mailman/messages/de/LC_MESSAGES directory permissions must be 02775: /usr/lib/mailman/messages/es/LC_MESSAGES directory permissions must be 02775: /usr/lib/mailman/messages/et/LC_MESSAGES directory permissions must be 02775: /usr/lib/mailman/messages/eu/LC_MESSAGES directory permissions must be 02775: /usr/lib/mailman/messages/fi/LC_MESSAGES directory permissions must be 02775: /usr/lib/mailman/messages/fr/LC_MESSAGES directory permissions must be 02775: /usr/lib/mailman/messages/hr/LC_MESSAGES directory permissions must be 02775: /usr/lib/mailman/messages/hu/LC_MESSAGES directory
[Mailman-Users] Mail Processing Problem?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm beginning to think it would have been easier to just start all over if I didn't care about my users getting upset. Anyway I still seem to have a problem that I didn't have before the restore. Since I don't know what is supposed to happen during processing I guess all I can do is guess. When I send a request to one on my lists (list name-request) the smtp log shows an error. The request gets processed at least is it piped tp the mailman request command, and then seems to get sent to list name.-bounces. The problem is that it tries to send it via hostname.domain.com which my SMTP server tries to send to my ISPs mail host. The mail is summarily rejected. I THINK it should be going to list name[EMAIL PROTECTED] instead. In any case what is supposed to be happening here and why it is trying to send it to bounces? Thanks. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFHhDd5/fiWYqZ2tVQRAmk0AKDr1imvUneQss8LBeJbQgPY5N4/jgCg5Lbb Idni+N3JvGBx4icMgjxwjgQ= =t95N -END PGP SIGNATURE- -- 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] Restoring Lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 At 07:17 AM 1/9/2008, you wrote: ??? Are you mixing in your replies with the quoted text here without distinuguishing the quoted text? That is VERY confusing, and will get your posts bit-canned by a lot of people, just fyi... That's odd. The text appears quoted when I am creating the reply. It must somehow be stripped when sent. I'll have to see what is going on. Thanks for the heads up and my apologies to the list. - -- Best regards, Charles Marcus I.T. Director Media Brokers International 678.514.6200 x224 678.514.6299 fax -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFHhVnv/fiWYqZ2tVQRAnH7AJoCpc162Hdn3pJwZDhxxI63/SAhNgCePT3o o+D1VssS90ad2eqjwe+kO/E= =3SIp -END PGP SIGNATURE- -- 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] Mail Processing Problem?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thanks for the reply. No. I do not have a static IP or a registered domain, which is why all mail from this server has to go through my ISP's server. However, non-mailman mail is sent just fine. If it is indeed the MAIL FROM then why would my changes in mm_cfg.py, not have fixed it? On the other hand, why would it complain about 'RCPT TO' rather then 'MAIL FROM'? At 02:38 PM 1/10/2008, you wrote: RCPT TO is the SMTP command for specifying the recipient(s) of the message. These will be the addresses of the list members or the owner/moderator or other recipient of a Mailman generated notice. I do not thing that is what the ISP's MTA is complaining about. I thing it returns whatever reject status it is returning in response to a RCPT TO command, but that doesn't mean it is complaining about the recipient address. I believe what it doesn't like is the MAIL FROM address - i.e. the [EMAIL PROTECTED] address. Is your list's host_name in DNS? - -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (MingW32) iD8DBQFHhpgQ/fiWYqZ2tVQRAiOiAKCZt1L6wcPut5WyOTGxYGvSoUT73QCeOYFD l48NO6KUihIevmqal//eeMU= =G09E -END PGP SIGNATURE- -- 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] Mail Processing Problem?
Thanks for the reply. I have a guess as to what is wrong but I don't know how to fix it in mailman. Here are the syslog entries for a non-mailman email: Jan 12 10:55:10 dap002 postfix/qmgr[2345]: 47CD185063: from=[EMAIL PROTECTED], size=435, nrcpt=1 (queue active) Jan 12 10:55:16 dap002 postfix/smtp[21572]: 47CD185063: to=[EMAIL PROTECTED], relay=mail.bellsouth.net[204.127.217.17]:25, delay=5.8, delays=0.05/0.02/5.5/0.28, dsn=2.0.0, status=sent (250 ok ; id=20080112155515H0100n202se) Jan 12 10:55:16 dap002 postfix/qmgr[2345]: 47CD185063: removed Note the from hostname is 'home.bellsouth.net'. Now the mailman entries: Jan 12 10:56:12 dap002 postfix/qmgr[2345]: D4F7D85061: from=[EMAIL PROTECTED], size=10015, nrcpt=1 (queue active) Jan 12 10:56:12 dap002 postfix/smtpd[21582]: disconnect from dap002[127.0.0.1] Jan 12 10:56:16 dap002 postfix/smtp[21572]: D4F7D85061: to=[EMAIL PROTECTED], relay=mail.bellsouth.net[207.115.11.17]:25, delay=3.5, delays=0.03/0.01/3.3/0.19, dsn=5.0.0, status=bounced (host mail.bellsouth.net[207.115.11.17] said: 550 [PERMFAIL] bellsouth.net requires valid sender domain (in reply to RCPT TO command)) Here the from hostname is 'dap002.bellsouth.net' instead of 'home.bellsouth.net', that is not to say I know this is the problem but its all I can see as different. Obviously mailman is somehow overriding the normal from hostname and building its own. The name 'dap002' is the LAN hostname but I cannot use that as the from address to my ISP. My ISP has a special hostname for situations like this that will properly resolve via DNS although it is a dummy name for all DHCP assigned IPs. My mm_cfg.py has these 2 lines referring to the hostname but obviously they are not what is being used in this case: DEFAULT_EMAIL_HOST = 'home.bellsouth.net' DEFAULT_URL_HOST = 'home.bellsouth.net' -- 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] Mail Processing Problem?
At 05:58 PM 1/12/2008, you wrote: Well, if the hostname really was home.bellsouth.net, that would map to IP address 216.77.188.41, but the reverse DNS for this IP address points back to dsl.bellsouth.net, which does map correctly back to the same IP address. So, I would not be surprised to see home.bellsouth.net changed to dsl.bellsouth.net in your outgoing mail. As I said later, that is a special name set up by the ISP for just this type situation. Certainly, the name dap002.bellsouth.net does not exist in the DNS. If this is what your system is trying to use to identify itself to the outside world, that would be a problem. Only mailman is trying to use that name. I suspect that the problem you're having may be a hostname or MTA misconfiguration issue, which Mailman is not involved in, and which cannot be fixed within Mailman. If that we the case, why is it only mailman sending mail that is effected? As I demonstrated, when using the 'mail' command, everything is fine. Try typing the command hostname at the command-line prompt on the machine. Also check your MTA configuration to make sure that this is not being over-ridden. There is no MTA setting that would effect mailman and nothing else that I can find? Any suggestions? If you made these changes after the list was created, then they will not be reflected in the list configuration. I think that running fix_url will do that for you, but you'll have to check the FAQ Wizard or the archives of the list to be sure. Keep in mind this was a working system that started giving me trouble after a restore. -- 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] Mail Processing Problem?
Success! :-D It seems I owe you another adult beverage of your choice. Thanks. Just out of curiosity, where is that parameter kept such that it did not get restored from the backup yet all the list archives and members did? At 09:44 PM 1/12/2008, you wrote: These will affect list attributes at list creation time but not subsequently. You can run fix_url to fix the list but in this case, that isn't necessary. In this case, all you need to do is go the the list admin General Options page and change Host name this list prefers for email. (host_name) from dap002.bellsouth.net to home.bellsouth.net. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan PGP.sig Description: PGP signature -- 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] Mail Processing Problem?
At 08:14 AM 1/14/2008, you wrote: Ahh... your quoting seems to be working now... now I can at least make sense of your replies without straining... Next we'll address the top-posting problem... ;) The top posting problem was temporary until I could get the quoting working right. I figured it would be less confusing that way. :-) jk... -- Best regards, Charles PGP.sig Description: PGP signature -- 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] Ghost Moderator Requests
I have a strange problem. I am getting a daily message from one of my mailing lists telling me I have 95 moderator requests pending. However, when I go to the administrator page for that mailing list it tells me there are no outstanding requests. Does anyone have any ideas what it happening? TIA. PGP.sig Description: PGP signature -- 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] Ghost Moderator Requests
At 06:10 PM 1/21/2008, you wrote: Somewhere, there is another test/backup/incompletely deleted/whatever Mailman installation that is sending these. Check the Received: headers of the message to see at which server it originates and then I'm not sure what you mean by at which server it originates. Are you talking about the server that is sending the mailman mail (i.e. the mailman server) or the server that sent the email(s) that require attention? If the latter, there is no way to tell since the message is from the mailman server. find / -name config.pck -print /var/lib/mailman/lists/mailman/mailman.pck /var/lib/mailman/lists/my real list/my real list.pck -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan PGP.sig Description: PGP signature -- 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] Ghost Moderator Requests
Thanks for the reply. At 04:07 PM 1/26/2008, you wrote: First of all, it is not clear from your prior posts whether or not you recognize that these held messages are all from the 'mailman' site list, not from your other list. Sorry I wasn't clear but yes, I knew they were from the mailman list. Also this (the 'mailman' list) list's web_page_url attribute which reflects its url host is http://dap002.dap.localnet/mailman/ which may or may not be valid, but is certainly not accessable from the internet. That is correct since I don't have a static IP. I can access the admin functions from the LAN. My users must do everything via email. Finally, these all appear to have been 'owner' bounces delivered to the site list last April 17. I can see that but I have no idea what is significant about that date since it did not show up until after I did this restore thing. If you go to the admindb interface for the 'mailman' list, you should see these messages and be able to discard them - go to the same URL as the admindb interface for your other list, but with 'mailman' as the list name. As I said, it tells me there are no pending requests. Or, you can discard them by running. path/to/mailmans/bin/discard /var/lib/mailman/data/heldmsg-mailman-* I thought I'd give this a try and here's what I get: [EMAIL PROTECTED] bin]# discard /var/lib/mailman/data/heldmsg-mailman-* Traceback (most recent call last): File /usr/sbin/discard, line 120, in ? main() File /usr/sbin/discard, line 110, in main mlist.HandleRequest(id, mm_cfg.DISCARD, '', False, False, '') File /usr/lib/mailman/Mailman/ListAdmin.py, line 164, in HandleRequest rtype, data = self.__db[id] KeyError: 113 [EMAIL PROTECTED] bin]# Must be a remnant of the restore fiasco. Do NOT just remove the heldmsg-mailman-* files since that will remove the message files, but it won't stop the notices. If you have already removed the files, you need to either go to the admindb interface for the mailman list and discard them or remove the /var/lib/mailman/lists/mailman/request.pck file which will be automatically recreated when necessary. Even though the above didn't work, can I do this anyway? I don't use that mailing list so there are no messages in it that I care about. Is there a way to just wipe everything manually? I guess this list is necessary but is there a way to wipe everything and have it rebuild what it needs? That should clean everything up, right? -- 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] Ghost Moderator Requests
At 07:28 PM 1/30/2008, you wrote: Did it? -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Sorry for not getting back to you, I've been unusually busy. Yes, it did. Thanks. PGP.sig Description: PGP signature -- 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] Problem Migrating Mailman to New Server
I am installing a replacement server and am having trouble migrating Mailman. The installation works but none of my lists show up when I use the browser interface. However, when I run 'list_lists' from the command line they are there. Is this a config issue with just the HTML interface or is there something else fundamentally wrong? I thought I just needed to do a simple copy of the /var/lib/mailman directory to the new server but perhaps there is more to it then that. TIA. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Mark Sapiro wrote: Dennis Putnam wrote: I am installing a replacement server and am having trouble migrating Mailman. The installation works but none of my lists show up when I use the browser interface. However, when I run 'list_lists' from the command line they are there. Is this a config issue with just the HTML interface or is there something else fundamentally wrong? See the FAQ at http://wiki.list.org/x/lYA9. Thanks for the reply but I've already been there. That does not seem to be my problem. All the config files were copied from the working server as is (the mm_cfg.py file is correct). The new server has exactly the same hostname and IP address. The only (intentional) difference, other then the hardware, is the underlying OS (Mandriva Free 2007 Spring replacing Mandriva 2007). I suppose it is possible that this version of Mandriva put the Mailman files someplace different then the previous version (why it doesn't follow the standard is beyond me) but so far I have not found any other location with config files. I think Mailman needs a command that lists all the file paths it is using. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Mark Sapiro wrote: Dennis Putnam wrote: Mark Sapiro wrote: Can you go successfully go to a http://www.example.com/mailman/listinfo/listname page for a known listname even though it doesn't appear on the overview. If not, I think your web server is pointing at the wrong place. OK, now we are making progress. Thanks. I can indeed see the list if I supply the list name in the link like you suggested. I guess that means the scriptalias is correct so the question now becomes, why do they not show up on the admin or listinfo links? Does this also mean if I start mailman it will work in spite of the incorrect web interface? Yes, Mailman will probably work if you start it as long as aliases or whatever is required for mail delivery to the list are in place. As far as lists missing from the listinfo overview, we are back to the FAQ at http://wiki.list.org/x/lYA9. Assuming the lists are public (Privacy options... - advertised = Yes), the list doesn't appear on the overview because VIRTUAL_HOST_OVERVIEW = On (the default), and the host portion of the list's web_page_url attribute does not exactly match the host portion of the URL used to access the page. Perhaps you had VIRTUAL_HOST_OVERVIEW = Off in mm_cfg.py on the old server and didn't carry it over. Or, perhaps you changed it in Defaults.py on the old server; if so, this is why you shouldn't do that. I'm making some progress as the problems so far seem to be ownerhip and permissions since the copy had to be done as root. I could not find anything that tells me what the group and owner should be for each associated directory but I think I have them all set to mailman:mail. Now I am getting this error from postfix: status=bounced (Command died with status 2: /usr/lib/mailman/mail/mailman post mailman. Command output: Group mismatch error. Mailman expected the mail wrapper script to be executed as group mail, but the system's mail server executed the mail script as group mailman. Try tweaking the mail server to run the script as group mail, or re-run configure, providing the command line option `--with-mail-gid=mailman'. ) Oct 20 19:25:15 dap002 postfix/qmgr[27883]: 9D0D819835: removed Oct 20 19:25:20 dap002 postfix/smtp[28602]: 202FF19836: to=[EMAIL PROTECTED], relay=mail.bellsouth.net[207.115.11.17]:25, delay=6.8, delays=0.01/0.01/3.2/3.6, dsn=2.0.0, status=sent (250 ok ; id=20081020232532H05001u3qhe) Oct 20 19:25:20 dap002 postfix/qmgr[27883]: 202FF19836: removed I don't think I understand what to do at this point. Everything other then what I copied was set per the Mandriva installer. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
That advanced the ball. The problem was that the mailman's primay group was mailman (Mandriva automagically creates a primary group for each user with the same name as the user name, that has been a problem more than once). I changed the primary group to mail. Thanks. However, I am now getting permission denied errors on the database folders. IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.2271.2' I ran check_perms and all is OK. This has always been about ownership/permissions but I question why check_perms doesn't/won't fix it. What is it supposed to be? FWIW, the owner:group for /usr/lib/mailman and /var/lib/mailman trees is mailman:mail. I should also note that the command (it was just a help command to req) did work but I did not want to try actually mailing something to a list until this is all fixed. Thanks again for your help and my ISP seems to be accepting email from the python.org domain again. Mark Sapiro wrote: Where are your aliases? The mail wrapper is compiled to to expect to be invoked by the 'mail' group. Postfix will invoke the wrapper as the user and that user's primary group corresponding to the owner of the aliases.db file in which the pipe command was found. I.e., if the aliases.db file is userx:groupy, postfix will invoke the wrapper as userx:groupx where groupx is userx's primary group. -- Mark Sapiro mark at msapiro.net http://mail.python.org/mailman/listinfo/mailman-usersThe 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://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Mark Sapiro wrote: Prior to 2.1.10, check_perms had a bug and didn't check the owner and group permissions on the archives/private directory itself. Permissions should be 2771 or maybe 2770 (drwxrws--x or drwxrws---). If archives/private is not o+x, it needs to be owned by the web server for public archive URLs to work. I changed it to 2771 (I just needed too do a chmod o-r). Subordinate directories should be 2775 (drwxrwsr-x) and subordinate files 0664 (-rw-rw-r--) except for the archives/private/*/database/ directory and subordinate files which should not have 'other' permissions. OK, this is confusing. The public archive directories are links (lrwxrwxrwx) to the private archive directories which contain the actual archives. Those directories are drwxrwsr-x. The files are 755. It is not clear to my why a help command to the -request address would try to lock the archive. Is (was) 2271 the pid of CommandRunner? No, it is 2273. I'm not sure I understand this question. The pid would depend on when qrunner was launched. I have stopped and started mailman several times so the pid could be anything, couldn't it? signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problem Migrating Mailman to New Server
Mark Sapiro wrote: OK, this is confusing. The public archive directories are links (lrwxrwxrwx) to the private archive directories which contain the actual archives. Those directories are drwxrwsr-x. The files are 755. If the files are 755, that's OK, but they aren't executable so they really should be 644. Sorry. They are indeed 644. Brain was out to lunch. Yes, that's why I said (was). However, if CommandRunner is now 2773, it is likely that 2771 is another runner and was at the time. In any case, 2771 was the pid of the process that tried to create the lock. I asked, because I don't believe that the IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.2271.2' error came from your 'help' command mailed to -request. In any case, where did this error come from?. If it is in Mailman's error log, there should also be a traceback. What is that? OK, now I understand what you are asking. I restarted mailman and let it run for several minutes with no error in /var/log/mailman/error. Then I submitted a help to -request. That is when the error occurred. I suppose it might mot be the help request per se but rather anything that causes mailman to do something. I tried to run a couple of other commands and they all do the same thing. I am reluctant to actually send a test to the list out of fear it might destroy something and make matters worse. Here is the traceback. Oct 24 17:30:09 2008 (5961) Uncaught runner exception: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' Oct 24 17:30:09 2008 (5961) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose mlist.ArchiveMail(msg) File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 216, in ArchiveMail h.processUnixMailbox(f) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 580, in processUnixMailbox self.add_article(a) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 632, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 664, in get_parent_info article.subject) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 311, in getOldestArticle self.__openIndices(archive) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 251, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 61, in __init__ self.lock() File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 77, in lock self.lockfile.lock() File /usr/lib/mailman/Mailman/LockFile.py, line 243, in lock self.__write() File /usr/lib/mailman/Mailman/LockFile.py, line 422, in __write fp = open(self.__tmpfname, 'w') IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1' Oct 24 17:30:09 2008 (5961) SHUNTING: 1224883807.7050669+416c5717ff6f07bcc5748843bf07afb92dc4b212 Here is the process (shouldn't this be running as 'mailman'?): mail 5961 0.1 0.7 11100 7356 ?R17:28 0:00 /usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s Thanks for your patience and continued help. signature.asc Description: PGP signature signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Changing a user's email address
Suppose I have a user that changes his email address and I don't want to wait for that user to confirm the address change? How do I change the address of any user simply as the list admin with no involvement of the list member? Thanks. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Configure Repy-To header for confirmations
I am having a problem getting the reply-to header configured for confirmations. Due to some email restrictions from my ISP I cannot use the default (i.e. [EMAIL PROTECTED]). Thus when a user tries to reply to a confirmation, it bounces (it needs to be [EMAIL PROTECTED]).I can't find this in the documentation (probably because my reply-to search key word keeps yielding user reply information not mailman generated reply-to forms). How to I configure the reply-to header for confirmations. Do I need to customize the form itself? Thanks. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Configure Repy-To header for confirmations
Thanks for the reply. OK, to be clear the problem is one of mailbox name length. Another list member replied privately and questioned that so I will repost that information here. The number characters in my list name plus the '-request' is 6 characters too many. I could change the list names but that would be too much effort for list members most of which are computer illiterate. These lists have been around for several years. The need for confirmations simply has not come up until now. It probably never worked from the beginning. It has been so long since I set these up I'm not sure I remember how (IIRC, that can be set on a list-by-list basis from the web interface) but obviously this is different. Perhaps I should have pointed that out in the original question but I didn't think it was really relevant. That being said, using list-confirm is still that same length. As for what needs to be munged, I think only the confirmation message. My list members don't use anything else and probably wouldn't know how anyway. In all the years these lists have been active, this is the first time someone had to change their email address so it is the first time a confirmation was needed. I was not aware this was going to be a major effort. Be aware that, although I am experienced with many various languages (scripting and otherwise), python is not among them. Mark Sapiro wrote: Dennis Putnam wrote; I am having a problem getting the reply-to header configured for confirmations. Due to some email restrictions from my ISP I cannot use the default (i.e. [EMAIL PROTECTED]). Thus when a user tries to reply to a confirmation, it bounces (it needs to be [EMAIL PROTECTED]).I can't find this in the documentation (probably because my reply-to search key word keeps yielding user reply information not mailman generated reply-to forms). How to I configure the reply-to header for confirmations. Do I need to customize the form itself? Thanks. Can you use [EMAIL PROTECTED] or does that have to be munged too? If you can use it, set VERP_CONFIRMATIONS = Yes in mm_cfg.py and restart Mailman. If the list-confirm address is munged too, you will have to modify the definitions of the getListAddress() and GetConfirmEmail() methods in Mailman/MailList.py to return the addresses you use. Also, if you are concerned about the site (mailman) list, you need to modify the get_site_email() function in Mailman/Utils.py. If you need help with these mods, post again and indicate which of the nine list-... addresses need to be munged and to what. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Configure Repy-To header for confirmations
Mark Sapiro wrote: Still, if you can use VERP_CONFIRMATIONS, it would make the code modifications simpler because of the way the address is generated. The difference is without VERP_CONFIRMATIONS, the message is From: [EMAIL PROTECTED] with Subject: confirm xx... and with VERP_CONFIRMATIONS it is From [EMAIL PROTECTED] with Subject: Your confirmation is required to ... Of course, if the local part suffix is included in the length restriction, this only makes it worse and can't be used. Since I don't know what the implications of VERP_CONFIRMATIONS are, I have reason to not try it. :) The length restriction is on the mailbox name or rather the user name (everything that precedes the '@'). Does the munging need to be done for all lists in the installation? Is it done in the same way for each list? I.e. is list-request always mapped to listreq or does the mapping vary depending on list. Can the mapping be deduced programmatically, or would it have to be looked up in a table? Actually no. There is only 1 list that otherwise exceeds this limit. The mapping can be deduced programmatically. It is simply the list name prepended to 'req' rather than prepended to '-request'. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Configure Repy-To header for confirmations
Mark Sapiro wrote: Dennis Putnam wrote: The implication is exactly what I said above. The aditional implication is that a reply which is addressed to [EMAIL PROTECTED] has to be delivered the same as if it were addressed to [EMAIL PROTECTED] Then that won't work either. Since Mailman doesn't use mailbox delivery, why do you have an issue with these names at all? I don't have a static IP. I have to create mailboxes on my ISP's server. Then use fetchmail to retrieve the messages. This means the mailbox has to be pre-defined to my ISP then I have fetchmail map that to the actual list mailbox in mailman. I'm not convinced you even need to do this. How does your MTA actually deliver to Mailman? The MTA that delivers to mailman is postfix but as I said above, the issue is that I have to use fetchmail. As far as mailman is concerned it is indeed going to list-request so the actual address used by list members is transparent to mailman. That is why I need to munge the Reply-To header for confirmations. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Configure Repy-To header for confirmations
Mark Sapiro wrote: The attached MailList.patch.txt patch (with an appropriate value for MAGIC_LENGTH) or something like it should do what you want for the -request address. The attached MailList.patch2.txt patch is a slight modification that handles substituting listabc for list-abcdef for any abcdef. Thanks but I'm afraid I have to let my ignorance show. Do I use both and how do I incorporate/install these? signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Configure Repy-To header for confirmations
Thanks for all this effort. I chose MailList.patch2.txt. Unfortunately I did get errors: patching file ./MailList.py Hunk #1 FAILED at 75. Hunk #2 FAILED at 190. 2 out of 2 hunks FAILED -- saving rejects to file ./MailList.py.rej Note that there is no file ./MailList.py.rej. All I changed (intentionally) was the 10 to a 13. I've attached the patch file just in case I inadvertently messed something up. Mark Sapiro wrote: You use one or the other, not both. You use MailList.patch.txt if you only want to substitute listreq for list-request. You use MailList.patch2.txt if you want to substitute lisdadm for list-admin, listbou for list-bounces, etc. for all nine of the suffixes. Step one - edit the patch file to replace the 10 in +MAGIC_LENGTH = 10 with the actual list name length that makes things too long. Step two - make a backup of Mailman/MailList.py Step three - patch --dry-run /path/to/Mailman/MailList.py /path/to/the/patch/file (see 'man patch' for more info) Depending on your Mailman version, you may see one or two Hunk #n succeeded at offset... messages from step 3. These are OK, but any other messages from step 3 after the patching file ... message may indicate a problem, so stop and post the error(s) Step four - If no errors at step 3 patch /path/to/Mailman/MailList.py /path/to/the/patch/file Step 5 - restart Mailman. --- c:/test-mailman-2.2/Mailman/MailList.py 2008-08-22 15:48:58.5 -0700 +++ c:/test-mailman/Mailman/MailList.py 2008-11-02 21:49:50.447344300 -0800 @@ -75,6 +75,8 @@ EMPTYSTRING = '' OR = '|' +# The magic listname length beyond which list-request becomes listreq +MAGIC_LENGTH = 13 try: True, False @@ -188,6 +190,8 @@ def getListAddress(self, extra=None): if extra is None: return '[EMAIL PROTECTED]' % (self.internal_name(), self.host_name) +if len(self.internal_name()) MAGIC_LENGTH: +return '[EMAIL PROTECTED]' % (self.internal_name(), extra[:3],self.host_name) return '[EMAIL PROTECTED]' % (self.internal_name(), extra,self.host_name) # For backwards compatibility -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Relative Admin URLs
I read some threads on producing relative URLs for the admin pages but it seemed like there is a bug/hole and I did not find any closure on it. Has that issue been resolved and if so how do I configure mailman to generate relative URLs rather than absolute? Thanks. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] List Distribution Sequence Confusion
I am having a problem when mailman (2.1.9) tries to distribute mail. My main problem is that I do not understand what it is doing. I do not have a static IP and I have to relay outgoing mail through my ISP's server. Thus there was a lot of fudging of the configuration to make it work thanks to help from this list. When I try to send mail to a list it seems to be trying to mail it to listname-boun...@fakehost.mydomain.com. As result I get this this message from my ISP's server, not unexpectedly: 550 [PERMFAIL] destination not valid within DNS (in reply to RCPT TO command)) I don't understand why it is sending mail there instead of to the members of the list. What am I doing wrong? FWIW, this was a working system prior to upgrading my Mandriva OS to 2008.1 so lots of things were changed. I can't say what specifically so this is almost like starting from scratch even though I copied all the config files from the working system. Thanks. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Relative Admin URLs
Hi Mark,
Thanks. I added the patch but is there a config parameter I need to set
to make it work? If not I cannot see any difference.
Mark Sapiro wrote:
Dennis Putnam wrote:
I read some threads on producing relative URLs for the admin pages but
it seemed like there is a bug/hole and I did not find any closure on it.
Has that issue been resolved and if so how do I configure mailman to
generate relative URLs rather than absolute? Thanks.
It's a bug. It has not been fixed to date, but it will be for the next
release. The following patch will fix it.
=== modified file 'Mailman/Utils.py'
--- Mailman/Utils.py2008-12-05 23:08:41 +
+++ Mailman/Utils.py2008-12-30 00:23:28 +
@@ -266,7 +266,7 @@
fullpath = os.environ.get('SCRIPT_NAME', '') + \
os.environ.get('PATH_INFO', '')
baseurl = urlparse.urlparse(web_page_url)[2]
-if not absolute and fullpath.endswith(baseurl):
+if not absolute and fullpath.startswith(baseurl):
# Use relative addressing
fullpath = fullpath[len(baseurl):]
i = fullpath.find('?')
signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Incoming Mail Going to Wrong List ( was: List Distribution Sequence Confusion)
I have more information on this that explains why I was confused about the sequence of events for processing mail to a list. It is not going to listname-bounces but rather going to mailman-bounces. The message is addressed to listn...@mydomain.com but winds up going to mail...@mydomain.com instead. Why is the wrong list processing the incoming mail? How do I debug this? TIA. Dennis Putnam wrote: I am having a problem when mailman (2.1.9) tries to distribute mail. My main problem is that I do not understand what it is doing. I do not have a static IP and I have to relay outgoing mail through my ISP's server. Thus there was a lot of fudging of the configuration to make it work thanks to help from this list. When I try to send mail to a list it seems to be trying to mail it to listname-boun...@fakehost.mydomain.com. As result I get this this message from my ISP's server, not unexpectedly: 550 [PERMFAIL] destination not valid within DNS (in reply to RCPT TO command)) I don't understand why it is sending mail there instead of to the members of the list. What am I doing wrong? FWIW, this was a working system prior to upgrading my Mandriva OS to 2008.1 so lots of things were changed. I can't say what specifically so this is almost like starting from scratch even though I copied all the config files from the working system. Thanks. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Odd Behavior
signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] Odd Behavior
I'm not sure this is really a Mailman issue but at this point, I don't know where else to start. The problem stems from email to the root user. I have an alias set (postfix) to send mail for root to my administrator address. If it matters this address is in a different domain so the form of the alias is administra...@myotherdomain.com. Also, FWIW, this seems to have started when I upgraded from Mandriva 2007 to 2008.2. What is happening, is that mail to root is somehow being routed through Mailman. Each time something is sent to root, the following error email is generated: --- This is the mail system at host home.mydomain.com. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system mailman-loop:/var/lib/mailman/data/owner-bounces.mbox@home.mydomain.com (expanded from root): unknown user: mailman-loop:/var/lib/mailman/data/owner-bounces.mbox mailman:|/usr/lib/mailman/mail/mailman post mailman@home.mydomain.com (expanded from root): unknown user: mailman:|/usr/lib/mailman/mail/mailman post mailman mailman-admin:|/usr/lib/mailman/mail/mailman admin mailman@home.mydomain.com (expanded from root): unknown user: mailman-admin:|/usr/lib/mailman/mail/mailman admin mailman mailman-bounces:|/usr/lib/mailman/mail/mailman bounces mailman@home.mydomain.com (expanded from root): unknown user: mailman-bounces:|/usr/lib/mailman/mail/mailman bounces mailman mailman-confirm:|/usr/lib/mailman/mail/mailman confirm mailman@home.mydomain.com (expanded from root): unknown user: mailman-confirm:|/usr/lib/mailman/mail/mailman confirm mailman mailman-join:|/usr/lib/mailman/mail/mailman join mailman@home.mydomain.com (expanded from root): unknown user: mailman-join:|/usr/lib/mailman/mail/mailman join mailman mailman-leave:|/usr/lib/mailman/mail/mailman leave mailman@home.mydomain.com (expanded from root): unknown user: mailman-leave:|/usr/lib/mailman/mail/mailman leave mailman mailman-owner:|/usr/lib/mailman/mail/mailman owner mailman@home.mydomain.com (expanded from root): unknown user: mailman-owner:|/usr/lib/mailman/mail/mailman owner mailman mailman-request:|/usr/lib/mailman/mail/mailman request mailman@home.mydomain.com (expanded from root): unknown user: mailman-request:|/usr/lib/mailman/mail/mailman request mailman mailman-subscribe:|/usr/lib/mailman/mail/mailman subscribe mailman@home.mydomain.com (expanded from root): unknown user: mailman-subscribe:|/usr/lib/mailman/mail/mailman subscribe mailman mailman-unsubscribe:|/usr/lib/mailman/mail/mailman unsubscribe mailman@home.mydomain.com (expanded from root): unknown user: mailman-unsubscribe:|/usr/lib/mailman/mail/mailman unsubscribe mailman . . . Reporting-MTA: dns; home.mydomain.com X-Postfix-Queue-ID: C0B9C85073 X-Postfix-Sender: rfc822; r...@home.mydomain.com Arrival-Date: Mon, 25 May 2009 04:11:19 -0400 (EDT) Final-Recipient: rfc822; mailman-loop:/var/lib/mailman/data/owner-bounces.mbox@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: mailman-loop:/var/lib/mailman/data/owner-bounces.mbox Final-Recipient: rfc822; mailman:|/usr/lib/mailman/mail/mailman post mailman@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: mailman:|/usr/lib/mailman/mail/mailman post mailman Final-Recipient: rfc822; mailman-admin:|/usr/lib/mailman/mail/mailman admin mailman@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: mailman-admin:|/usr/lib/mailman/mail/mailman admin mailman Final-Recipient: rfc822; mailman-bounces:|/usr/lib/mailman/mail/mailman bounces mailman@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: mailman-bounces:|/usr/lib/mailman/mail/mailman bounces mailman Final-Recipient: rfc822; mailman-confirm:|/usr/lib/mailman/mail/mailman confirm mailman@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: mailman-confirm:|/usr/lib/mailman/mail/mailman confirm mailman Final-Recipient: rfc822; mailman-join:|/usr/lib/mailman/mail/mailman join mailman@home.mydomain.com Original-Recipient: rfc822; root Action: failed Status: 5.1.1 Diagnostic-Code: X-Postfix; unknown user: mailman-join:|/usr/lib/mailman/mail/mailman join mailman Final-Recipient: rfc822; mailman-leave:|/usr/lib/mailman/mail/mailman leave
[Mailman-Users] Mandriva Upgrade Woes (as Usual)
Well, as usual, my upgrade of Mandriva to v 2010.0 has broken Mailman. I once again humbly request help. Here is the traceback from 'mailmanctl start': /usr/lib/mailman/Mailman/Utils.py:32: DeprecationWarning: the sha module is deprecated; use the hashlib module instead import sha Traceback (most recent call last): File /usr/sbin/mailmanctl, line 110, in module from Mailman.MailList import MailList File /usr/lib/mailman/Mailman/MailList.py, line 51, in module from Mailman.Archiver import Archiver File /usr/lib/mailman/Mailman/Archiver/__init__.py, line 17, in module from Archiver import * File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 32, in module from Mailman import Mailbox File /usr/lib/mailman/Mailman/Mailbox.py, line 21, in module import mailbox File /usr/lib/python2.6/mailbox.py, line 19, in module import email.message ImportError: No module named message Thanks. Sigh! signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Bounce Question
Due to some long time configuration issues, which have now been resolved, I think was missing some list events. Now I have to play catchup. I am not sure how bounce processing works. Lets assume that a list member's email address goes bad. Exactly what happens to the bounced message and how does the list owner get notified? Assuming the owner missed those notifications, how can (s)he tell which users have invalid addresses? Thanks. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Bounce Question
I am really trying to reply to Barry but, as a note to the admins, Barry's message did not make it to me for some reason. If it weren't for the replies I would not have seen this. Thanks Barry. P.S. I tried to go to the veenet link but it keeps timing out. On 3/15/2011 4:41 PM, Jeff Grossman wrote: On Tue, 15 Mar 2011 11:24:25 -0500, Barry Finkel bsfin...@anl.gov wrote: On 03/15/11 09:57, Dennis Putnam wrote: Due to some long time configuration issues, which have now been resolved, I think was missing some list events. Now I have to play catchup. I am not sure how bounce processing works. Lets assume that a list member's email address goes bad. Exactly what happens to the bounced message and how does the list owner get notified? Assuming the owner missed those notifications, how can (s)he tell which users have invalid addresses? Thanks. The bounce score begins at 0.0. Each bounce (only one per day is counted) increases the score by 1.0 or 0.5 depending upon if the -bounces processing detects a soft error or hard error. Once the bounce score reaches 5.0, the subscription is set to NOMAIL, and for three successive weeks, once per week, a test mail is sent to the address asking the subscriber to re-confirm. If there is no response to these three mailings, then the address is unsubscribed. All of these parameters are configurable. The bounced mail that triggers the 5.0 score is sent to the list owners, the previous bounce messages are discarded. The unsubscribe notice is sent to the list owners. I run a report daily http://veenet.value.net/~msapiro/scripts/get_bounce_info.py that tells me for each Mailman list, each subscriber that has a bounce score greater than zero. I review the report daily to spot bad addresses. Look at the Mailman logs /var/log/mailman/bounce and maybe other logs in that directory. Are you sure about the 1.0 and 0.5 score based on soft and hard failure? I think Mark has said previously that a soft and hard bounce both get scored as 1.0. Jeff -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dap1%40bellsouth.net signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Monthly Reminder Question
What triggers the monthly reminder? I cannot find any config parameter that lets me set what day or date in each month to send it. Does this have t be done manually with a cron job? If so what is the command? signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Monthly Reminder Question
Thanks Andrew. That was what I was looking for. On 3/18/2011 7:28 PM, Andrew Hodgson wrote: Dennis Putnam wrote: What triggers the monthly reminder? I cannot find any config parameter that lets me set what day or date in each month to send it. Does this have t be done manually with a cron job? If so what is the command? It is in Cron - see the file in ~/cron/crontab.in: [...] |# 5 AM on the first of each month, mail out password reminders. |0 5 1 * * /usr/bin/python -S /usr/local/mailman/cron/mailpasswds See this section of the installation guide: http://www.gnu.org/software/mailman/mailman-install/node41.html Thanks. Andrew. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Monthly Reminder Question
Thanks for the reply. Yes, it does the same thing. Is there a debug
option for this?
On 3/20/2011 10:19 AM, Andrew Hodgson wrote:
Hi,
Have you tried it without any arguments? I just ran it on a virtual machine
here and it worked fine. I don't know much details about the program if it
should write to stderr/stdout etc.
Andrew.
-Original Message-
From: Dennis Putnam [mailto:d...@bellsouth.net]
Sent: 20 March 2011 00:01
To: Andrew Hodgson
Subject: Re: [Mailman-Users] Monthly Reminder Question
I tried running that command from CLI and while it didn't output any errors,
it also didn't produce any email that I could find. I have a test list with
just me as a member ('python -S /usr/lib/mailman/cron/mailpasswds -l
testlist'). I never received anything. Should the command write to 'stderr'
if something is wrong?
Should it write anything to 'stdout'?
On 3/18/2011 7:28 PM, Andrew Hodgson wrote:
Dennis Putnam wrote:
What triggers the monthly reminder? I cannot find any config parameter that
lets me set what day or date in each month to send it. Does this have t be
done manually with a cron job? If so what is the command?
It is in Cron - see the file in ~/cron/crontab.in:
[...]
|# 5 AM on the first of each month, mail out password reminders.
|0 5 1 * * /usr/bin/python -S /usr/local/mailman/cron/mailpasswds
See this section of the installation guide:
http://www.gnu.org/software/mailman/mailman-install/node41.html
Thanks.
Andrew.
signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Archives Link
For reasons unknown I am suddenly not at to access list archives (as admin). I ran check_perms but it found no problems and there is nothing in the logs. Can someone suggest a course of action to debug this? TIA. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archives Link
Sorry. It was half time during one of the NCCA games I was watching and in my haste I left out some details. The error is 403 with this URL: http://myhost.mydomain.com/pipermail/listname/ I've made no changes intentionally (wouldn't check_perms catch problems here). Here are the requisite directory listings: ls -l /var/lib/mailman drwxrwsr-x 4 mail mail 1024 2011-02-23 04:55 archives/ ls -l /var/lib/mailman/archives drwxrws--- 6 mail mail 1024 2011-02-23 04:55 private/ drwxrwsr-x 2 mail mail 1024 2011-02-23 04:55 public/ On 3/20/2011 10:21 PM, Mark Sapiro wrote: Dennis Putnam wrote: For reasons unknown I am suddenly not at to access list archives (as admin). I ran check_perms but it found no problems and there is nothing in the logs. Can someone suggest a course of action to debug this? TIA. To what archive URL are you going and what happens when you go there? Did you recently change the archive from public to private and still using the public (pipermail) URL? Did you recently set the archives/private/ directory o-x without setting its owner to the web server user? signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Monthly Reminder Question
Thanks for the reply. I have verified all the settings, please see embedded comments below. On 3/20/2011 10:16 PM, Mark Sapiro wrote: On 3/20/2011 5:35 PM, Dennis Putnam wrote: Thanks for the reply. Yes, it does the same thing. Is there a debug option for this? On 3/20/2011 10:19 AM, Andrew Hodgson wrote: Hi, Have you tried it without any arguments? I just ran it on a virtual machine here and it worked fine. I don't know much details about the program if it should write to stderr/stdout etc. If the site list is missing, it writes a message to stderr and logs it to Mailman's 'error' log. If a member doesn't have a password, it logs that to Mailman's 'error' log. Its empty. If any uncaught exceptions occur, it writes a traceback to stderr. Otherwise, it is silent. It was silent. It will not mail any reminders at all for a list if the list's General Options - send_reminders is No. It will not mail to a user whose Get password reminder email for this list? option is no. Both are set to yes. Otherwise, it will generate the mail and queue it in the virgin queue, and if VirginRunner, IncomingRunner and OutgoingRunner are all running and there is no error (logged in Mailman's error log) the mail will be sent. They are all running. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Monthly Reminder Question
On 3/21/2011 8:38 PM, Mark Sapiro wrote: On 3/21/2011 6:20 AM, Dennis Putnam wrote: On 3/20/2011 10:16 PM, Mark Sapiro wrote: If the site list is missing, it writes a message to stderr and logs it to Mailman's 'error' log. If a member doesn't have a password, it logs that to Mailman's 'error' log. Its empty. If any uncaught exceptions occur, it writes a traceback to stderr. Otherwise, it is silent. It was silent. It will not mail any reminders at all for a list if the list's General Options - send_reminders is No. It will not mail to a user whose Get password reminder email for this list? option is no. Both are set to yes. Otherwise, it will generate the mail and queue it in the virgin queue, and if VirginRunner, IncomingRunner and OutgoingRunner are all running and there is no error (logged in Mailman's error log) the mail will be sent. They are all running. Just to be sure, check qfiles/virgin/ for any message entries (.pck files). That directory is empty. Also check Mailman's smtp log for the time you ran cron/mailpasswds. There should be an smtp to mailman for 1 recips entry for each reminder sent. Yes, its there. If there aren't any, check the smtp-failure log. If there are smtp log entries, check the MTA logs. The only SMTP log that has anything in it is the info log (error and warning are both empty). I guess that makes sense when everything is working, Postfix-wise. However, I think I see the message, if it is from listname-bounces. The problem is, I don't see who it is to (I think I may have the Postfix logging set wrong) so I don't know for sure if it really is the message and there is no indication it was sent, just removed. Also, check the spam/junk folders of the recipients. That is always the first place I check for missing email. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Monthly Reminder Problem
I started this thread some time ago and got to the point where I was able to trace things to Postfix and ultimately found where the message was apparently sent to my ISP. May 5 06:34:41 dap002 postfix/smtpd[3674]: connect from dap002[127.0.0.1] May 5 06:34:41 dap002 postfix/smtpd[3674]: E904B2001: client=dap002[127.0.0.1] May 5 06:34:41 dap002 postfix/cleanup[3677]: E904B2001: message-id=mailman.0.1304591680.3673.mail...@bellsouth.net May 5 06:34:41 dap002 postfix/qmgr[2599]: E904B2001: from=mailman-boun...@bellsouth.net, size=1833, nrcpt=1 (queue active) May 5 06:34:41 dap002 postfix/smtpd[3674]: disconnect from dap002[127.0.0.1] May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 220 isp.att.net - Maillennium ESMTP/MULTIBOX frfwmhc04 #3 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: EHLO home.bellsouth.net May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-isp.att.net May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-7BIT May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-8BITMIME May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-DSN May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-HELP May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-NOOP May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-PIPELINING May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-SIZE 26214400 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250-VERS V05.40c++ May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 XMVP 2 May 5 06:34:42 dap002 postfix/smtp[3678]: server features: 0x900f size 26214400 May 5 06:34:42 dap002 postfix/smtp[3678]: Using ESMTP PIPELINING, TCP send buffer size is 4096 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: MAIL FROM:mailman-boun...@bellsouth.net SIZE=1833 May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: RCPT TO:d...@bellsouth.net ORCPT=rfc822;d...@bellsouth.net May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: DATA May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 ok May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 ok May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 354 ok May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: . May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: QUIT May 5 06:34:42 dap002 postfix/smtp[3678]: mail.bellsouth.net[204.127.217.17]:25: 250 ok ; id=20110505103442H040014q56e May 5 06:34:42 dap002 postfix/smtp[3678]: E904B2001: to=d...@bellsouth.net, relay=mail.bellsouth.net[204.127.217.17]:25, delay=1, delays=0.05/0.06/0.61/0.3, dsn=2.0.0, status=sent (250 ok ; id=20110505103442H040014q56e) May 5 06:34:42 dap002 postfix/smtp[3678]: name_mask: resource May 5 06:34:42 dap002 postfix/smtp[3678]: name_mask: software May 5 06:34:42 dap002 postfix/qmgr[2599]: E904B2001: removed As you can see, it appears everything is working properly as far as Postfix is concerned. However, my ISP never delivers the email to the recipient. All other mail to/from my mailing lists work and are successfully delivered including welcome messages, etc. This means to me (unless someone can think of something else) that the reason my ISP is not delivering the mail is because it is finding something unique in this particular email that does not exist in all others. There is no bounced message from the ISP so it must be throwing it into the bit bucket for some reason and I am not getting even a hint as to what is wrong. Can someone think of what is unique about these messages from all the others mailman generates? I doubt it is anything in the body so it seems it has to be something in the headers. The only straw I can grasp is perhaps the from address. 'Mailman-bounces' does not exist but is that not the from address of all mailman generated messages? Thanks. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Monthly Reminder Problem
Thanks for the help. Should we take this off list, since this seems unique, or do you think the list would be interested? On 5/10/2011 9:15 AM, Ralf Hildebrandt wrote: * Dennis Putnam d...@bellsouth.net: I have gotten some feedback from my list members. It seems no one got the message although the log shows they all were accepted by my ISP. I'm stuck. So you'll have to got the bcc route and find out WHAT PHRASE EXACTLY causes the mail to be stuck. I can help, since I find this highly interesting :) On 5/10/2011 5:08 AM, Ralf Hildebrandt wrote: * Dennis Putnam d...@bellsouth.net: As a followup, there is something definitely weird going on but I am pretty sure it is not a mailman problem per se. I am still waiting for some feedback from my list members but it appears that the problem is my own email address. Very very odd. Meaning you're the only person NOT to receive the mails? I can and do get other messages as both the list owner and a member but not this particular one. However, as I said before, the message is definitely being accepted by my ISP's mail server. This is probably going to be one of those unsolvable problems with my ISP unless there are other list members that did not receive the reminder. Thanks for your help. On 5/5/2011 10:05 AM, Ralf Hildebrandt wrote: Well, you can use: recipient_bcc_maps = hash:/etc/postfix/recipient_bcc_maps containing d...@bellsouth.net someaccount@localhost then postmap /etc/postfix/recipient_bcc_maps which would then deliver a copy of EVERY mail sent to d...@bellsouth.net in copy to someaccount@localhost O! You meant in Postfix. I thought you were talking about mailman. Interesting idea, I'll give it a try. All you THEN have to do is to coax mailman into actually sending such a mail :) Once you have a copy of the faulty mail at the mailbox for someaccount@localhost you can always do stuff like: cat themail.txt | sendmail -i -f mailman-boun...@bellsouth.net d...@bellsouth.net Another good idea I didn't think of that I can try with any text. That would at least confirm if from is the culprit. You can then use an editor to remove portions from, the email UNTIL it arrives at bellsouth! Thanks for the suggestions. I'll try them and get back if nothing definitive shows up. Just let me know if you encounter any problems. I find this highly interesting :) signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Minimal Mailboxes Question
Due to various reasons, I had to change my site name from 'mailman' to something else. It is not clear from the documentation what mailboxes are really required. The site list is not used for anything other than processing reminders and other administrative functions. What I need to know is what names are required for proper function. I am limited by my ISP to the number of subaccounts I can have so I can't have more than the absolute essentials. For a regular mailing list I have the following mailboxes: name name-owner name-confirm name-join name-leave name-request For the site list I have: sitename-owner sitename-bounces For the most part this seems to be working under normal circumstances. What happens to mail from the regular list that bounces? Do I need name-bounces or does it go to sitename-bounces? Are these mailboxes sufficient or do I need others (I can add a maximum of 2 more) particularly when something goes wrong. It seems like my problem area is when something bad happens, I don't get notified. That is the reason I had to change my site name so I can retrieve bounces. TIA. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] mailpasswds error
I am still struggling to get my monthly password reminder working. I had to change the site list from 'mailman' to 'dapmm' in order to create acceptable site mailbox names for my ISP. However, now when I run 'mailpasswds -l listname I get this error: Site list is missing: dapmm Obviously I am still missing a piece of the puzzle. The only change I made was MAILMAN_SITE_LIST='dapmm' to mm_cfg.py. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailpasswds error
Thanks for the reply. As usual, nothing is that simple. I tried to create the list 'dapmm' and got this: Jul 01 13:06:07 2011 admin(7032): admin(7032): [- Mailman Version: 2.1.13 -] admin(7032): [- Traceback --] admin(7032): Traceback (most recent call last): admin(7032): File /usr/lib/mailman/scripts/driver, line 112, in run_main admin(7032): main() admin(7032): File /usr/lib/mailman/Mailman/Cgi/create.py, line 56, in main admin(7032): process_request(doc, cgidata) admin(7032): File /usr/lib/mailman/Mailman/Cgi/create.py, line 191, in process_request admin(7032): urlhost=hostname) admin(7032): TypeError: Create() got an unexpected keyword argument 'urlhost' admin(7032): [- Python Information -] admin(7032): sys.version = 2.6.5 (r265:79063, May 20 2011, 13:23:49) [GCC 4.4.3] admin(7032): sys.executable = /usr/bin/python admin(7032): sys.prefix = /usr admin(7032): sys.exec_prefix = /usr admin(7032): sys.path= /usr admin(7032): sys.platform= linux2 admin(7032): [- Environment Variables -] I didn't include all the environment stuff because of the data it contains but if a specific variable is needed, let me know and I will post it. On 7/1/2011 11:56 AM, Mark Sapiro wrote: On 7/1/2011 8:27 AM, Dennis Putnam wrote: I am still struggling to get my monthly password reminder working. I had to change the site list from 'mailman' to 'dapmm' in order to create acceptable site mailbox names for my ISP. However, now when I run 'mailpasswds -l listname I get this error: Site list is missing: dapmm Obviously I am still missing a piece of the puzzle. The only change I made was MAILMAN_SITE_LIST='dapmm' to mm_cfg.py. Apparently you also neglected to restart Mailman or you would have gotten the same error there. You have changed the name of the site list, but you haven't created a list with the new name. Your old 'mailman' list is no longer the site list. You can delete it and create a new 'dapmm' site list or rename the 'mailman' list to 'dapmm' per http://wiki.list.org/x/mYA9, or if for some reason you want to keep the 'mailman' list, that's OK, but you must have a site list and it's name is now 'dapmm', so you need to create it. Then, restart Mailman. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailpasswds error
Thanks. Mandrivia strikes again. I guess I need figure out how to upgrade to 2.1.14. On 7/1/2011 3:15 PM, Mark Sapiro wrote: Dennis Putnam wrote: Thanks for the reply. As usual, nothing is that simple. I tried to create the list 'dapmm' and got this: Jul 01 13:06:07 2011 admin(7032): admin(7032): [- Mailman Version: 2.1.13 -] admin(7032): [- Traceback --] admin(7032): Traceback (most recent call last): admin(7032): File /usr/lib/mailman/scripts/driver, line 112, in run_main admin(7032): main() admin(7032): File /usr/lib/mailman/Mailman/Cgi/create.py, line 56, in main admin(7032): process_request(doc, cgidata) admin(7032): File /usr/lib/mailman/Mailman/Cgi/create.py, line 191, in process_request admin(7032): urlhost=hostname) admin(7032): TypeError: Create() got an unexpected keyword argument 'urlhost' It appears that your /usr/lib/mailman/Mailman/Cgi/create.py script is from Mailman 2.1.14 and your base Mailman version including /usr/lib/mailman/Mailman/MailList.py is 2.1.13. These are not compatible. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailpasswds error
It turns out the RPM for 2.1.14 is not available yet for 2010. However, I reinstalled 2.1.13 and created the new list. Now I am on to the next layer of the onion. # ./config_list -i file dapmm breal_name/b attribute not changed! It must differ from the list's name by case only. On 7/1/2011 3:47 PM, Mark Sapiro wrote: Dennis Putnam wrote: Thanks. Mandrivia strikes again. I guess I need figure out how to upgrade to 2.1.14. You could try bin/newlist. That might work. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailpasswds error
My ISP occasionally, for unknown reasons, blocks email from python.org and apparently sometimes to python.org. Since I did not get a reply and I cannot find this in the archives, I am sending this again. If this is a double post, my apologies in advance. It turns out the RPM for 2.1.14 is not available yet for 2010. However, I reinstalled 2.1.13 and created the new list. Now I am on to the next layer of the onion. # ./config_list -i file dapmm breal_name/b attribute not changed! It must differ from the list's name by case only. On 7/1/2011 3:47 PM, Mark Sapiro wrote: Dennis Putnam wrote: Thanks. Mandrivia strikes again. I guess I need figure out how to upgrade to 2.1.14. You could try bin/newlist. That might work. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailpasswds error
Thanks for the reply. I ran the test message and what I got back was nothing like what you suggested. It was simply the message, in tact, as if it was a simple relay. There was nothing in the bounce log either. Obviously there is still something wrong but where do I go from here? On 7/6/2011 8:28 PM, Mark Sapiro wrote: Dennis Putnam wrote: Thanks for the reply, however I'm a little confused by it. I did indeed run 'config_list -o file mailman' first. Are you saying that the import was already done and the '-i' command is unnecessary? No. I'm saying that when you ran 'bin/config_list -i file dapmm' all the settings in 'file' were successfully applied except for the one real_name = ' Mailman' setting which you didn't want anyway. There is nothing in the Wiki article that indicated that your suggested edit is necessary. I'll update the wiki as soon as the licensing innue that prevents me from doing so at the moment is resolved. In any case I've sent the password reminder messages and they were all processed by Postfix as before. I guess now I have to see if anything comes back although I know already that the message to my own address should have arrived by now. I did verify that 'dapmm-bounces' was the 'From:' address on the outgoing messages. Did you verify the the outgoing MTA relayed the message(s)? Will I screw anything up if I send a test message to 'dapmm-bounces' and what should I expect as result? No. Assuming Bounce processing - bounce_unrecognized_goes_to_list_owner is Yes, an ordinary email test message to dapmm-bounces that doesn't look like a DSN should be forwarded to the owner address(es) of the dapmm list. In any case, there should be a message like Jul 05 10:46:31 2011 (23530) dapmm: bounce message w/no discernable addresses: message-id and if forwarding, one like Jul 05 10:46:31 2011 (23530) dapmm: forwarding unrecognized, message-id: message-id in Mailman's bounce log. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Customizing Monthly Reminder
I am trying to customize my monthly password reminder for a specific list. As I understood the documentation, in 'templates' I had to create the directory path 'lists/list name/en' and place an edited copy of 'userpass.txt' into it. However, when the monthly reminder is sent, it uses the original default text for the reminder. What am I misunderstanding about the hierarchy of customized files? TIA. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Customizing Monthly Reminder
Thanks for the reply. The information that I want to add to the monthly reminder is specific to the members of one particular list. While I guess it does not hurt to send it to all lists if I word it correctly, it would be nice to have list specific reminders. Is there a relatively simple way around this or is it hard coded? Perhaps this could be added as a feature for a future release. On 10/2/2011 10:45 PM, Mark Sapiro wrote: Dennis Putnam wrote: I am trying to customize my monthly password reminder for a specific list. As I understood the documentation, in 'templates' I had to create the directory path 'lists/list name/en' and place an edited copy of 'userpass.txt' into it. However, when the monthly reminder is sent, it uses the original default text for the reminder. What am I misunderstanding about the hierarchy of customized files? TIA. First of all, the template for monthly reminders is cronpass.txt, not userpass.txt. userpass.txt is for 'on demand' reminders, but that isn't the only issue. A second issue is list specific templates do not go in templates/lists/listname/lc/. They go in a language (en or whatever) directory in the already existing lists/listname directory (the directory that contains config.pck), but there is yet another issue. Monthly password reminders are sent from the site (mailman) list. A single reminder message includes passwords for all lists with the same host_name to which the recipient is subscribed with reminders enabled. Thus, the template is processed without a list context, and a customized cronpass.txt template placed in a list directory will not be consulted. You have to put it in templates/site/en/cronpass.txt or templates/host_name/en/cronpass.txt, and it will apply to reminders for all lists or all lists with that host_name. I have just updated the FAQ at http://wiki.list.org/x/jYA9 to mention this fact. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
As usual my attempt to update Mandriva has destroyed Mailman. This time
the update failed and rather than move forward, I reverted back to the
working version (2010.2). However, I must have missed something because
I am getting the following error when I try to access Mailman web:
Apr 28 16:07:42 2012 admin(17726):
pr 28 16:07:42 2012
admin(17726):
admin(17726): [- Mailman Version: 2.1.13 -]
admin(17726): [- Traceback --]
admin(17726): Traceback (most recent call last):
admin(17726): File /usr/lib/mailman/scripts/driver, line 97, in run_main
admin(17726): pkg = __import__('Mailman.Cgi', globals(), locals(),
[scriptname])
admin(17726): File /usr/lib/mailman/Mailman/Cgi/admin.py, line 35,
in module
admin(17726): from Mailman import MailList
admin(17726): File /usr/lib/mailman/Mailman/MailList.py, line 64, in
module
admin(17726): from Mailman import Gui
admin(17726): File /usr/lib/mailman/Mailman/Gui/__init__.py, line
25, in module
admin(17726): from Privacy import Privacy
admin(17726): File /usr/lib/mailman/Mailman/Gui/Privacy.py, line 28,
in module
admin(17726): from Mailman import GPGUtils
admin(17726): File /usr/lib/mailman/Mailman/GPGUtils.py, line 32, in
module
admin(17726): import GnuPGInterface
admin(17726): ImportError: No module named GnuPGInterface
admin(17726): sys.version = 2.7.2 (default, Dec 19 2011, 09:56:13)
[GCC 4.6.1 20110627 (Mandriva)]
admin(17726): sys.executable = /usr/bin/python
admin(17726): sys.prefix = /usr
admin(17726): sys.exec_prefix = /usr
admin(17726): sys.path= /usr
admin(17726): sys.platform= linux2
admin(17726): [- Environment Variables -]
admin(17726): SSL_VERSION_INTERFACE: mod_ssl/2.2.22
admin(17726): SSL_CIPHER_EXPORT: false
admin(17726): SSL_SERVER_S_DN_Email: ...@.net
admin(17726): SERVER_SOFTWARE: Apache/2.2.22 (Mandriva
Linux/PREFORK-0.1mdv2010.2)
admin(17726): SCRIPT_NAME: /mailman/admin
admin(17726): SSL_SERVER_A_KEY: rsaEncryption
admin(17726): SSL_SERVER_S_DN_ST: Georgia
admin(17726): SERVER_SIGNATURE: addressApache/2.2.22 (Mandriva
Linux/PREFORK-0.1mdv2010.2) Server at x..com Port 443/address
admin(17726):
admin(17726): REQUEST_METHOD: GET
admin(17726): SERVER_PROTOCOL: HTTP/1.1
admin(17726): SSL_SERVER_S_DN:
/C=US/ST=/L=x/O=x/CN=xx.xx.com/emailAddress=...@.net
admin(17726): SSL_CIPHER: DHE-RSA-CAMELLIA256-SHA
admin(17726): SSL_SERVER_V_START: Mar 18 13:32:36 2011 GMT
admin(17726): SSL_SESSION_ID:
66E6AC1408845A20EC6F56C140D2BED471A632BD7C03FC89503B0B611F1B2A18
admin(17726): SSL_CLIENT_VERIFY: NONE
admin(17726): SSL_SERVER_I_DN_ST: xxx
admin(17726): HTTP_CONNECTION: keep-alive
admin(17726): SERVER_NAME: x..com
admin(17726): REMOTE_ADDR: 74.176.153.13
admin(17726): SSL_CIPHER_ALGKEYSIZE: 256
admin(17726): SSL_SECURE_RENEG: true
admin(17726): SSL_SERVER_I_DN:
/C=US/ST=/L=x/O=x/CN=localhost/emailAddress=...@.net
admin(17726): SSL_SERVER_I_DN_C: US
admin(17726): SSL_COMPRESS_METHOD: NULL
admin(17726): SSL_SERVER_I_DN_L: Loganville
admin(17726): SSL_SERVER_I_DN_O: x
admin(17726): SSL_SERVER_M_SERIAL: 01
admin(17726): SERVER_ADDR: 192.168.0.3
admin(17726): DOCUMENT_ROOT: /var/www/html
admin(17726): SERVER_PORT: 443
admin(17726): SSL_SERVER_I_DN_Email: ...@.net
admin(17726): SSL_VERSION_LIBRARY: OpenSSL/1.0.0a
admin(17726): PYTHONPATH: /usr/lib/mailman
admin(17726): SCRIPT_FILENAME: /usr/lib/mailman/cgi-bin/admin.cgi
admin(17726): SERVER_ADMIN: mailman-ow...@xxx.net
admin(17726): SSL_SERVER_S_DN_O: x
admin(17726): SSL_SERVER_A_SIG: sha1WithRSAEncryption
admin(17726): SSL_SERVER_S_DN_L: Loganville
admin(17726): SCRIPT_URI: https://x..com/mailman/admin
admin(17726): SCRIPT_URL: /mailman/admin
admin(17726): HTTPS: on
admin(17726): SSL_SERVER_M_VERSION: 1
admin(17726): SSL_SERVER_S_DN_C: US
admin(17726): QUERY_STRING:
admin(17726): REQUEST_URI: /mailman/admin
admin(17726): HTTP_ACCEPT:
text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
admin(17726): PERL5LIB: /usr/share/awstats/lib:/usr/share/awstats/plugins
admin(17726): SSL_CIPHER_USEKEYSIZE: 256
admin(17726): HTTP_USER_AGENT: Mozilla/5.0 (Windows NT 5.1; rv:12.0)
Gecko/20100101 Firefox/12.0
admin(17726): GATEWAY_INTERFACE: CGI/1.1
admin(17726): SSL_SERVER_I_DN_CN: localhost
admin(17726): REMOTE_PORT: 4811
admin(17726): HTTP_ACCEPT_LANGUAGE: en-us,en;q=0.5
admin(17726): HTTP_DNT: 1
admin(17726): SSL_SERVER_V_END: Mar 17 13:32:36 2012 GMT
admin(17726): SSL_PROTOCOL: SSLv3
admin(17726): HTTP_HOST: x..com
admin(17726): SSL_SERVER_S_DN_CN:
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
On 4/28/2012 4:57 PM, Mark Sapiro wrote:
On 4/28/2012 1:24 PM, Dennis Putnam wrote:
As usual my attempt to update Mandriva has destroyed Mailman. This time
the update failed and rather than move forward, I reverted back to the
working version (2010.2). However, I must have missed something because
I am getting the following error when I try to access Mailman web:
Apr 28 16:07:42 2012 admin(17726):
pr 28 16:07:42 2012
admin(17726):
admin(17726): [- Mailman Version: 2.1.13 -]
admin(17726): [- Traceback --]
admin(17726): Traceback (most recent call last):
admin(17726): File /usr/lib/mailman/scripts/driver, line 97, in run_main
admin(17726): pkg = __import__('Mailman.Cgi', globals(), locals(),
[scriptname])
admin(17726): File /usr/lib/mailman/Mailman/Cgi/admin.py, line 35,
in module
admin(17726): from Mailman import MailList
admin(17726): File /usr/lib/mailman/Mailman/MailList.py, line 64, in
module
admin(17726): from Mailman import Gui
admin(17726): File /usr/lib/mailman/Mailman/Gui/__init__.py, line
25, in module
admin(17726): from Privacy import Privacy
admin(17726): File /usr/lib/mailman/Mailman/Gui/Privacy.py, line 28,
in module
admin(17726): from Mailman import GPGUtils
This import is not in standard GNU Mailman and neither is the
Mailman/GPGUtils.py module.
I wonder if the update installed this so rather than restore something,
maybe I need to delete something. But from where is this being called?
admin(17726): File /usr/lib/mailman/Mailman/GPGUtils.py, line 32, in
module
admin(17726): import GnuPGInterface
admin(17726): ImportError: No module named GnuPGInterface
I don't have a clue what needs to be restored as I didn't even know this
was using GPG.
Nor do I.
signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
Of course I did not expect this to be easy. After restoring the Mailman
directory as suggested, mailman will not start:
Traceback (most recent call last):
File /usr/sbin/mailmanctl, line 106, in module
from Mailman import mm_cfg
ImportError: Bad magic number in /usr/lib/mailman/Mailman/mm_cfg.pyc
On 4/28/2012 6:40 PM, Mark Sapiro wrote:
On 4/28/2012 3:02 PM, Dennis Putnam wrote:
On 4/28/2012 4:57 PM, Mark Sapiro wrote:
On 4/28/2012 1:24 PM, Dennis Putnam wrote:
As usual my attempt to update Mandriva has destroyed Mailman. This time
the update failed and rather than move forward, I reverted back to the
working version (2010.2). However, I must have missed something because
I am getting the following error when I try to access Mailman web:
Apr 28 16:07:42 2012 admin(17726):
pr 28 16:07:42 2012
admin(17726):
admin(17726): [- Mailman Version: 2.1.13 -]
admin(17726): [- Traceback --]
admin(17726): Traceback (most recent call last):
admin(17726): File /usr/lib/mailman/scripts/driver, line 97, in
run_main
admin(17726): pkg = __import__('Mailman.Cgi', globals(), locals(),
[scriptname])
admin(17726): File /usr/lib/mailman/Mailman/Cgi/admin.py, line 35,
in module
admin(17726): from Mailman import MailList
admin(17726): File /usr/lib/mailman/Mailman/MailList.py, line 64, in
module
admin(17726): from Mailman import Gui
admin(17726): File /usr/lib/mailman/Mailman/Gui/__init__.py, line
25, in module
admin(17726): from Privacy import Privacy
admin(17726): File /usr/lib/mailman/Mailman/Gui/Privacy.py, line 28,
in module
admin(17726): from Mailman import GPGUtils
This import is not in standard GNU Mailman and neither is the
Mailman/GPGUtils.py module.
I wonder if the update installed this so rather than restore something,
maybe I need to delete something. But from where is this being called?
According to the above traceback, the import is in
/usr/lib/mailman/Mailman/Gui/Privacy.py at line 25.
If you have a backup of /usr/lib/mailman/Mailman/ you could try
restoring all of it.
signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
On to the next layer of the onion. :-( Traceback (most recent call last): File /usr/sbin/mailmanctl, line 106, in module from Mailman import mm_cfg ImportError: cannot import name mm_cfg On 5/2/2012 9:48 AM, Mark Sapiro wrote: Dennis Putnam wrote: Of course I did not expect this to be easy. After restoring the Mailman directory as suggested, mailman will not start: Traceback (most recent call last): File /usr/sbin/mailmanctl, line 106, in module from Mailman import mm_cfg ImportError: Bad magic number in /usr/lib/mailman/Mailman/mm_cfg.pyc It appears your system Python is now different from the one that compiled all the .pyc files. Just do rm -r /path/to/Mailman/*.pyc This will remove all the compiled Python modules and they will be recompiled as needed. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
Actually I think python itself may be hosed. I am uninstalling it and
reinstalling to see if that fixes it. If not then I will try your
suggestion.
On 5/2/2012 10:06 AM, Mark Sapiro wrote:
Mark Sapiro wrote:
It appears your system Python is now different from the one that
compiled all the .pyc files. Just do
rm -r /path/to/Mailman/*.pyc
I responded without really thinking. I don't think that will work
completely. It will remove the .pyc files immediately subordinate the
Mailman/, but not any deeper ones. For that you need something like
find /path/to/Mailman -name *.pyc -exec rm {} \;
signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
I am making progress (I think). When I uninstalled and reinstalled python, it seems to have taken mailman with it. I did a reinstall of mailman and now the daemon and the qrunners start. I can also now access the initial web page with my lists shown. However, when I try to access the management page I get a 404 error. Obviously something still needs to be restored but I don't know what. Do I now need to re-restore mailman/Mailman? On 5/2/2012 10:12 AM, Mark Sapiro wrote: Dennis Putnam wrote: On to the next layer of the onion. :-( Traceback (most recent call last): File /usr/sbin/mailmanctl, line 106, in module from Mailman import mm_cfg ImportError: cannot import name mm_cfg Did you remove *.py files too? If so, restore and try again removing only *.pyc files. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
All the cgi files are present. It appears to me that my web server config was unaffected by the botched upgrade attempt. However, I don't know if the mailman or python installs did something. What should I look for in the httpd configuration? On 5/2/2012 11:14 AM, Mark Sapiro wrote: Dennis Putnam wrote: I am making progress (I think). When I uninstalled and reinstalled python, it seems to have taken mailman with it. I did a reinstall of mailman and now the daemon and the qrunners start. I can also now access the initial web page with my lists shown. However, when I try to access the management page I get a 404 error. Obviously something still needs to be restored but I don't know what. Do I now need to re-restore mailman/Mailman? I'm guessing you are saying that you can go to http://www.example.com/mailman/listinfo/ and see the expected results, but either one or both of http://www.example.com/mailman/admin/ or http://www.example.com/mailman/admin/LISTNAME gives a 404. This would seem to say that /path/to/mailman/cgi-bin/listinfo exists but /path/to/mailman/cgi-bin/admin is missing. Mailman's cgi-bin directory should contain all of adminconfirm edithtml listinfo options rmlist subscribe admindb create private roster If all those are there, there is probably some issue with the web server config. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
I seem to recall seeing this problem before but I can't find it in any of my archives. [Wed May 02 13:14:20 2012] [error] [client 74.176.153.13] script not found or unable to stat: /usr/lib/mailman/cgi-bin/admin.cgi.cgi, referer: https://dap002.dyndns-ip.com/mailman/admin Obviously the double cgi extension is the problem. On 5/2/2012 12:42 PM, Mark Sapiro wrote: Dennis Putnam d...@bellsouth.net wrote: All the cgi files are present. It appears to me that my web server config was unaffected by the botched upgrade attempt. However, I don't know if the mailman or python installs did something. What should I look for in the httpd configuration? check your web server error logs. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
Thanks for the reply. You are correct in that it does not exist in mm_cfg.py. However, in Defaults.py it is set to CGIEXT = '.cgi' The question then becomes, where should I fix it (presumably in mm_cfg-py). Leave it to Mandriva to change what is normal for everyone else. On 5/2/2012 7:44 PM, Mark Sapiro wrote: Dennis Putnam wrote: I seem to recall seeing this problem before but I can't find it in any of my archives. [Wed May 02 13:14:20 2012] [error] [client 74.176.153.13] script not found or unable to stat: /usr/lib/mailman/cgi-bin/admin.cgi.cgi, referer: https://dap002.dyndns-ip.com/mailman/admin Obviously the double cgi extension is the problem. What is the setting for CGIEXT in mm_cfg.py? If there's nothing there, look in Defaults.py, but the default should be CGIEXT = '' If your cgi wrappers are actually named with a .cgi extension, CGIEXT should be set to '.cgi', otherwise it should be the default null. It is not at all clear to me why this fails with the admin CGI and not with listinfo. If there is anything in the web server that rewrites these, it shouldn't be doing that. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
Thanks. The cgi scripts do have the cgi extension on them. I put CGIEXT = '' in mm_cfg.py which, of course fixed the problem. On 5/3/2012 5:10 PM, Mark Sapiro wrote: Dennis Putnam wrote: Thanks for the reply. You are correct in that it does not exist in mm_cfg.py. However, in Defaults.py it is set to CGIEXT = '.cgi' The question then becomes, where should I fix it (presumably in mm_cfg-py). Leave it to Mandriva to change what is normal for everyone else. What are the actual names of the wrappers in Mailman's cgi-bin directory? Do they have a .cgi extension? If they do not have a .cgi extension, I would put CGIEXT = '' in mm_cfg.py. If they do have a .cgi extension, but the web server is looking for files with a .cgi.cgi (doubled) extension, I would look at the web server config and see if it is rewriting the URLs to add the second '.cgi' and, if so, remove that rewrite. Also look at the various web page links and form action= URLs and verify that they are correct. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
I've made the decision to abandon Mandriva and migrate to Centos. I have mailman up an running (sort of) but now have the opposite problem. This is a vanilla install of Apache so the only config file is mailman.conf at this time. The cgi extension does not exist, in cgi-bin, on this installation of mailman. However, apache is looking for command.cgi. I don't understand why this is a problem out of the box. Shouldn't a vanilla install have this configured correctly? In any case what is the correct way to configure this? Thanks. On 5/4/2012 12:12 PM, Mark Sapiro wrote: Dennis Putnam wrote: Thanks. The cgi scripts do have the cgi extension on them. I put CGIEXT = '' in mm_cfg.py which, of course fixed the problem. It may have fixed the problem for the moment, but it is the wrong way to do it. If the cgi-bin/* wrappers have .cgi extensions, the proper value for CGIEXT is '.cgi'. If that is resulting in the web server looking for *.cgi.cgi files, this is due to something that was added to the web server configuration, possibly as a prior 'solution' to a problem of the web server looking for files without the '.cgi' extension. Anyway, I would find what's adding the extra '.cgi' in the web server and remove it and then either remove the CGIEXT setting from mm_cfg.py or set it to '.cgi'. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
Thanks for the reply. I think you'll it pretty much vanilla.
mm_py.cfg
---
# -*- python -*-
# Copyright (C) 1998,1999,2000,2001,2002 by the Free Software
Foundation, Inc.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
This module contains your site-specific settings.
From a brand new distribution it should be copied to mm_cfg.py. If you
already have an mm_cfg.py, be careful to add in only the new settings you
want. Mailman's installation procedure will never overwrite your mm_cfg.py
file.
The complete set of distributed defaults, with documentation, are in the
file
Defaults.py. In mm_cfg.py, override only those you want to change,
after the
from Defaults import *
line (see below).
Note that these are just default settings; many can be overridden via the
administrator and user interfaces on a per-list or per-user basis.
###
# Here's where we get the distributed defaults.
from Defaults import *
import pwd, grp
##
# Put YOUR site-specific settings below this line.
#ATTENTION: when you use SELinux, mailman might not
#be able to recompile the configuration file
#due to policy settings. If this is the case,
#please run (as root) the supplied mailman-update-cfg script
##
#Here's where we override shipped defaults with settings #
#suitable for the RPM package. #
MAILMAN_UID = pwd.getpwnam('mailman')[2]
MAILMAN_GID = grp.getgrnam('mailman')[2]
##
#Set URL and email domain names #
#
# Mailman needs to know about (at least) two fully-qualified domain
# names (fqdn)
#
# 1) the hostname used in your urls (DEFAULT_URL_HOST)
# 2) the hostname used in email addresses for your domain
(DEFAULT_EMAIL_HOST)
#
# For example, if people visit your Mailman system with
# http://www.dom.ain/mailman; then your url fqdn is www.dom.ain,
# and if people send mail to your system via yourl...@dom.ain then
# your email fqdn is dom.ain. DEFAULT_URL_HOST controls the former,
# and DEFAULT_EMAIL_HOST controls the latter. Mailman also needs to
# know how to map from one to the other (this is especially important
# if you're running with virtual domains). You use
# add_virtualhost(urlfqdn, emailfqdn) to add new mappings.
# Default to using the FQDN of machine mailman is running on.
# If this is not correct for your installation delete the following 5
# lines that acquire the FQDN and manually edit the hosts instead.
from socket import *
try:
fqdn = getfqdn()
except:
fqdn = 'mm_cfg_has_unknown_host_domains'
DEFAULT_URL_HOST = fqdn
DEFAULT_EMAIL_HOST = fqdn
# Because we've overriden the virtual hosts above add_virtualhost
# MUST be called after they have been defined.
##
# Put YOUR site-specific configuration below, in mm_cfg.py . #
# See Defaults.py for explanations of the values.#
# Note - if you're looking for something that is imported from mm_cfg,
but you
# didn't find it above, it's probably in Defaults.py.
---
mailman.conf
--
# Directives for the mailman web interface
Alias /pipermail/ /var/lib/mailman/archives/public/
ScriptAliasMatch ^/mailman/([^/]*)(.*)$ /usr/lib/mailman/cgi-bin/$1.cgi$2
# For the archives
Directory /var/lib/mailman/archives/public
Options +FollowSymLinks
Order allow,deny
Allow from all
/Directory
---
On 5/9/2012 4:07 PM, Mark Sapiro wrote:
Dennis Putnam wrote:
I've made the decision to abandon Mandriva and migrate to Centos. I have
mailman up an running (sort of) but now have the opposite problem. This
is a vanilla install of Apache so the only config file is mailman.conf
at this time. The cgi extension
Re: [Mailman-Users] Dumb Me Tried to Update Mandriva (Again)
Yep, I copied the config from my Mandriva installation thinking they would be compatible. I was wrong and restoring the default fixed it. Thanks. On 5/9/2012 7:36 PM, Mark Sapiro wrote: Dennis Putnam wrote: mailman.conf -= - # Directives for the mailman web interface Alias /pipermail/ /var/lib/mailman/archives/public/ ScriptAliasMatch ^/mailman/([^/]*)(.*)$ /usr/lib/mailman/cgi-bin/$1.cgi$2 Either remove the '.cgi' from the above line making it ScriptAliasMatch ^/mailman/([^/]*)(.*)$ /usr/lib/mailman/cgi-bin/$1$2 or remove the line completely and replace it with ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ Now the real question is was that file part of the Centos (RedHat) Mailman package or was it residue from Mandriva. If you're sure it was part of the Centos rpm, file a bug report with whoever made the rpm. If not look for some Mailman config in /etc/httpd/conf/httpd.conf or some other included file. If you find other Mailman configuration, it may be correct so you maybe could just remove /etc/httpd/conf.d/mailman.conf. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Migration Problem - No Publicly Advertised Lists
After following the instructions for migrating mailman to a new server (http://wiki.list.org/display/DOC/How+do+I+move+a+list+to+a+different+server-Mailman+installation.), I am having trouble with the listinfo page saying there are no publicly advertised lists. I ran 'withlist' and the output appeared normal. Everything else seems to be working other than managing lists via the web pages. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Migration Problem - No Publicly Advertised Lists
Hi David, Looks right to me. drwxrwsr-x. 2 mailman mailman 4096 May 9 09:36 . drwxrwsr-x. 4 mailman mailman 4096 May 9 08:21 .. lrwxrwxrwx. 1 mailman mailman 44 May 9 09:36 cufsalumni - /var/lib/mailman/archives/private/cufsalumni lrwxrwxrwx. 1 mailman mailman 39 May 9 09:36 dapmm - /var/lib/mailman/archives/private/dapmm lrwxrwxrwx. 1 mailman mailman 41 May 9 09:36 mailman - /var/lib/mailman/archives/private/mailma On 5/11/2012 11:52 AM, David wrote: On Fri, May 11, 2012 at 11:07 AM, Dennis Putnam d...@bellsouth.net mailto:d...@bellsouth.net wrote: After following the instructions for migrating mailman to a new server (http://wiki.list.org/display/DOC/How+do+I+move+a+list+to+a+different+server-Mailman+installation.), I am having trouble with the listinfo page saying there are no publicly advertised lists. I ran 'withlist' and the output appeared normal. Everything else seems to be working other than managing lists via the web pages. What is the output of the command below? ls -la /var/lib/mailman/archives/public/ (assuming your mailman install is located at /var/lib) signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Migration Problem - No Publicly Advertised Lists
Thanks for the reply. Unfortunately, 'dumpdb' is not installed and I cannot find a package that contains it. On 5/11/2012 2:55 PM, Mark Sapiro wrote: Dennis Putnam wrote: I am having trouble with the listinfo page saying there are no publicly advertised lists. I ran 'withlist' and the output appeared normal. Everything else seems to be working other than managing lists via the web pages. See the FAQ at http://wiki.list.org/x/lYA9. If the information there does not help you solve the issue, do bin/dumpdb lists/LISTNAME/config.pck | grep web_page_url and compare the host in that URL with the host in the URL you are using to access the listinfo page. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Migration Problem - No Publicly Advertised Lists
Ah! I took your command literally. So the problem is that my mm_cfg.py
seems to not be working. The resulting URL has the local FQDN not what I
specified. Here is my mm_cfg.py (sanitized):
# -*- python -*-
# Copyright (C) 1998,1999,2000,2001,2002 by the Free Software
Foundation, Inc.
#
# This program is free software; you can redistribute it and/or
# modify it under the terms of the GNU General Public License
# as published by the Free Software Foundation; either version 2
# of the License, or (at your option) any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
This module contains your site-specific settings.
From a brand new distribution it should be copied to mm_cfg.py. If you
already have an mm_cfg.py, be careful to add in only the new settings you
want. Mailman's installation procedure will never overwrite your mm_cfg.py
file.
The complete set of distributed defaults, with documentation, are in the
file
Defaults.py. In mm_cfg.py, override only those you want to change,
after the
from Defaults import *
line (see below).
Note that these are just default settings; many can be overridden via the
administrator and user interfaces on a per-list or per-user basis.
###
# Here's where we get the distributed defaults.
from Defaults import *
import pwd, grp
##
# Put YOUR site-specific settings below this line.
#ATTENTION: when you use SELinux, mailman might not
#be able to recompile the configuration file
#due to policy settings. If this is the case,
#please run (as root) the supplied mailman-update-cfg script
##
#Here's where we override shipped defaults with settings #
#suitable for the RPM package. #
MAILMAN_UID = pwd.getpwnam('mailman')[2]
MAILMAN_GID = grp.getgrnam('mailman')[2]
##
#Set URL and email domain names #
#
# Mailman needs to know about (at least) two fully-qualified domain
# names (fqdn)
#
# 1) the hostname used in your urls (DEFAULT_URL_HOST)
# 2) the hostname used in email addresses for your domain
(DEFAULT_EMAIL_HOST)
#
# For example, if people visit your Mailman system with
# http://www.dom.ain/mailman; then your url fqdn is www.dom.ain,
# and if people send mail to your system via yourl...@dom.ain then
# your email fqdn is dom.ain. DEFAULT_URL_HOST controls the former,
# and DEFAULT_EMAIL_HOST controls the latter. Mailman also needs to
# know how to map from one to the other (this is especially important
# if you're running with virtual domains). You use
# add_virtualhost(urlfqdn, emailfqdn) to add new mappings.
# Default to using the FQDN of machine mailman is running on.
# If this is not correct for your installation delete the following 5
# lines that acquire the FQDN and manually edit the hosts instead.
from socket import *
try:
fqdn = getfqdn()
except:
fqdn = 'mm_cfg_has_unknown_host_domains'
DEFAULT_URL_HOST = 'myhostname.myispdomain.com'
DEFAULT_EMAIL_HOST = 'myispdomain.net'
# Because we've overriden the virtual hosts above add_virtualhost
# MUST be called after they have been defined.
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
##
# Put YOUR site-specific configuration below, in mm_cfg.py . #
# See Defaults.py for explanations of the values.#
# Note - if you're looking for something that is imported from mm_cfg,
but you
# didn't find it above, it's probably in Defaults.py.
Thanks.
On 5/11/2012 7:35 PM, Mark Sapiro wrote:
Dennis Putnam wrote:
Thanks for the reply. Unfortunately, 'dumpdb' is not installed and I
cannot find a package that contains it.
It's part of Mailman. it's in Mailman's bin/ directory, not in /bin or
/usr/bin, but /usr/lib/mailman/bin or somewhere like that.
signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Migration Problem - No Publicly Advertised Lists
Thanks again. I did not, I had to boot anyway for other reasons and I thought that would be sufficient. Obviously not. In any case I had to run check_perms a couple of times but it seems to be working OK now. On 5/12/2012 9:53 AM, Mark Sapiro wrote: Dennis Putnam wrote: Ah! I took your command literally. So the problem is that my mm_cfg.py seems to not be working. The resulting URL has the local FQDN not what I specified. Here is my mm_cfg.py (sanitized): Did you run fix_url AFTER editing mm_cfg.py? If so, what is the exact command you ran? /path/to/bin/withlist -l -a -r fix_url should do it. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Web Admin Security Question
After migrating my OS from Mandriva to CentOS I noticed that SSL mailman web access is no longer used. Is this something that is no longer necessary or do I still have more configuring to do? Do I really need SSL or is the management of web admin out of the box sufficient? Thanks. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Web Admin Security Question
Thanks for the reply. Unfortunately I can't find any of this on the old server so I cannot understand what I did to make it work. I am not an Apache expert so I am having trouble with step 1 and hope someone can get me over this hump. I have SSL working as I can access the admin pages using https. However, I can also access it using http so I am not forcing SSL. I did not quite understand the looping caveat in option one so I tried the rewrite rule in option 2. That did not seem to do anything but there was no indication in the instructions where that should go. I have a .conf file that loads the SSL module and sets up the certificates. I added the rewrite code to that file. On 5/20/2012 8:17 PM, Mark Sapiro wrote: Dennis Putnam wrote: After migrating my OS from Mandriva to CentOS I noticed that SSL mailman web access is no longer used. Is this something that is no longer necessary or do I still have more configuring to do? Do I really need SSL or is the management of web admin out of the box sufficient? If you care about sending your admin and moderator passwords in the clear over HTTP, you will want to use HTTPS. See The FAQ at http://wiki.list.org/x/7oA9 for instructions on how to set this up. Don't omit steps 2 and 3. these are important. signature.asc Description: OpenPGP digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Web Admin Security Question
That didn't seem to help either. This is what is in
/etc/httpd/conf.d/mailman.conf
# Directives for the mailman web interface
RewriteEngine On
RewriteCond %{HTTPS} Off
RewriteRule ^(.*)$ https://%{HTTP_HOST}$1 [R,L]
Alias /pipermail/ /var/lib/mailman/archives/public/
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/
# For the archives
Directory /var/lib/mailman/archives/public
Options +FollowSymLinks
Order allow,deny
Allow from all
/Directory
On 5/21/2012 4:38 PM, Mark Sapiro wrote:
Dennis Putnam wrote:
I did not quite understand the looping caveat in option one
so I tried the rewrite rule in option 2. That did not seem to do
anything but there was no indication in the instructions where that
should go. I have a .conf file that loads the SSL module and sets up the
certificates. I added the rewrite code to that file.
That's not where it belongs. One place to put it would be just ahead of
wherever you have your Alias /pipermail/ and ScriptAlias /mailman/
mailman directives in /etc/httpd/conf/httpd.conf or
/etc/httpd/conf.d/mailman or wherever they are.
signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
