[Mailman-Users] Mailman with remote smtp server
Hi , I want to set up mailman to use a remote smtp server. How to achieve this ? I am having trouble understanding how to set up list aliases in /etc/alias in particular? Thanks Meenal -- 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] Troubleshooting posting of a message
Hi, [I changed the name of this thread, as I realized that I more or less hijacked this thread from [EMAIL PROTECTED] and two threads with the same subject proceeded in parallel, my sincere apologies to [EMAIL PROTECTED] and to the list] Mark Sapiro wrote: Rolf E. Sonneveld wrote: Mark Sapiro wrote: One minor point here. The post log entry is not written until the message is delivered by SMTPDirect. OK, thus only after the message has been delivered to at least one subscriber (or the first MTA in the chain of delivery to at least one subscriber). Yes, the first MTA, namely the one on localhost, port 25 unless overridden by SMTPHOST/SMTPPORT in mm_cfg.py. There is no guarantee this MTA has sent the message further. You need to refer the the MTA's logs for that. OK, there was no message submission to the MTA, and this corresponds to the fact that there are no entries in smtp and smtp-failure logfiles. In my case there were no entries in smtp nor in smtp-failure. So the message didn't get that far. 1) The MTA pipes the message to the wrapper which passes it to the scripts/post script which in turn places it in the qfiles/in queue. Nothing is logged in Mailman, but the MTA normally logs the delivery. Now here's the problem, I think. The MTA logs the message as being delivered to Mailman (via the wrapper script $MAILMANDIR/mailman/bin/mailman), so from the MTA's point of view it's done. Now, as the sent message cannot be found under qfiles, and as none of the $MAILMANDIR/logs/* files is modified, it seems as if the message disappeared in a black hole. Is there no way to enable debugging in the wrapper script? It would show the first action of Mailman, I assume. There are at least two possibilities here. 1) The post was rejected (not held or discarded). A reject is not logged, but there should be an associated entry in Mailman's smtp log with a mailman generated message-id and 1 recipient for the reject message sent to the poster. There is none. 2) The wrapper is for a different Mailman installation with a different qfiles directory and probably no qrunners running and probably different log files too. I see no other installation; I have only one in /usr/local/mailman. The wrapper itself (I would expect it to be located at $MAILMANDIR/mail/mailman, not $MAILMANDIR/mailman/bin/mailman) correct, I made a wrong assumption when I was typing. I doublechecked and the mailman wrapper is at $MAILMANDIR/mail/mailman. has the path to the scripts/ directory compiled in and doesn't have any debug switches. It will invoke the scripts/post script and presumably this happens OK or it will return a failure status to the MTA which would be logged by the MTA. The logfile within the MTA shows: 11:26:48.08: middleman version 0.2 starting, pid 25427 11:26:48.16: channel: mailman 11:26:48.17: option file: IMTA_TABLE:mailman_option 11:26:48.17: Opening the channel option file 11:26:48.17: mtaOptionStart: succeeded 11:26:48.17: WRAPPER=/usr/local/mailman/mail/mailman 11:26:48.17: MAX_THREADS=5 11:26:48.17: mtaDequeueStart() 11:26:48.17: #1: process_message() callback 11:26:48.17: #1: build_operations() starting 11:26:48.17: #1: first address: [EMAIL PROTECTED] 11:26:48.17: #1: localpart: allloc5estatic-owner 11:26:48.17: #1:listname: allloc5estatic 11:26:48.17: #1:command: owner 11:26:48.17: #1: build_operations() returning 11:26:48.17: #1: get_messagefile() starting 11:26:48.17: #1: opening tmpfile 11:26:48.19: #1: wrote tmpfile successfully 11:26:48.19: #1: get_messagefile() returning 11:26:48.19: #1: running wrapper for every recipient 11:26:48.19: #1: seeking back to the beginning of the message 11:26:48.19: #1: about to fork() 11:26:48.19: #1: command completed successfully 11:26:48.19: #1: cleaning up 11:26:48.19: #1: mm_opers_free() starting 11:26:48.19: #1: mm_opers_free() returning 11:26:48.19: #1: waiting child 25428 11:26:48.20: #1: dequeue finished 11:26:48.21: #1: command completed successfully 11:26:48.21: #1: cleaning up 11:26:48.21: #1: mm_opers_free() starting 11:26:48.21: #1: mm_opers_free() returning 11:26:48.21: #1: dequeue finished 11:29:48.00: mtaDequeueStart() returned You can add debugging to the scripts/post script. If you look at this script, you will see that it already detects a missing or invalid list name from the wrapper and writes to stderr which is logged to both the post and error logs. You could add some more output, say by adding the last two lines of inq = get_switchboard(mm_cfg.INQUEUE_DIR) inq.enqueue(sys.stdin.read(), listname=listname, tolist=1, _plaintext=1) print sys.stderr, 'Post for %s queued in %s' \ % (listname, mm_cfg.INQUEUE_DIR) I have added the last two lines, but nothing is written to the post logfile. If you don't see this in the
[Mailman-Users] Dates grouped by date while going through an archive of mailing list
Hi all, When clicking on mailing list archive even with dates the resulting list is a flat list one never comes to know when a particular discussion started or ended right there. Other lists system make this pretty much easy. For e.g. http://lists.gnu.org/archive/html/grub-devel/2007-04/index.htmlshould be easy to know what I mean. We have been using GNU Mailman 2.1.8 . Please lemme know if something like this is there in 2.1.9 or something similar is in works at the HEAD. Cheers ! -- Shirish Agarwal This work is licensed under the Creative Commons NonCommercial Sampling Plus 1.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/nc-sampling+/1.0/ -- 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] Error? in accept_these_nonmembers Processing
I create new Mailman (2.1.9) lists via copying template files. One of my template files has: accept_these_nonmembers = ['[EMAIL PROTECTED]', '[EMAIL PROTECTED]', '[EMAIL PROTECTED] (Joe Bleaux)', '[EMAIL PROTECTED]'] (I have split the line for easier readibility.) When I create a new list via /usr/sbin/newlist $listname config_list -i $1.config $listname I get no complaints, and the administrator web interface shows the four addresses with the parenthesized name after the third address. I have not tested whether any of these addresses can post to the new list. But when I want to add another address to the list (or remove an address) via the admin web interface, I get an error messsage about an incorrect address. When I remove the parenthesized name, the error message is not produced. If the parenthesized name is not valid, I would expect an error message during the config_list command execution. -- 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] Unable to Find Bogus User
I've started to get an error message back from the monthly reminders. The gateway is reporting that: Your message could not be delivered to: dawn norris,University of Maine (The name was not found at the remote site. Check that the name has been entered correctly.) Fair enough. It's not an e-mail address, there's no reason why the server SHOULD be able to deliver it. But I can't find the bad entry. Find_member for 'dawn,' 'dawn Norris,' and 'University of Maine' are all coming back with nothing found. How do I locate this incorrect entry? Bill -- 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] password reminders and unsubscribed users
I am running mailman 2.1.9.cp2 and have an ongoing issue I can't find an solution for. There are a number of people who have unsubscribed to my list, yet they continue to receive monthly password reminders. A few months ago I even disabled the password reminder for the list as a whole, and that works for all the subscribed users, yet the old unsubscribed users still continue to receive reminders! I verified once again today that these users are not subscribed. They themselves have no access to the user admin stuff, even with the password mailman just sent them and they receive no other email traffic from the list, just the password reminders. Any idea what is causing this, and how to fix the problem? I am about to just remove the password reminder cron entry, which I know disables reminders for all list, unless someone has a clue what is going on here. An archive search shows no help for this issue, though it has been mentioned before. jim -- 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] Counting messages that went to postfix queue
Hi, We're in the final tests of a pilot of mailman at our University. Due to the previous problem with majordomo2 losing about 9% of email (never sent to postfix, on same server) in the mail list, we'd like to verify that the number of emails that were attempted to be delivered equals the number from list_members command. I've tried finding the message queue IDs which were used and grep QueueID maillog | wc but this seems difficult to do since some reappear again in the logs, which were initially bounces. I also tried pflogsumm and looked at those stats. At first I thought the message sizes and multiples of that message size going to different domains would be a key, but it seems to be inaccurate. I don't have any indications that anyone in our pilot list was lost, but we just need a method to account for the reliability. Regards, --Donald -- 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] Retrieving list membership via email
Folks -- I'd just like a quick confirmation of Mailman (2.1.4, yikes!) behavior: A message sent to [EMAIL PROTECTED] with a body of who should return the list members. (FAQ 3.62) However, my list has 'private_roster' set to 'List Admin Only', and when (from a list owner email address) I send who admin_password, I get: - Results: You are not allowed to retrieve the list membership. Is this expected behavior? -- Drew Tenenholz -- 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] Pipermail -- MHonArc error
I am trying to convert a list from the Pipermail archiver to MhonArc. I can run /bin/arch --wipe listname successfully. I get this error when generating the MhonArc archive with /bin/arch listname Pickling archive state into /data/mailman/archives/private/listname/pipermail.pck Traceback (most recent call last): File ./arch, line 202, in ? main() File ./arch, line 190, in main archiver.processUnixMailbox(fp, start, end) File /data/mailman/Mailman/Archiver/pipermail.py, line 576, in processUnixMailbox self.mhonarcProcessUnixMailbox(input, start, end) File /data/mailman/Mailman/Archiver/pipermail.py, line 706, in mhonarcProcessUnixMailbox status = mhonarch_process.close() IOError: [Errno 32] Broken pipe If I switch back to Pipermail it will run successfully. It looks too that I miss March and April 2007 archives when trying to convert to MHonArc, but Pipermail generates them. Would this point to an problem in the .mbox file? --Karl -- 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 and Qmail/Vpopmail
Hello, I'm trying to install Mailman and have some problems. If I try to send an email to the list(configuration), qmail cannot deliver the mail and I get a Sorry, no mailbox here by that name. I looked in the logs and qmail actually tries to find the local [EMAIL PROTECTED], like I configured it in the virtualdomains. I think qmail doesn't check the mailman home which is /usr/local/mailman. And I don't really know how qmail could find it. I have the line lists.mydomain.tld:mailman in virtualdomains, but how should qmail know where to find the mailman home directory? Hope the question is not to stupid and somebody can help me. Thanks, Simon Schuh -- 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 and Qmail/Vpopmail
Simon, The Qmail files can usually be found in /var/qmail/mailnames. There should be a directory for each domain. Within these directories Qmail uses .qmail-alias filenames for configuration so they are easily missed. Make sure to use 'ls -al' to see them. Check to see if Mailman has created the proper .files. There should be quite a few for each list you have created. In Service, Michael Kabot President - SOAR Scouting Online Affordable Reliable [EMAIL PROTECTED] 585-388-0211 www.soarol.com | -Original Message- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED] | On Behalf Of Simon Schuh | Sent: Tuesday, May 01, 2007 6:34 PM | To: mailman-users@python.org | Subject: [Mailman-Users] Mailman and Qmail/Vpopmail | | | Hello, | | I'm trying to install Mailman and have some problems. | If I try to send an email to the list(configuration), | qmail cannot deliver the mail and I get a Sorry, no mailbox | here by that name. I looked in the logs and qmail actually | tries to find the local [EMAIL PROTECTED], | like I configured it in the virtualdomains. I think qmail | doesn't check the mailman home which is /usr/local/mailman. | And I don't really know how qmail could find it. I have the | line lists.mydomain.tld:mailman in virtualdomains, but how | should qmail know where to find the mailman home directory? | | Hope the question is not to stupid and somebody can help me. | | Thanks, | Simon Schuh | | -- | 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/mkabot%40 soarol.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Sorry for the link not getting right
Hi all, When clicking on mailing list archive even with dates the resulting list is a flat list one never comes to know when a particular discussion started or ended right there. Other lists system make this pretty much easy. For e.g. http://lists.gnu.org/archive/html/grub-devel/2007-04/index.htmlhttp://lists.gnu.org/archive/html/grub-devel/2007-04/index.htmlshouldshould http://lists.gnu.org/archive/html/grub-devel/2007-04/index.htmlshould be easy to know what I mean. They use something called MHonArc We have been using GNU Mailman 2.1.8 . Please lemme know if something like this is there in 2.1.9 or something similar is in works at the HEAD. Cheers ! -- -- Shirish Agarwal This work is licensed under the Creative Commons NonCommercial Sampling Plus 1.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/nc-sampling+/1.0/ -- 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] Dates grouped by date while going through anarchive of mailing list
shirish agarwal wrote: When clicking on mailing list archive even with dates the resulting list is a flat list one never comes to know when a particular discussion started or ended right there. Other lists system make this pretty much easy. For e.g. http://lists.gnu.org/archive/html/grub-devel/2007-04/index.html should be easy to know what I mean. But that's a Mhonarc archive, not a pipermail archive. We have been using GNU Mailman 2.1.8 . Please lemme know if something like this is there in 2.1.9 or something similar is in works at the HEAD. Cheers ! There is no current work on changing pipermail, but you can always use Mhonarc as your Mailman archiver. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.004.htp. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Error? in accept_these_nonmembers Processing
Barry Finkel wrote:
I create new Mailman (2.1.9) lists via copying template files.
One of my template files has:
accept_these_nonmembers = ['[EMAIL PROTECTED]', '[EMAIL PROTECTED]',
'[EMAIL PROTECTED] (Joe Bleaux)', '[EMAIL PROTECTED]']
The *_these_nonmembers lists are lists of plain email addresses without
comments or real names or regexps (beginning with ^) that match email
addresses.
(I have split the line for easier readibility.)
Actually, config_list input is Python, and in Python it is perfectly
acceptable to break a list like the above across lines. New-lines
outside of quoted strings are ignored if they occur inside parens (),
brackets [] or braces {}.
When I create a new
list via
/usr/sbin/newlist $listname
config_list -i $1.config $listname
I get no complaints, and the administrator web interface shows the
four addresses with the parenthesized name after the third address.
I have not tested whether any of these addresses can post to the new
list.
With the above, [EMAIL PROTECTED] could not post (because the code
would test whether '[EMAIL PROTECTED]' is equal to '[EMAIL PROTECTED]
(Joe Bleaux)') but the others could.
But when I want to add another address to the list (or remove
an address) via the admin web interface, I get an error messsage about
an incorrect address. When I remove the parenthesized name, the error
message is not produced. If the parenthesized name is not valid, I
would expect an error message during the config_list command execution.
It's not valid and your expectation is reasonable, but this isn't what
happens (I'm not saying it can't/won't be fixed).
Here's a section of the code that would normally validate the supplied
value.
if wtype in (mm_cfg.EmailList, mm_cfg.EmailListEx):
# BAW: value might already be a list, if this is coming from
# config_list input. Sigh.
if isinstance(val, ListType):
return val
In other words, if accept_these_nonmembers (or any attribute which is a
list of email addresses or a list of email addresses and regexps)
comes from the GUI page, it is the contents of a text box which is a
string and it is validated and transformed to a list, but if it is
already a list, it is assumed to be from input to config_list and the
list is just assigned to the attribute without validatating its
contents.
If you want to see this fixed, the best next step is to report it in
the bug tracker at
http://sourceforge.net/tracker/?group_id=103atid=100103. (Since
I've already done the analysis, I'll probably fix it, but get it in
the tracker anyway.)
--
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] Unable to Find Bogus User
McNutt Jr, William R wrote: I've started to get an error message back from the monthly reminders. The gateway is reporting that: Your message could not be delivered to: dawn norris,University of Maine (The name was not found at the remote site. Check that the name has been entered correctly.) Fair enough. It's not an e-mail address, there's no reason why the server SHOULD be able to deliver it. But I can't find the bad entry. Find_member for 'dawn,' 'dawn Norris,' and 'University of Maine' are all coming back with nothing found. How do I locate this incorrect entry? Presumably the address on the list is OK, but a .forward or other aliasing mechanism downstream of Mailman is converting it. Also, it seems you are not getting the message body returned since it contains the address to which the reminder was sent. If you are getting Received: headers back, you might be able to narrow it down from the domain of the first server it is sent to. If you set VERP_PASSWORD_REMINDERS = Yes in mm_cfg.py, the reminders will be sent with envelope from [EMAIL PROTECTED] where user=example.net comes from the recipients [EMAIL PROTECTED] member address and example.com is your domain. The 'bounce' should come back to the envelope address and enable you to see the user's address. -- 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] password reminders and unsubscribed users
Jim Miller wrote: I am running mailman 2.1.9.cp2 and have an ongoing issue I can't find an solution for. There are a number of people who have unsubscribed to my list, yet they continue to receive monthly password reminders. A few months ago I even disabled the password reminder for the list as a whole, and that works for all the subscribed users, yet the old unsubscribed users still continue to receive reminders! I verified once again today that these users are not subscribed. They themselves have no access to the user admin stuff, even with the password mailman just sent them and they receive no other email traffic from the list, just the password reminders. Any idea what is causing this, and how to fix the problem? I am about to just remove the password reminder cron entry, which I know disables reminders for all list, unless someone has a clue what is going on here. An archive search shows no help for this issue, though it has been mentioned before. There have been past reports of this, and the ones that haven't been resolved are from cPanel installations. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp. It's even worse than just unsubscribed members still getting reminders. See http://mail.python.org/pipermail/mailman-users/2007-February/055638.html for a report of users receiving reminders from a deleted list. -- 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] Counting messages that went to postfix queue
D G Teed wrote: Due to the previous problem with majordomo2 losing about 9% of email (never sent to postfix, on same server) in the mail list, we'd like to verify that the number of emails that were attempted to be delivered equals the number from list_members command. Look at the entry in Mailman's smtp log which will tell you how man total recipients there wore for each sent message. I've tried finding the message queue IDs which were used and grep QueueID maillog | wc but this seems difficult to do since some reappear again in the logs, which were initially bounces. If you mean Message-Id:, that's in the smtp log entry. If you mean the MTA's IDs, they would not normally be found anywhere in Mailman's logs, and there could be more than one for a single post because a single post may or may not be sent in a single smtp transaction depending on Mailman settings and number of recipients. I also tried pflogsumm and looked at those stats. At first I thought the message sizes and multiples of that message size going to different domains would be a key, but it seems to be inaccurate. I don't have any indications that anyone in our pilot list was lost, but we just need a method to account for the reliability. If you want to know what Mailman thinks, if there are no entries in Mailman's smtp-failure log, the number of recips in the smtp log entry is the number of recipients given to the MTA. You can believe this number or not, but I know of no case in which it is wrong. If you want to know what the MTA did with these recipients and whether or not it lost any, that is not a Mailman question. -- 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 and Qmail/Vpopmail
My Qmail files are in /home/vpopmail/domains, but there are no files for Mailman. I tried to create them manually, but probably did that wrong. Where should they be? Simon Schuh Michael Kabot schrieb: Simon, The Qmail files can usually be found in /var/qmail/mailnames. There should be a directory for each domain. Within these directories Qmail uses .qmail-alias filenames for configuration so they are easily missed. Make sure to use 'ls -al' to see them. Check to see if Mailman has created the proper .files. There should be quite a few for each list you have created. In Service, Michael Kabot President - SOAR Scouting Online Affordable Reliable [EMAIL PROTECTED] 585-388-0211 www.soarol.com -- 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 and Qmail/Vpopmail
Can you see an .qmail-alias files under the /var/vpopmail/domains diretory? Are you using Plesk, Cpanel, or any type of server/domain control panel? If so, create an email alias through the control panel for one of your domains domain.tld. Check to see if the .qmail-alias file shows up in /var/vpopmail/domains/domain.tld. If it does not, that is not where Qmail configuration files are stored. Unfortunately, I am not familiar with Vpopmail or how it interfaces with Qmail. In Service, Michael Kabot President - SOAR Scouting Online Affordable Reliable [EMAIL PROTECTED] 585-388-0211 www.soarol.com | -Original Message- | From: [EMAIL PROTECTED] | [mailto:[EMAIL PROTECTED] | On Behalf Of Simon Schuh | Sent: Tuesday, May 01, 2007 10:57 PM | To: mailman-users@python.org | Subject: Re: [Mailman-Users] Mailman and Qmail/Vpopmail | | | My Qmail files are in /home/vpopmail/domains, but there are | no files for | Mailman. | I tried to create them manually, but probably did that wrong. | Where should they be? | | Simon Schuh | | | | Michael Kabot schrieb: | Simon, | | The Qmail files can usually be found in | /var/qmail/mailnames. There | should be a directory for each domain. Within these | directories Qmail | uses .qmail-alias filenames for configuration so they are easily | missed. Make sure to use 'ls -al' to see them. | | Check to see if Mailman has created the proper .files. | There should | be quite a few for each list you have created. | | | In Service, | | Michael Kabot | President - SOAR |Scouting Online | Affordable Reliable | [EMAIL PROTECTED] | 585-388-0211 | | www.soarol.com | | | -- | 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/mkabot%40 soarol.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Troubleshooting posting of a message
Rolf E. Sonneveld wrote: Now, I tested the following: I became user mailman mailman cd /usr/local/mailman/scripts mailman ./post listname message input ctrl-D and indeed something showed up in the locks logfile, as well as in the post logfile and in the bounce logfile (as the sender address was not defined, mailman could not authorize the message submissions, which ended in a bounce). So it seems that the calling program within the MTA gets a positive success status from mailman, but something is wrong during message submission. To repeat part of he logfile: [...] 11:26:48.19: #1: running wrapper for every recipient 11:26:48.19: #1: seeking back to the beginning of the message 11:26:48.19: #1: about to fork() 11:26:48.19: #1: command completed successfully 11:26:48.19: #1: cleaning up 11:26:48.19: #1: mm_opers_free() starting 11:26:48.19: #1: mm_opers_free() returning 11:26:48.19: #1: waiting child 25428 11:26:48.20: #1: dequeue finished 11:26:48.21: #1: command completed successfully 11:26:48.21: #1: cleaning up [...] I see two possibilities. 1) the wrapper is failing and this fact is not communicated back to the MTA. Possibly there is a group mismatch or some other problem, but these result in stderr output from the wrapper and a non-zero exit status, both of which should be seen by the MTA. 2) the wrapper's precompiled path to the scripts directory is to something other than /usr/local/mailman/scripts. It is not clear to me from your initial posts whether this issue involves just one list or all lists and whether things this list (or all lists) ever worked. In any case, you could try your test similarly to the above, but using the wrapper as in cd /usr/local/mailman/mail (or whatever the correct directory is) ./mailman post listname message input ctrl-D The first attempt will probably result in a group mismatch error before it reads any message input. This will at least tell you what group it is expecting which may help if there is really a group mismatch with the MTA. Then if you can try it again as the expected group, you can see if it actually posts the message. -- 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] global email address blocklist?
Ron Brogden wrote: Looking at the source, I see the following on line 394 of MailList.py: self.ban_list = [] I am wondering if a possible solution here would be to initialize this value to include a list of banned email address, either via an included value from Defaults.py or by hardcoding the values into to the above array? self.ban_list = [ '[EMAIL PROTECTED]', '[EMAIL PROTECTED]' ] You can do either. The 'standard' way to do it would be to define DEFAULT_BAN_LIST = [] in Defaults.py (actually Defaults.py.in for a patch) and then put your list DEFAULT_BAN_LIST =['[EMAIL PROTECTED]', '[EMAIL PROTECTED]'] in mm_cfg.py and put self.ban_list = mm_cfg.DEFAULT_BAN_LIST in MailList.py. What I am unclear of is whether this means that every message has to be scanned through this list or whether it would only apply to subscribe requests. It only applies to subscription requests, and since 2.1.7, invitations, subscription confirmations and changes of address. However, the above changes will only initialize the ban_list for new lists. You will still need to use config_list or whatever to update existing lists. Another potential spot would be in AddMember(). Perhaps just adding a new function to MailList.py which checks if the address is in a global array and raises an error if this is the case? Yes. This would have the addvantage of not requiring the various list's ban_list to be updated with every change and seems a better solution for your purpose. I suggest however that the place to make this change is not AddMember(), but GetBannedPattern(). -- 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] Retrieving list membership via email
Drew Tenenholz wrote: I'd just like a quick confirmation of Mailman (2.1.4, yikes!) behavior: A message sent to [EMAIL PROTECTED] with a body of who should return the list members. (FAQ 3.62) However, my list has 'private_roster' set to 'List Admin Only', and when (from a list owner email address) I send who admin_password, I get: - Results: You are not allowed to retrieve the list membership. Is this expected behavior? Assuming 'admin_password' above is the actual list admin or moderator password and not the user password of the admin, then no, it is not the expected behavior. If it is the user password of the admin, then it is the expected behavior. The password needs to be the list's admin or moderator password. The address you send the 'who' from and to which the results will be returned can be any address. -- 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] Dates grouped by date while going through an archive of mailing list
On 5/1/07, shirish agarwal wrote: When clicking on mailing list archive even with dates the resulting list is a flat list one never comes to know when a particular discussion started or ended right there. Other lists system make this pretty much easy. For e.g. http://lists.gnu.org/archive/html/grub-devel/2007-04/index.html should be easy to know what I mean. We have been using GNU Mailman 2.1.8 . Please lemme know if something like this is there in 2.1.9 or something similar is in works at the HEAD. Cheers ! There is work planned on the archiving system for 2.2, but nothing that I know of for 2.1.x. You could always use a different archiver, such as mhonarc -- the details on how to do this should be covered in the documentation and the FAQ Wizard. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- 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] Error? in accept_these_nonmembers Processing
On 5/1/07, Barry Finkel wrote: I get no complaints, and the administrator web interface shows the four addresses with the parenthesized name after the third address. I have not tested whether any of these addresses can post to the new list. But when I want to add another address to the list (or remove an address) via the admin web interface, I get an error messsage about an incorrect address. When I remove the parenthesized name, the error message is not produced. If the parenthesized name is not valid, I would expect an error message during the config_list command execution. Yeah, I've seen some weirdness myself in areas like this. The one that hit me was a service provider role account with an unusual (but legal) character in the name tried to post to one of our internal group lists, and I approved that message and also clicked the box to have Mailman automatically add that address to the whitelist. That worked, no problem. However, when I later went to add more addresses to the whitelist, there was nothing I could to get anything accepted -- until I deleted this unusual address. After that, everything worked fine. But I also couldn't re-add this unusual address. There's definitely some bugs in the code to handle the whitelist addresses. I need to file my own bug report on this subject on SourceForge, and I would encourage you to do the same. Maybe then we could get Tokio or Mark to actually find fix this one. ;) -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- 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] Unable to Find Bogus User
On 5/1/07, McNutt Jr, William R wrote: Fair enough. It's not an e-mail address, there's no reason why the server SHOULD be able to deliver it. But I can't find the bad entry. Find_member for 'dawn,' 'dawn Norris,' and 'University of Maine' are all coming back with nothing found. How do I locate this incorrect entry? Good question. If find_member isn't finding it, that tells me that there's some other illegal characters in the address that aren't visible, or that maybe the address is something totally different inside your system and that the broken aliasing is happening somewhere else. Other than doing a dumpdb of all the lists and doing some visual searching, I'm not sure that I've got an easy answer for you. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- 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] Counting messages that went to postfix queue
On 5/1/07, D G Teed wrote: I've tried finding the message queue IDs which were used and grep QueueID maillog | wc but this seems difficult to do since some reappear again in the logs, which were initially bounces. Mailman will give you the message-id, the list name, and the number of recipients it was sent to. However, this won't help you for digest recipients, since Mailman will have to generate a different and totally unique message-id for that. In addition, it will use the same message-id on outbound as was used on inbound, so unless you have different copies of your MTA running on different ports and sending their logs to different locations, you're going to get a mix of both inbound and outbound activity in your log files. This will make it more difficult to track down what happened when. Now, postfix will give you a one-to-many mapping of the message-id and the queue-ids, and then you can track the status of the individual queue-ids. I also tried pflogsumm and looked at those stats. At first I thought the message sizes and multiples of that message size going to different domains would be a key, but it seems to be inaccurate. Speaking as the author of the mmdsr script, and as someone who has hacked around with the pflogsumm script, I can tell you that this is a process that is harder to do than most people would give credit for. Beyond that, I'm not sure I can give you any specific advice. I've been looking at installing Splunk on the python.org machines so that we can more easily track down what happened when to which mail messages, but right now it doesn't appear to know anything about Mailman log format. I don't mind teaching it about that kind of stuff, but that does mean that we're that much further away from having any kind of short-term solution for this problem. I don't have any indications that anyone in our pilot list was lost, but we just need a method to account for the reliability. Mailman doesn't currently have much for you in this area. We know that this is an area of weakness, and are planning on fixing this in upcoming versions. However, we do not otherwise have a whole lot of details as to what will be going on when. If you have specific requirements, I would urge you to join the discussions on this topic in the Mailman Wiki pages. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- 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] password reminders and unsubscribed users
On 5/1/07, Jim Miller wrote: I am running mailman 2.1.9.cp2 and have an ongoing issue I can't find an solution for. First off, this is a cPanel version. See FAQ 6.11. Any idea what is causing this, and how to fix the problem? I am about to just remove the password reminder cron entry, which I know disables reminders for all list, unless someone has a clue what is going on here. An archive search shows no help for this issue, though it has been mentioned before. I'm guessing you have more than one copy of Mailman installed, and that it's the other version which is sending out the notices. Talk to your service provider to find out for sure. -- Brad Knowles [EMAIL PROTECTED], Consultant Author LinkedIn Profile: http://tinyurl.com/y8kpxu Slides from Invited Talks: http://tinyurl.com/tj6q4 -- 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 with remote smtp server
Meenal Pant wrote: I want to set up mailman to use a remote smtp server. How to achieve this ? I am having trouble understanding how to set up list aliases in /etc/alias in particular? To use a remote SMTP server for outgoing mail, simply set SMTPHOST and maybe SMTPPORT in mm_cfg.py. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.072.htp. To use a remote server for incoming mail to Mailman is much more complex. A search of the archives of this list for fetchmail will turn up some info (http://www.google.com/search?q=site%3Amail.python.org++inurl%3Amailman-users++fetchmail). Depending on how remote the server is, it may be possible to use NFS to give the remote server access to the mail wrapper on the Mailman host which can be another way to do it. -- 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] New to list - Have cpanel questions
Hello, I'm new to the list. Am about to move a Mailman list to a new server that uses cpanel. I understand there is a slightly different version used by cpanel. Any tips for making the move? Any potential problems I should be aware of? If anyone has how-to instructions I'd be grateful. Thanks in advance for any advice/assistance. -- 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
