Re: [Mailman-Users] Moderation action
Hello,
Mark Sapiro napisał(a):
Patrick Bogen wrote:
Unfortunately, it looks like, since Moderate.py comes before anything
else, there's no really 'correct' way to do this.
It doesn't come before SpamDetect which processes header_filter_rules,
so your suggestion below won't work.
Thank you both for your answers.
What if I did as you suggested first, but instead of one filter rule that
matches everything, there would be one filter rule for each address I want
held (I assume that there won't be more than 4-5 such subscribers), and such
a rule would match a From: header with that address, and of course action
would be Hold?
Does it make any sense or you think it would be better to use the energy to
write a patch to the source code?
One option that ought to work, however, would be the following:
Moderate all users that you want rejected, and set
member_moderation_action to reject. Unmoderate the users you want
held. Add a header filter rule that matches on everything (something
like a single caret ('^') should suffice), and is set to Hold. I
haven't tested this, and I don't know if it will work or not.
Dominika
--
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] New Mailman Installation - Can't Send Email toaNewList(reformatted)
Mark Sapiro wrote: So we're back to the original question. Please go back to http://mail.python.org/pipermail/mailman-users/2006-November/054347.html and try to understand what I wrote there. As I said there, The fact that you have nothing in virtual-mailman after running bin/genaliases and/or creating lists indicates you have no lists whose host_name attribute is in the POSTFIX_STYLE_VIRTUAL_DOMAINS list. Since POSTFIX_STYLE_VIRTUAL_DOMAINS is apparently correct, the problem is with the lists. This is because the various DEFAULT_*_HOST settings and add_virtualhost directives are not correct in mm_cfg.py or weren't when the lists were created. The post referenced above says more about this. Mark, Ok, I added these lines at the end of the mm_cfg.py file: DEFAULT_URL_HOST = 'www.domain1.net' DEFAULT_EMAIL_HOST = 'mail.domain1.net' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost(DEFAULT_URL_HOST, 'mail.domain2.net') Then, I ran the command below that refresh the mailman system: bin/withlist -l -a -r fix_url -- Then, I verified that the file virtual-mailman had been populated. Looks good so far... Now, how do I restart or refresh the Postfix system? Regards, Jeff -- 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] [EMAIL PROTECTED] isnt working
there are log entries in maillog that say Dec 4 09:15:07 listserv postfix/smtpd[2573]: connect from listserv.mydomain.com[127.0.0.1] Dec 4 09:15:07 listserv postfix/smtpd[2573]: 0C3CA2184C3: client=listserv.mydomain.com[127.0.0.1] Dec 4 09:15:07 listserv postfix/cleanup[2576]: 0C3CA2184C3: message-id=[EMAIL PROTECTED] Dec 4 09:15:07 listserv postfix/qmgr[2438]: 0C3CA2184C3: from=[EMAIL PROTECTED], size=3775, nrcpt=1 (queue active) Dec 4 09:15:07 listserv postfix/smtpd[2573]: disconnect from listserv.mydomain.com[127.0.0.1] Dec 4 09:15:07 listserv postfix/smtp[2580]: 0C3CA2184C3: to=[EMAIL PROTECTED], relay=mydomain.com[10.180.50.2], delay=0, status=bounced (host mydomain.com[10.180.50.2] said: 550 5.7.1 Unable to relay for [EMAIL PROTECTED] (in reply to RCPT TO command)) Dec 4 09:15:07 listserv postfix/cleanup[2576]: 34EAD2184EA: message-id=[EMAIL PROTECTED] Dec 4 09:15:07 listserv postfix/qmgr[2438]: 34EAD2184EA: from=, size=5858, nrcpt=1 (queue active) Dec 4 09:15:07 listserv postfix/qmgr[2438]: 0C3CA2184C3: removed Dec 4 09:15:07 listserv postfix/local[2577]: 34EAD2184EA: to=[EMAIL PROTECTED], relay=local, delay=0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman bounces mailman) Dec 4 09:15:07 listserv postfix/qmgr[2438]: 34EAD2184EA: removed If that part where is says removed means that they are off the list - they aren't. This is the vette log says: Dec 04 08:25:03 2006 (2762) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 08:25:03 2006 (2762) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 08:30:03 2006 (2762) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 08:30:03 2006 (2762) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 08:35:03 2006 (2762) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 08:35:03 2006 (2762) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 08:40:03 2006 (2762) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 08:40:03 2006 (2762) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 08:45:04 2006 (2762) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 08:45:04 2006 (2762) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 08:50:03 2006 (2762) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 08:50:03 2006 (2762) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 08:55:03 2006 (2762) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 08:55:03 2006 (2762) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 09:00:04 2006 (2762) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 09:00:04 2006 (2762) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 09:00:05 2006 (2762) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 09:00:05 2006 (2762) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 09:05:05 2006 (2374) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 09:05:05 2006 (2374) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 09:10:03 2006 (2374) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 09:10:03 2006 (2374) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 09:15:03 2006 (2374) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 09:15:03 2006 (2374) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Dec 04 09:20:04 2006 (2374) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 09:20:04 2006 (2374) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list I am very confused. Could the fact that it wont relay to my local domain be the problem? ken Mark Sapiro [EMAIL PROTECTED] wrote: Ken Cheney wrote: Given that I am very new to Mailman/Postfix/Linux... where would I find the MTA logs? Maybe /var/log/maillog; maybe somewhere else. how would I tell if the message made it to mailman. There will be a maillog entry indicating the message was delivered via a pipe to the wrapper as in
[Mailman-Users] Change entire user list
Hi; I supervise a Mailman list for a club of RVers which has about 550 members. Once a month I get a new roster to put up on the site, but I don't get specific changes to email addresses, new members or deleted members. Is there a simple way to unsubscribe the entire current list and mass subscribe the new list? Thank you. Frank Baillie -- 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] Change entire user list
* Frank Baillie [EMAIL PROTECTED]: Hi; I supervise a Mailman list for a club of RVers which has about 550 members. Once a month I get a new roster to put up on the site, but I don't get specific changes to email addresses, new members or deleted members. Is there a simple way to unsubscribe the entire current list and mass subscribe the new list? I added a patch which lets you do exactly that. http://sourceforge.net/tracker/?atid=300103group_id=103func=browse topmost line http://sourceforge.net/tracker/index.php?func=detailaid=1605292group_id=103atid=300103 -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBFsend no mail to [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] [EMAIL PROTECTED] isnt working
On 12/4/06, Ken Cheney [EMAIL PROTECTED] wrote: there are log entries in maillog that say Dec 4 09:15:07 listserv postfix/smtpd[2573]: connect from listserv.mydomain.com[127.0.0.1] Dec 4 09:15:07 listserv postfix/smtpd[2573]: 0C3CA2184C3: client=listserv.mydomain.com[127.0.0.1] Dec 4 09:15:07 listserv postfix/cleanup[2576]: 0C3CA2184C3: message-id=[EMAIL PROTECTED] Dec 4 09:15:07 listserv postfix/qmgr[2438]: 0C3CA2184C3: from=[EMAIL PROTECTED], size=3775, nrcpt=1 (queue active) Dec 4 09:15:07 listserv postfix/smtpd[2573]: disconnect from listserv.mydomain.com[127.0.0.1] Something connected from the local computer and sent a message. Dec 4 09:15:07 listserv postfix/smtp[2580]: 0C3CA2184C3: to=[EMAIL PROTECTED], relay=mydomain.com[10.180.50.2], delay=0, status=bounced (host mydomain.com[10.180.50.2] said: 550 5.7.1 Unable to relay for [EMAIL PROTECTED] (in reply to RCPT TO command)) The message was to [EMAIL PROTECTED] The server attempted to deliver this by connecting to mydomain.com (IP 10.180.50.2), which refused to relay to the address [EMAIL PROTECTED] Dec 4 09:15:07 listserv postfix/cleanup[2576]: 34EAD2184EA: message-id=[EMAIL PROTECTED] Dec 4 09:15:07 listserv postfix/qmgr[2438]: 34EAD2184EA: from=, size=5858, nrcpt=1 (queue active) Dec 4 09:15:07 listserv postfix/qmgr[2438]: 0C3CA2184C3: removed The local SMTP server generated a bounce notification and removed the original message from its queue. Dec 4 09:15:07 listserv postfix/local[2577]: 34EAD2184EA: to=[EMAIL PROTECTED], relay=local, delay=0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman bounces mailman) Dec 4 09:15:07 listserv postfix/qmgr[2438]: 34EAD2184EA: removed The bounce notification was delivered to mailman's bounce handler, and the bounce notification was removed from postfix's queue. If that part where is says removed means that they are off the list - they aren't. The 'removed' is postfix removing messages from its queue, which is completely normal and correct. This is the vette log says: Dec 04 08:25:03 2006 (2762) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 08:25:03 2006 (2762) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list Once again, '[EMAIL PROTECTED]' isn't a member of the list. This is probably a postfix DSN, which is sent 'from' postfix, or something similar. It looks like no posts are actually reaching your mailing list. I am very confused. Could the fact that it wont relay to my local domain be the problem? Your server doesn't seem to realize that [EMAIL PROTECTED] is supposed to be delivered locally. Perhaps this is correct; however, the smart host that it's set up to deliver through ALSO won't accept [EMAIL PROTECTED] At least one of these is incorrect. If the mailman server is also the server where you read your mail (e.g., your POP or IMAP server), then it needs to be configured to accept messages for kcheney for local delivery. If your SMTP relay host is the server where you read your mail, IT Needs to be set up to accept mail from [EMAIL PROTECTED] for local delivery. -- - Patrick Bogen -- 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] Moderation action
Dominika Tkaczyk wrote: What if I did as you suggested first, but instead of one filter rule that matches everything, there would be one filter rule for each address I want held (I assume that there won't be more than 4-5 such subscribers), and such a rule would match a From: header with that address, and of course action would be Hold? Yes, I think that would work. You could have a separate rule for each poster or just one rule with a separate regexp for each poster. In fact, you could then moderate everyone and set default_member_moderation to Yes to simplify maintenance of moderation because the header rule would apply to first hold the message and then when the held message is approved, it wil bypass moderation. Note however that this wouldn't work if the header rule action was accept because messages which are accepted by such a rule still go through the additional checks. In this case, the posters would need to have their moderate flags off. Does it make any sense or you think it would be better to use the energy to write a patch to the source code? I think it always makes sense to use existing configuration options if you can rather that patching the code, unless using the existing features is just too cumbersome which I don't think is the case here. -- 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] New Mailman Installation - Can't Send Email toaNewList(reformatted)
mcjathan wrote: Mark, Ok, I added these lines at the end of the mm_cfg.py file: DEFAULT_URL_HOST = 'www.domain1.net' DEFAULT_EMAIL_HOST = 'mail.domain1.net' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) add_virtualhost(DEFAULT_URL_HOST, 'mail.domain2.net') Then, I ran the command below that refresh the mailman system: bin/withlist -l -a -r fix_url -- Then, I verified that the file virtual-mailman had been populated. Looks good so far... Now, how do I restart or refresh the Postfix system? It seems the above was originally posted from another address and the original didn't reach (or hasn't yet reached) the list. Anyway, it is answered at http://mail.python.org/pipermail/mailman-users/2006-December/054773.html. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] HELP! My lists have lost their minds
All the email to one of my lists is coming with the [listname] header from another list, and all the email to that list is coming with the [listname] header from the other. Even when I go to http://list.xcski.com/mailman/listinfo/partyhats I see the page I should be seeing at http://list.xcski.com/mailman/listinfo/techhats/ (although the techhats pages seems ok). The partyhats archive is toast as well. I've shut down all my lists, but how do I fix this? -- Paul Tomblin [EMAIL PROTECTED] http://blog.xcski.com/ If men are from Mars and women are from Venus, there's going to be one big-ass fight over where to set the thermostat. -- Jim Rosenberg -- 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] Change entire user list
Frank Baillie [EMAIL PROTECTED] wrote: Hi; I supervise a Mailman list for a club of RVers which has about 550 members. Once a month I get a new roster to put up on the site, but I don't get specific changes to email addresses, new members or deleted members. Is there a simple way to unsubscribe the entire current list and mass subscribe the new list? Thank you. Frank Baillie There are two commands in the bin directory: remove_members --all --nouserack --noadminack $LISTNAME add_members -w n -r $FILE $LISTNAME The first will remove all subscribers in $LISTNAME without any acknowledgements to the subscribers and administrators. The second will silently subscribe all of the e-mail addresses in the $FILE file. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- 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] Another hint
I'm getting this message when I try to fix the archives: Traceback (most recent call last): File /var/lib/mailman/bin/arch, line 187, in ? main() File /var/lib/mailman/bin/arch, line 172, in main archiver = HyperArchive(mlist) File /usr/lib/mailman/Mailman/Archiver/HyperArch.py, line 599, in __init__ self.__super_init(dir, reload=1, database=db) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 289, in __init__ d = pickle.load(f) cPickle.UnpicklingError: could not find MARK -- Paul Tomblin [EMAIL PROTECTED] http://blog.xcski.com/ I've long believed that a large amount of our current technology was invented by SF writers, and remained fiction until some geek read it and thought I know how to build that. -- Andrew Dalgleish -- 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] mbox files
Quoting Mark Sapiro ([EMAIL PROTECTED]): Paul Tomblin wrote: slowed my computer down to a crawl. I gave up and used the mbox splitter awk program I found in the list archives and I'm now building the archives 500 messages at a time. Hope that works. It should. Also, you can effectively do the same thing without breaking up the mbox by using the --start= and --end= options on bin/arch. See bin/arch --help Paul Tomblin [EMAIL PROTECTED] replied: Is there any way to make arch smarter about ^From lines? First pass through the archive, I ended up with a bazillion messages in the archive for today, all with No subject because it was treating any line like ^From as the start of a message. It would be nice if it recognized the difference between real mbox start-of-message ^From and just random lines from some list member. I was under the impression that ANY line in an mbox file that began with ^From was the start of a new message. That is why mailers change a mail body line ^From to ^ From . Is there an mbox standard? What you could do is write a script to process the corrupted mbox file. It would write non-^From lines intact, but it would parse the ^From lines to determine if they were the start of new messages or just plain mail body lines. Body lines would be re-written with an initial . -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- 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] [EMAIL PROTECTED] isnt working
Ken Cheney wrote: there are log entries in maillog that say Dec 4 09:15:07 listserv postfix/smtpd[2573]: connect from listserv.mydomain.com[127.0.0.1] Dec 4 09:15:07 listserv postfix/smtpd[2573]: 0C3CA2184C3: client=listserv.mydomain.com[127.0.0.1] Dec 4 09:15:07 listserv postfix/cleanup[2576]: 0C3CA2184C3: message-id=[EMAIL PROTECTED] Dec 4 09:15:07 listserv postfix/qmgr[2438]: 0C3CA2184C3: from=[EMAIL PROTECTED], size=3775, nrcpt=1 (queue active) Dec 4 09:15:07 listserv postfix/smtpd[2573]: disconnect from listserv.mydomain.com[127.0.0.1] Dec 4 09:15:07 listserv postfix/smtp[2580]: 0C3CA2184C3: to=[EMAIL PROTECTED], relay=mydomain.com[10.180.50.2], delay=0, status=bounced (host mydomain.com[10.180.50.2] said: 550 5.7.1 Unable to relay for [EMAIL PROTECTED] (in reply to RCPT TO command)) The above is a message from Mailman to [EMAIL PROTECTED] that can't be delivered because Postfix doesn't know how to route mail to mydomain.com or it is not allowed to relay mail from 127.0.0.1 to mydomain.com. This is a Postfix configuration issue. Dec 4 09:15:07 listserv postfix/cleanup[2576]: 34EAD2184EA: message-id=[EMAIL PROTECTED] Dec 4 09:15:07 listserv postfix/qmgr[2438]: 34EAD2184EA: from=, size=5858, nrcpt=1 (queue active) The above are an incoming message (a DSN from Postfix back to Mailman saying the first message was undeliverable). Dec 4 09:15:07 listserv postfix/qmgr[2438]: 0C3CA2184C3: removed This is Postfix telling you the the first message (0C3CA2184C3) was removed from Postfix's queue because Postfix was done with it. Postfix has no knowledge of what Mailman does and you won't find anything in the Postfix maillog that relates to any action Mailman has taken other than mail delivery. Dec 4 09:15:07 listserv postfix/local[2577]: 34EAD2184EA: to=[EMAIL PROTECTED], relay=local, delay=0, status=sent (delivered to command: /usr/lib/mailman/mail/mailman bounces mailman) Dec 4 09:15:07 listserv postfix/qmgr[2438]: 34EAD2184EA: removed And these are Postfix's delivery of the DSN to the mail/mailman wrapper for 'mailman-bounces' and the subsequent removal of the processed message from Postfix's queue. If that part where is says removed means that they are off the list - they aren't. That's not what it says. The above entries presumably all come after some message to listname-leave was received and delivered to Mailman. These are a reply from Mailman which is undeliverable (most likely because you aren't allowing relaying from localhost/127.0.0.1) and the subsequent bounce being returned to Mailman. This is the vette log says: Dec 04 08:25:03 2006 (2762) -request/hold autoresponse discarded for: [EMAIL PROTECTED] Dec 04 08:25:03 2006 (2762) Mailman post from [EMAIL PROTECTED] held, message-id=[EMAIL PROTECTED]: Post by non-member to a members-only list and several more snipped I am very confused. Could the fact that it wont relay to my local domain be the problem? The first message above is saying that Mailman is trying to send an autoresponse to a message received at the listname-request (or -join, -leave or -(un)subscribe) address, but the user has already received the daily limit of such messages. The second is a held post. What happens to these? Do you see them in the admindb interface for the list? Messages clearly reach Mailman. The problem is that the messages that mailman sends can't be relayed. You have to configure Postfix to relay from localhost/127.0.0.1 to anywhere. Then you will see Mailman's responses and more will become clear. -- 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] Change entire user list
Barry Finkel wrote: There are two commands in the bin directory: remove_members --all --nouserack --noadminack $LISTNAME add_members -w n -r $FILE $LISTNAME The first will remove all subscribers in $LISTNAME without any acknowledgements to the subscribers and administrators. The second will silently subscribe all of the e-mail addresses in the $FILE file. And there is the sync_members command which synchronizes the list membership with the addresses in an input file which is the one step way to do what is wanted, but these all require command line access. Ralf's patch mentioned in another reply allows doing sync_members from the web interface, but of course it requires more than command line access to install the patch. -- 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] HELP! My lists have lost their minds
Paul Tomblin wrote: All the email to one of my lists is coming with the [listname] header from another list, and all the email to that list is coming with the [listname] header from the other. Even when I go to http://list.xcski.com/mailman/listinfo/partyhats I see the page I should be seeing at http://list.xcski.com/mailman/listinfo/techhats/ (although the techhats pages seems ok). The partyhats archive is toast as well. It seems that somehow, the lists/techhats/config.pck file may have gotten copied/restored to lists/partyhats/config.pck. a similar thing may have happened with archives/private/techhats/ - archives/private/partyhats/. I've shut down all my lists, but how do I fix this? I hope you have a good backup :-( -- 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] Change entire user list
* Barry Finkel [EMAIL PROTECTED]: There are two commands in the bin directory: remove_members --all --nouserack --noadminack $LISTNAME add_members -w n -r $FILE $LISTNAME The first will remove all subscribers in $LISTNAME without any acknowledgements to the subscribers and administrators. The second will silently subscribe all of the e-mail addresses in the $FILE file. Why so complicated? Simply use sync_members instead. -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBFsend no mail to [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Change entire user list
* Mark Sapiro [EMAIL PROTECTED]: And there is the sync_members command which synchronizes the list membership with the addresses in an input file which is the one step way to do what is wanted, but these all require command line access. Ralf's patch mentioned in another reply allows doing sync_members from the web interface, but of course it requires more than command line access to install the patch. OTOH somebody could adopt the patch (the feature request is 2 years old now :) ) -- Ralf Hildebrandt (i.A. des IT-Zentrums) [EMAIL PROTECTED] Charite - Universitätsmedizin BerlinTel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-BerlinFax. +49 (0)30-450 570-962 IT-Zentrum Standort CBFsend no mail to [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] HELP! My lists have lost their minds
Quoting Mark Sapiro ([EMAIL PROTECTED]): Paul Tomblin wrote: All the email to one of my lists is coming with the [listname] header from another list, and all the email to that list is coming with the [listname] header from the other. Even when I go to http://list.xcski.com/mailman/listinfo/partyhats I see the page I should be seeing at http://list.xcski.com/mailman/listinfo/techhats/ (although the techhats pages seems ok). The partyhats archive is toast as well. It seems that somehow, the lists/techhats/config.pck file may have gotten copied/restored to lists/partyhats/config.pck. a similar thing may have happened with archives/private/techhats/ - archives/private/partyhats/. Nope, I checked that - partyhats/config.pck looks fine, as does techhats/config.pck. I've shut down all my lists, but how do I fix this? I hope you have a good backup :-( Since it seems my backup and my current are the same, that's not going to help much. -- Paul Tomblin [EMAIL PROTECTED] http://blog.xcski.com/ We sealed our federal pact without bloodshed and without exploitation of the weak by the strong. All it took was fairness, justice and some compromises on both sides. - George-Etienne Cartier. -- 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] [EMAIL PROTECTED] isnt working
Patrick Bogen wrote: Dec 4 09:15:07 listserv postfix/smtp[2580]: 0C3CA2184C3: to=[EMAIL PROTECTED], relay=mydomain.com[10.180.50.2], delay=0, status=bounced (host mydomain.com[10.180.50.2] said: 550 5.7.1 Unable to relay for [EMAIL PROTECTED] (in reply to RCPT TO command)) The message was to [EMAIL PROTECTED] The server attempted to deliver this by connecting to mydomain.com (IP 10.180.50.2), which refused to relay to the address [EMAIL PROTECTED] Patrick obviously paid more attention to this error than I did. Patrick's analysis of the relaying failure is correct. -- 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] [EMAIL PROTECTED] isnt working
x.x.50.2 is one of my DNS servers it has no email funcionality at all. I thought that postfix sent the mail.. meaning not relayed off of something else. Ken Mark Sapiro [EMAIL PROTECTED] wrote: Patrick Bogen wrote: Dec 4 09:15:07 listserv postfix/smtp[2580]: 0C3CA2184C3: to=, relay=mydomain.com[10.180.50.2], delay=0, status=bounced (host mydomain.com[10.180.50.2] said: 550 5.7.1 Unable to relay for [EMAIL PROTECTED] (in reply to RCPT TO command)) The message was to [EMAIL PROTECTED] The server attempted to deliver this by connecting to mydomain.com (IP 10.180.50.2), which refused to relay to the address [EMAIL PROTECTED] Patrick obviously paid more attention to this error than I did. Patrick's analysis of the relaying failure is correct. -- Mark SapiroThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan - Cheap Talk? Check out Yahoo! Messenger's low PC-to-Phone call rates. -- 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] [EMAIL PROTECTED] isnt working
On 12/4/06, Ken Cheney [EMAIL PROTECTED] wrote: x.x.50.2 is one of my DNS servers it has no email funcionality at all. I thought that postfix sent the mail.. meaning not relayed off of something else. Email works by mail servers relaying mail to each other until it gets to a server that (believes) it can deliver it locally. There is either something wrong with the MX records in your domain, or your Postfix server is actually set to relay mail to the DNS, for some reason. Check your postfix config for settings related to relaying or smarthosts, and check your DNS config to see if all your MX records are correct. -- - Patrick Bogen -- 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] Strange Archives Issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I inherited an old Mailman installation, which I upgraded from an unknown version to the latest version, 2.1.9. Most of the other lists are fine, but one particular list has issues archiving messages. Messages to the list get shunted after being delivered, before being archived. I've researched this issue for months, and it's finally driven me to bugging the list for additional places to look. Please note that other lists, created both before and after the upgrade, archive just fine. Here's some logs from the 'error' log: Dec 04 14:07:09 2006 (4446) Uncaught runner exception: [Errno 21] Is a directory: '/var/ lib/mailman/archives/public/LISTNAME' Dec 04 14:07:09 2006 (4446) 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/IncomingRunner.py, line 133, in _dispose mlist.Save() File /usr/lib/mailman/Mailman/MailList.py, line 565, in Save self.CheckHTMLArchiveDir() File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 236, in CheckHTMLArchiveDir breaklink(pubdir) File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 56, in breaklink os.unlink(link) OSError: [Errno 21] Is a directory: '/var/lib/mailman/archives/public/LISTNAME' Dec 04 14:07:09 2006 (4446) SHUNTING: 1165258558.144629+452aa00f48fbbba74e1259752d575731 e2085546 Here's an idea of directory structure: [EMAIL PROTECTED]: /var/lib/mailman/archives]# ls -la total 24 drwxrwsr-x 3 rootmailman 4096 Nov 13 15:47 ./ drwxrwsr-x 6 rootmailman 4096 Nov 7 09:58 ../ drwxrwsr-x 29 mailman mailman 4096 Dec 4 12:32 private/ lrwxrwxrwx 1 rootmailman7 Nov 13 15:47 public - private/ [EMAIL PROTECTED]: /var/lib/mailman/archives/private]# ls -la drwxrwsr-x 29 mailman mailman 4096 Dec 4 12:32 ./ *snip* drwxrwsr-x 6 mailman mailman 4096 Dec 4 14:06 LISTNAME/ drwxrwsr-x 2 mailman mailman 4096 Jul 13 11:16 LISTNAME.mbox/ *snip* I'm really at the end of my rope. I'd like to avoid deleting the list and recreating it, but I think I may have to do that. I figured I'd send out one last call for help before I do that. Thanks, Chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFdHb0zT/AXrftr4URAnn5AJ4jpWE0TheX/V89J8G97aekWTcvyACfRNlw zpuptiMzstfe9S4H8XphBn0= =m33q -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] [EMAIL PROTECTED] isnt working
I have internal DNS that is marginally different than external DNS. My internal DNS points to the internal IP of my exchange server and the internal IP of my listserv. My external DNS points to the external IPs of each. They are correct. should I be looking somewhere other than main.cf? Patrick Bogen [EMAIL PROTECTED] wrote: On 12/4/06, Ken Cheney wrote: x.x.50.2 is one of my DNS servers it has no email funcionality at all. I thought that postfix sent the mail.. meaning not relayed off of something else. Email works by mail servers relaying mail to each other until it gets to a server that (believes) it can deliver it locally. There is either something wrong with the MX records in your domain, or your Postfix server is actually set to relay mail to the DNS, for some reason. Check your postfix config for settings related to relaying or smarthosts, and check your DNS config to see if all your MX records are correct. -- - Patrick Bogen - Any questions? Get answers on any topic at Yahoo! Answers. Try it now. -- 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, Fedora Core, 500 Internal Server Error
I have posted a few times with no luck in getting mailman to work with Fedora Core using YUM. I have installed and all seems to be working something to do with suexe. Emails go out and using email a person can subcribe, but the web pages do not work. Can anyone please tell me they have successfully installed mailman on a Fedora Core box and if so can they please help me get mine working. I understand that is a permissions error having to do with suexe, but I have not clue how to make it work. Thanks -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Strange Archives Issue
Christopher Wawak wrote: Here's some logs from the 'error' log: Dec 04 14:07:09 2006 (4446) Uncaught runner exception: [Errno 21] Is a directory: '/var/ lib/mailman/archives/public/LISTNAME' Dec 04 14:07:09 2006 (4446) 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/IncomingRunner.py, line 133, in _dispose mlist.Save() File /usr/lib/mailman/Mailman/MailList.py, line 565, in Save self.CheckHTMLArchiveDir() File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 236, in CheckHTMLArchiveDir breaklink(pubdir) File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 56, in breaklink os.unlink(link) OSError: [Errno 21] Is a directory: '/var/lib/mailman/archives/public/LISTNAME' Dec 04 14:07:09 2006 (4446) SHUNTING: 1165258558.144629+452aa00f48fbbba74e1259752d575731 e2085546 Here's an idea of directory structure: [EMAIL PROTECTED]: /var/lib/mailman/archives]# ls -la total 24 drwxrwsr-x 3 rootmailman 4096 Nov 13 15:47 ./ drwxrwsr-x 6 rootmailman 4096 Nov 7 09:58 ../ drwxrwsr-x 29 mailman mailman 4096 Dec 4 12:32 private/ lrwxrwxrwx 1 rootmailman7 Nov 13 15:47 public - private/ The above is your problem. archives/public should be a directory, not a symlink. The symlinks should be for lists with public archives only and should be like archives/public/listname - archives/private/listname and maybe archives/public/listname.mbox - archives/private/listname.mbox if the global .mbox is also public. All you need to do is rm the archives/public symlink and create the archives/public directory with group mailman and permissions drwxrwsr-x. Also, the archives/private directory should nt be world readable. Its permissions should be drwxrws--x. You don't need to create any symlinks in the archives/public directory. Mailman will create these as required for lists with public archives as the lists are accessed. After fixing the above, you can run bin/unshunt to reprocess the shunted messages. -- 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] Mailman, Fedora Core, 500 Internal Server Error
Vernon Webb wrote: I have posted a few times with no luck in getting mailman to work with Fedora Core using YUM. I have installed and all seems to be working something to do with suexe. Emails go out and using email a person can subcribe, but the web pages do not work. Can anyone please tell me they have successfully installed mailman on a Fedora Core box and if so can they please help me get mine working. I understand that is a permissions error having to do with suexe, but I have not clue how to make it work. The Apache restrictions on the suEXEC module conflict with Mailman's security model. If possible, don't use suEXEC for the Mailman CGIs. If you have to use suEXEC, I think you will have to make the suEXEC user and group the same as the owner and group of the wrappers (in $prefix/cgi-bin) and possibly remove the SETGID bit from the wrappers. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.016.htp and http://httpd.apache.org/docs/2.0/suexec.html for further detail. Note that I have no experience with suEXEC so I may be wrong about this, but that's how it looks to me. -- 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] Mailman, Fedora Core, 500 Internal Server Error
Vernon Webb wrote: I understand that is a permissions error having to do with suexe, but I have not clue how to make it work. You might find the results of http://www.google.com/search?hl=enq=site%3Amail.python.org++inurl%3Amailman++suexec (starting with http://mail.python.org/pipermail/mailman-users/1999-November/002656.html) helpful. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Some lists no longer archiving
Hi, I have a list that stopped archiving in Octoberother lists are Ok... Where would I start looking for a reason why? regards Steven Jones Senior Linux/Unix/San System Administrator APG -Technology Integration Team Victoria University of Wellington Phone: +64 4 463 6272 Mobile: +64 27 563 6272 -- 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] Change entire user list
Ralf Hildebrandt wrote: OTOH somebody could adopt the patch (the feature request is 2 years old now :) ) Message received. :-) -- 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] HELP! My lists have lost their minds
Paul Tomblin wrote: Nope, I checked that - partyhats/config.pck looks fine, as does techhats/config.pck. I've shut down all my lists, but how do I fix this? Did you either 'restart' or 'stop' and 'start' mailman before 'shutting down'? Actually, I don't see how it is possible that the web admin interface would show data different from the config.pck unless the underlying file system is somehow broken. -- 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] HELP! My lists have lost their minds
Quoting Mark Sapiro ([EMAIL PROTECTED]): Paul Tomblin wrote: Nope, I checked that - partyhats/config.pck looks fine, as does techhats/config.pck. I've shut down all my lists, but how do I fix this? Did you either 'restart' or 'stop' and 'start' mailman before 'shutting down'? /etc/init.d/mailman stop Actually, I don't see how it is possible that the web admin interface would show data different from the config.pck unless the underlying file system is somehow broken. The config.db was fine, but the config.pck *was* corrupted. Or rather, it appeared to be a copy of another lists, since doing a list_members on both lists returned the same list. Very odd. -- Paul Tomblin [EMAIL PROTECTED] http://blog.xcski.com/ I did volunteer EMS as recovery from sysadmining, then I did sysadmining to recover from volunteer EMS. -- random -- 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] HELP! My lists have lost their minds
Paul Tomblin wrote: The config.db was fine, but the config.pck *was* corrupted. Or rather, it appeared to be a copy of another lists, since doing a list_members on both lists returned the same list. The config.db is left over from Mailman 2.0.x and is probably VERY out of date and should probably just be discarded along with config.db.last. And yes, your symptom seemed to be the result of a config.pck having been replaced somehow with that of another list. I don't know how that could have happened, but at this point you need to find the most recent backup of a good config.pck. -- 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] HELP! My lists have lost their minds
Quoting Mark Sapiro ([EMAIL PROTECTED]): Paul Tomblin wrote: The config.db was fine, but the config.pck *was* corrupted. Or rather, it appeared to be a copy of another lists, since doing a list_members on both lists returned the same list. And yes, your symptom seemed to be the result of a config.pck having been replaced somehow with that of another list. I don't know how that could have happened, but at this point you need to find the most recent backup of a good config.pck. Yeah, I found one from a few weeks ago. A few weeks ago I started backing up to a new external USB disk, and on Sunday that disk crashed so I have no recent backups. Yesterday when I was rebuilding the archives for this machine, it got extremely low on memory, and I guess that did something. This is my first experiment with Xen and LVM, and so far I'm not impressed. -- Paul Tomblin [EMAIL PROTECTED] http://blog.xcski.com/ [Y]ou should write for the comprehension of the next programmer who looks at your code, keep it clean and sensible, and *not* play any obscure Jedi mind-tricks. -- Anthony de Boer -- 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] Some lists no longer archiving
Steven Jones wrote: I have a list that stopped archiving in Octoberother lists are Ok... Where would I start looking for a reason why? Assuming admin-Archiving Options-archive is still set to Yes, look in Mailman's 'error' log. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] VERP and AOL feedback
I have read a couple threads on this, but none have really been able to help me. I need to get the AOL feedback to work, but I need more header information. VERP works great if it wasn't for one problem. We have a HUGE customer base, and this changes header information that the customer sees. Is there anyway I could add header like X-Member. This way it does not interfere with what they see, or use for filtering. I have added custom headers already to our mailings, but I am not sure how I would go about getting the actual e-mail address of the customer in there. Thanks -Rob -- 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] VERP and AOL feedback
Rob Jackson wrote: Is there anyway I could add header like X-Member. This way it does not interfere with what they see, or use for filtering. I have added custom headers already to our mailings, but I am not sure how I would go about getting the actual e-mail address of the customer in there. I'm sure there are multiple ways to do this, but here's what I suggest. Set OWNERS_CAN_ENABLE_PERSONALIZATION = Yes in mm_cfg.py. Then set the list's Non-digest options-personalize to Yes. Also, find the code try: d['user_delivered_to'] = mlist.getMemberCPAddress(member) # BAW: Hmm, should we allow this? d['user_password'] = mlist.getMemberPassword(member) d['user_language'] = mlist.getMemberLanguage(member) in the process() function in Mailman/Handlers/Decorate.py and add the line msg['X-Member-Address'] = d['user_delivered_to'] to make it try: d['user_delivered_to'] = mlist.getMemberCPAddress(member) msg['X-Member-Address'] = d['user_delivered_to'] # BAW: Hmm, should we allow this? d['user_password'] = mlist.getMemberPassword(member) d['user_language'] = mlist.getMemberLanguage(member) This will only work for messages, not for digests. -- 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] [EMAIL PROTECTED] isnt working
Ken Cheney wrote: should I be looking somewhere other than main.cf? If you mean Postfix's main.cf, that may be it or it could be in your MX records or ? Patrick Bogen [EMAIL PROTECTED] wrote: On 12/4/06, Ken Cheney wrote: x.x.50.2 is one of my DNS servers it has no email funcionality at all. Well, accordilng to the maillog entry you quoted earlier Dec 4 09:15:07 listserv postfix/smtp[2580]: 0C3CA2184C3: to=[EMAIL PROTECTED], relay=mydomain.com[10.180.50.2], delay=0, status=bounced (host mydomain.com[10.180.50.2] said: 550 5.7.1 Unable to relay for [EMAIL PROTECTED] (in reply to RCPT TO command)) Postfix on the mailman machine connected to port 25 [10.180.50.2] in order to deliver a message to kcheney at mydomain.com and something there answered the connect and spoke enough SMTP to get as far as receiving a RCPT TO command and to respond that it couldn't relay to mydomain.com. Were all the occurrences of mydomain.com in that log entry actually the same domain before you munged them? It seems pretty strange that a server at mydomain.com[10.180.50.2] would think it a) needed to relay to mydomain.com, and b) couldn't. What does [10.180.50.2] think it's host name is? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Duplicate password reminders
All of the members of all of the lists on my site appear to be getting duplicate reminders. There is a single crontab entry for mailman calling mailpasswords. Is there some additional mechanism by which mailman might be calling mailpasswords? This is mailman 2.1.6 Thank you. -j -- Jeffrey Goldberghttp://www.goldmark.org/jeff/ -- 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] mails send from a webmail system dont get a Subject_prefix if there are umlauts
Hi, recently we noticed, that mails send from our webmailsystem TWIG containing a german umlaut in the subject aren't getting a Subject_prefix from maliman. Mails from other mailclients do get the Subject_prefix. The problem seams, that twig isn't encoding the subject correctly, so it get invalid and thats why mailman isn't setting a Subject_prefix. Is there a way to get mailman setting the Subject_prefix? Thanks for hints and comments! Regrads Götz -- Götz Reinicke IT Koordinator Tel. +49 7141 969-420 Fax +49 7141 969 55-420 [EMAIL PROTECTED] Filmakademie Baden-Württemberg Mathildenstr. 20 71638 Ludwigsburg www.filmakademie.de -- 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] Moderation action
Mark Sapiro napisał(a): Dominika Tkaczyk wrote: What if I did as you suggested first, but instead of one filter rule that matches everything, there would be one filter rule for each address I want held (I assume that there won't be more than 4-5 such subscribers), and such a rule would match a From: header with that address, and of course action would be Hold? Yes, I think that would work. You could have a separate rule for each poster or just one rule with a separate regexp for each poster. Now I see, yes that will probably be a little simpler. I thought earlier that a rule has only one regexp. In fact, you could then moderate everyone and set default_member_moderation to Yes to simplify maintenance of moderation because the header rule would apply to first hold the message and then when the held message is approved, it wil bypass moderation. Note however that this wouldn't work if the header rule action was accept because messages which are accepted by such a rule still go through the additional checks. In this case, the posters would need to have their moderate flags off. Thank you again for your help. Dominika -- 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
