[Mailman-Users] Unsubscribe link on msg_footer
Hi list, I would place in email footer the link to give possibility to the user to unsubscribe (possibly directly, without insert the password) I try to do this adding in msg_footer the following Unsubscribe: %(user_optionsurl)s?password=%(user_password) sunsub=1unsubconfirm=1 but Mailman (2.1.11 on Debian Lenny) said me that I can't use user_optionsutl in this variable There is any other way to do this? Thank you -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Error running bin/mailmanctl restart
Mark has been helping me with this off-line but I thought I would send this to the list to see if there are others who are aware of the solution. I have been using the following on a clean install of Mac Server 10.5.8 and upgrading Mailman 2.1.9 to 2.1.12: ./configure --prefix=/usr/share/mailman --with-cgi-gid=_www --with-mail-gid=mail --with-mailhost=domain.com --with-urlhost=domain.com --with-var-prefix=/var/mailman --with-groupname=_mailman and get the following error: * Installation directory /var/mailman is not configured properly! * Directory must be owned by group _mailman: /var/mailman /var/mailman is has the settings root:wheel while the files inside are root:_mailman. Do I need to change the group of the /var/mailman directory for the install? I know that change is probably not significant, but I an not sure enough of my knowledge to know. Once I get this right, I plan on upgrading a 10.6.2 production server running 2.1.12rc1 to 2.1.12. Thanks! Paul -- Paul Kleeberg p...@fpen.org On Dec 16, 2009, at 3:53 PM, Mark Sapiro wrote: Paul Kleeberg wrote: You are correct. /var points to /private/var but /private/var/mailman is owned by root:wheel. Should I chgrp to _mailman which is the group of all the files inside or use --with-groupname=wheel As long as the subordinate directories are all group _mailman and SETGID, the group of var-prefix itself doesn't matter. And you should configure with --with-groupname=_mailman to match the group of the existing install. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Error running bin/mailmanctl restart
Paul Kleeberg wrote: Mark has been helping me with this off-line It wasn't my intent to go off-line, but if someone replies to me without including the list, I tend not to copy the list on further replies. and get the following error: * Installation directory /var/mailman is not configured properly! * Directory must be owned by group _mailman: /var/mailman /var/mailman is has the settings root:wheel while the files inside are root:_mailman. Do I need to change the group of the /var/mailman directory for the install? I know that change is probably not significant, but I an not sure enough of my knowledge to know. It is only significant to configure in your case, but configure whant the prefix and var_prefix directories to be SETGID and Mailman's group so that subordinates created by make install will be the same. When you originally asked about this off line, I thought what you had would be OK because it was a working installation, but apparently it only works for Apple :( You need to chgrp _mailman /var/mailman chmod g+s /var/mailman to make configure happy. The prefix directory (/usr/share/mailman in your case) needs to be the same. Once I get this right, I plan on upgrading a 10.6.2 production server running 2.1.12rc1 to 2.1.12. FYI, 2.1.13rc1 is released and 2.1.13 final will be released next week barring the unexpected. It fixes several minor bugs in 2.1.12. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Searching across lists and making global changes
Have multiple mailing lists under one domain Is there any way to search across all lists for a certain member and make a global change to their email or name? As an administrator, if a user changes their email, I often have to search each list for the member to locate them (1) and then change their info (2) Thank you. -- Brian J. Luria DVM, DACVIM Bluepearl Veterinary Partners Florida Veterinary Specialists Tampa: (813) 933-8944 Clearwater: (727) 572-0132 Brandon: (813) 571-3303 www.bluepearlvet.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Problem with mailing list
Hi there - I have been having problems with my MAILMAN mailing list that my hosting service believes is a MAILMAN related problem rather than a hosting one. I can't post to the list, though the support staff at the hosting service can... My message gets to MAILMAN but disappears into the ether once it has been approved, and isn't showing up in the archives. The list is brilla...@brillante.com.au. How do I get support for this? thanks, Elizabeth -- Elizabeth Cotterell Brillante Pty Ltd PO Box 4136 Kingston ACT 2604 AUSTRALIA email: i...@brillante.com.au web: www.brillante.com.au -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Unsubscribe link on msg_footer
-Original Message- From: mailman-users-bounces+s.watkins=nhm.ac...@python.org [mailto:mailman-users-bounces+s.watkins=nhm.ac...@python.org] On Behalf Of Andrea Cappelli Sent: 17 December 2009 11:27 To: mailman-users@python.org Subject: [Mailman-Users] Unsubscribe link on msg_footer Hi list, I would place in email footer the link to give possibility to the user to unsubscribe (possibly directly, without insert the password) I try to do this adding in msg_footer the following Unsubscribe: %(user_optionsurl)s?password=%(user_password) sunsub=1unsubconfirm=1 but Mailman (2.1.11 on Debian Lenny) said me that I can't use user_optionsutl in this variable There is any other way to do this? Thank you I'm sorry to say this but this gives me the screaming hab-dabs. Emailing a user's password in plain text WITHOUT the user requesting it or expecting it??? Please... No... Don't do it. Walk away from the whizzy super-fasty-clicky-interfacey-clicky thing and ... No! Just don't.. Please? By all means link them back to the webpage that allows them to unsubscribe. By all means link them to the webpage that allows them to have a password reminder/reset their password. But don't EVER just randomly send out a user's password to them BECAUSE... Well, they MIGHT want to unsubscribe... Or floss the cat.. Or... Sorry to seem like such a insert preferred expletive here but this opens the door to some many different types of Hell it is strongly to be discouraged. Regards, (Xmas cheers and all that... Ho ho ho!) S Watkins == -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] How to reduce list archives
Hi,
we private archive all our lists - and its come the time where we
need to free space up on the volume that its archiving to. We are using version
2.1.12.
We tried to edit the archives/private/listname.mbox/listname.mbox file to
remove the messages we don't want and then run 'bin/arch --wipe listname' and
got:
e...@mailhost-locust] /usr/local/mailman/bin $ ./arch --wipe security
#0 20090102122338.d9d2a158...@flens.dfn-cert.de
Schreibe Archivzustand in Datei
/HAmailhost/mailman/archives/private/security/pipermail.pck
Traceback (most recent call last):
File ./arch, line 201, in ?
main()
File ./arch, line 189, in main
archiver.processUnixMailbox(fp, start, end)
File /usr/local/mailman/Mailman/Archiver/pipermail.py, line 578, in
processUnixMailbox
a = self._makeArticle(m, self.sequence)
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 684, in
_makeArticle
mlist=self.maillist)
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 308, in __init__
charset = message.get_content_charset(cset_out)
File /usr/lib/python2.4/email/Message.py, line 800, in get_content_charset
charset = unicode(charset, 'us-ascii').encode('us-ascii')
TypeError: decoding Unicode is not supported
The archive was completely lost and restored from backup. Any help would be
appropriate.
Thanks.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Searching across lists and making global changes
Apologies if this is a repeat, wasn't sure it went through * Have multiple mailing lists under one domain Is there any way to search across all lists for a certain member and make a global change to their email or name? As an administrator, if a user changes their email, I often have to search each list for the member to locate them (1) and then change their info (2) Thank you. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Unsubscribe link on msg_footer
Andrea Cappelli wrote: I try to do this adding in msg_footer the following Unsubscribe: %(user_optionsurl)s?password=%(user_password)sunsub=1unsubconfirm=1 but Mailman (2.1.11 on Debian Lenny) said me that I can't use user_optionsutl in this variable There is any other way to do this? Steff Watkins has already replied as to why this is a bad idea. As to why it doesn't work, the %(user_optionsurl)s and %(user_password)s replacements are only available if the list's Non-digest options - personalize setting is Yes or Full Personalization. If the personalize setting doesn't appear on the Non-digest options page, the installation has to add OWNERS_CAN_ENABLE_PERSONALIZATION = Yes to mm_cfg.py to enable it. But as Steff says, don't do it. Just use Unsubscribe: %(user_optionsurl)s or without personalization Unsubscribe: %(web_page_url)soptions/%(list_name)s -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Searching across lists and making global changes
On Wed, Dec 16, 2009 at 04:36:14PM -0500, Brian Luria wrote: Have multiple mailing lists under one domain Is there any way to search across all lists for a certain member find_member if you've got shell access and make a global change to their email or name? I tend to see how many entries there are, if it's one or two, i'll do it manually; clone_member is a dandy tool for where there are quite a few. Both of those just work on the email address; for the name, make the person handle that via /options, and instruct them to set the 'set globally' option. -- ``novissima autem inimica destruetur mors omnia enim subiecit sub pedibus eius cum autem dicat'' (I Corinthios 15:26 (Biblia Sacra Vulgata)) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] How to reduce list archives
Hans Joachim Wenzel wrote:
we private archive all our lists - and its come the time where we
need to free space up on the volume that its archiving to. We are using
version 2.1.12.
We tried to edit the archives/private/listname.mbox/listname.mbox file to
remove the messages we don't want and then run 'bin/arch --wipe listname' and
got:
e...@mailhost-locust] /usr/local/mailman/bin $ ./arch --wipe security
#0 20090102122338.d9d2a158...@flens.dfn-cert.de
Schreibe Archivzustand in Datei
/HAmailhost/mailman/archives/private/security/pipermail.pck
Traceback (most recent call last):
File ./arch, line 201, in ?
main()
File ./arch, line 189, in main
archiver.processUnixMailbox(fp, start, end)
File /usr/local/mailman/Mailman/Archiver/pipermail.py, line 578, in
processUnixMailbox
a = self._makeArticle(m, self.sequence)
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 684, in
_makeArticle
mlist=self.maillist)
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 308, in
__init__
charset = message.get_content_charset(cset_out)
File /usr/lib/python2.4/email/Message.py, line 800, in get_content_charset
charset = unicode(charset, 'us-ascii').encode('us-ascii')
TypeError: decoding Unicode is not supported
The archive was completely lost and restored from backup. Any help would be
appropriate.
This is due to an incompatibility between Mailman 2.1.12 and the email
package in some Python 2.4.x releases. See the March 2009 note in the
FAQ at http://wiki.list.org/x/pYA9 which includes a link to a patch
to the Python lib/email/Charset.py module to fix this.
Also see the comment thread in the bug report at
https://bugs.launchpad.net/mailman/+bug/328353.
I'm surprised that this was the only place you noticed this problem.
Are there occasional shunted messages and error log tracebacks?
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Problem with mailing list
Elizabeth Cotterell wrote: Hi there - I have been having problems with my MAILMAN mailing list that my hosting service believes is a MAILMAN related problem rather than a hosting one. I can't post to the list, though the support staff at the hosting service can... My message gets to MAILMAN but disappears into the ether once it has been approved, and isn't showing up in the archives. The list is brilla...@brillante.com.au. How do I get support for this? thanks, Elizabeth So your hosting service offers Mailman lists, but is unwilling or unable to support them. The real answer is to find a host for your lists that is willing to support what they offer. This is complicated by the fact that http://brillante.com.au/mailman/listinfo is a cPanel Mailman. See the FAQ at http://wiki.list.org/x/sYA9. That all said, here's the situation. Mailman will silently discard a message for one of several reasons. All discards are logged in Mailman's vette log which the host can see, but ... The most likely reason is content filtering: filter_content is Yes filter_action is Discard nothing was left after content filtering There are various reasons for this, e.g. the message's type is multipart/related and pass_mime_types doesn't include that type, or the message has only text/html parts and they aren't passed. Other possible reasons include: The post is from a moderated member and member_moderation_action is discard. The post is from a non-member and there is a match in discard_these_nonmembers or generic_nonmember_action is discard. The post matches a header_filter_rules rule with discard action. The incoming message for some reason contains an X-BeenThere: header with the list's address The installation has set ARCHIVE_HTML_SANITIZER to discard html only messages and the list's scrub_nondigest is Yes and this is a text/html message. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Searching across lists and making global changes
On Thu, Dec 17, 2009 at 12:00:34PM -0500, Brian Luria wrote: Thanks please don't (1) reply to list-posts off-list: send them to the list; (2) top-post The site is hosted so I dont have shell access. Only the admin interface etc. I presume that is of no use(?) It doesn't look that way; although if the hosts will write a wrapper to make clone_members/find_members available that may be a help. I don't imagine you're the site-admin, either, for the lists. That said, you might find the thread of which http://www.mail-archive.com/mailman-users@python.org/msg41130.html is a part, of interest. I would suggest that, in the absence of these, you get the users to bloody-well do their housekeeping themselves. Point them to the options page, if necessary, pre-fill a URI with their email address, so something like: http://lists.example.org/mailman/options/listfoo/f...@example.com where they can change their name, and see which other lists that email address is a member of. People asking me -- as listadmin -- to change their subscriptions usually get something like mail me the request from both the old and new address so i know it's not nefarious, or visit http://lists.example.org/help#swapsub for instructions on how to do it yourself. That said, I'm grumpy, and miserable, and believe people should take responsibility for themselves. -- ``Democracy means that if the doorbell rings in the early hours, it is likely to be the milkman.'' (Winston Churchill, attrib.) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Error running bin/mailmanctl restart
I am ready to tear my hair out. Thanks to Mark, I got mailman up and running except for one minor hitch. In my log file I see an endless stream of: 12/17/09 11:56:49 AM com.apple.launchd[1] (org.list.mailmanctl) Throttling respawn: Will start in 10 seconds 12/17/09 11:57:00 AM com.apple.launchd[1] (org.list.mailmanctl) Throttling respawn: Will start in 10 seconds Searching the archives, I found this (The thread starts at http://www.mail-archive.com/mailman-users@python.org/msg53952.html): The only difference between my org.list.mailmanctl.plist and Apple's is my verb *start*, as opposed to Apple's *startf*. I'm baffled by *startf*, which is not supported by mailman and does nothing, either in the CLI or in org.list.mailmanctl.plist. Further on down in the messages I read: I just caught that Bryan notes that he receives an endless succession of those messages where as I see one and that's it. Comparing our launchd .plist files, I see a few differences: Bryan: keyOnDemand/key false/ Me: keyOnDemand/key true/ keyRunAtLoad/key true/ So I made that change to /System/Library/LaunchDaemons/org.list.mailmanctl.plist. Everything appeared to work fine, web interface works, creating a list works but qrunner does not to appear to start on bootup. it appears that I now have to manually run: sudo /usr/share/mailman/bin/mailmanctl start to get mailman to start. That concerns me. I need to know how to get it to start on boot and how to restart itself if it dies. When this is all done, I would be happy to summarize what I learned for http://wiki.list.org/pages/viewpage.action?pageId=4030530. Paul -- Paul Kleeberg p...@fpen.org On Dec 17, 2009, at 9:35 AM, Mark Sapiro wrote: Paul Kleeberg wrote: and get the following error: * Installation directory /var/mailman is not configured properly! * Directory must be owned by group _mailman: /var/mailman /var/mailman is has the settings root:wheel while the files inside are root:_mailman. Do I need to change the group of the /var/mailman directory for the install? I know that change is probably not significant, but I an not sure enough of my knowledge to know. It is only significant to configure in your case, but configure whant the prefix and var_prefix directories to be SETGID and Mailman's group so that subordinates created by make install will be the same. When you originally asked about this off line, I thought what you had would be OK because it was a working installation, but apparently it only works for Apple :( You need to chgrp _mailman /var/mailman chmod g+s /var/mailman to make configure happy. The prefix directory (/usr/share/mailman in your case) needs to be the same. Once I get this right, I plan on upgrading a 10.6.2 production server running 2.1.12rc1 to 2.1.12. FYI, 2.1.13rc1 is released and 2.1.13 final will be released next week barring the unexpected. It fixes several minor bugs in 2.1.12. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Help with an error
Now that I know what a nightmare it is for me to upgrade Apple's installation of Mailman on a 10.5.8 server, I am not eager to upgrade my 10.6.2 server to which this message applies. I would like to apply the patch that Mark sent to me but I see from faq 4.40 that I will need to go through the same process of './configure' and 'make install' as I would with an upgrade. Are there any other options? I would like to leave it alone, but denying a subscription request fails and i keep getting reminders each morning of the pending request. Are there other options to deny the request? Paul -- Paul Kleeberg p...@fpen.org On Dec 13, 2009, at 10:11 AM, Mark Sapiro wrote: Paul Kleeberg wrote: In attending to a subscription request to a sunsetted list (the request came before the migration) via the web interface, I received an error. Here is the mailman error log (I have modified e-mail addresses and the domain name): Dec 13 08:35:55 2009 admin(81221): admin(81221): [- Mailman Version: 2.1.12rc1 -] admin(81221): [- Traceback --] admin(81221): Traceback (most recent call last): admin(81221): File /usr/share/mailman/scripts/driver, line 112, in run_main admin(81221): main() admin(81221): File /BinaryCache/mailman/mailman-132~28/Root/usr/share/mailman/Mailman/Cgi/admindb.py, line 164, in main admin(81221): File /BinaryCache/mailman/mailman-132~28/Root/usr/share/mailman/Mailman/Cgi/admindb.py, line 773, in process_form admin(81221): AttributeError: 'str' object has no attribute 'get' This is a bug in 2.1.12rc1. Upgrade to 2.1.12 or install the attached admindb.patch.txt. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan admindb.patch.txt -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Help with an error
Paul Kleeberg wrote: Now that I know what a nightmare it is for me to upgrade Apple's installation of Mailman on a 10.5.8 server, I am not eager to upgrade my 10.6.2 server to which this message applies. I would like to apply the patch that Mark sent to me but I see from faq 4.40 that I will need to go through the same process of './configure' and 'make install' as I would with an upgrade. Are there any other options? FAQ 4.40 describes a general process for applying patches that could patch files that are input to configure. For the admindb.py patch I gave you, you don't have to do this. Just apply the patch to the installed Mailman/Cgi/admindb.py file. Since it's a CGI, you don't even have to restart Mailman. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Error running bin/mailmanctl restart
--On December 17, 2009 1:21:35 PM -0600 Paul Kleeberg p...@fpen.org wrote: I am ready to tear my hair out. Thanks to Mark, I got mailman up and running except for one minor hitch. In my log file I see an endless stream of: 12/17/09 11:56:49 AM com.apple.launchd[1] (org.list.mailmanctl) Throttling respawn: Will start in 10 seconds12/17/09 11:57:00 AM com.apple.launchd[1] (org.list.mailmanctl) Throttling respawn: Will start in 10 seconds Searching the archives, I found this (The thread starts at http://www.mail-archive.com/mailman-users@python.org/msg53952.html): The only difference between my org.list.mailmanctl.plist and Apple's is my verb *start*, as opposed to Apple's *startf*. I'm baffled by *startf*, which is not supported by mailman and does nothing, either in the CLI or in org.list.mailmanctl.plist. At one point, I compared the stock mailmanctl with that from the one Apple distributes with Mac OS X Server. The only difference was that the 'start' stanza in main() had been cloned as a 'startf' stanza, with a couple of relatively minor changes, primarily (if I remember correctly) to make it not daemonize, since things run from launchd aren't allowed to daemonize. I *think* that that's what's leading to the problem you see -- mailmanctl daemonizes, launchd cleans it up and it respawns, eventually triggering the error. For my Mailman install on Mac OS X (client, not server) I gave up on using launchd to start Mailman at boot time, and just used an old-style StartupItem. I did make launchd scripts for all the Mailman stuff that's normally run out of cron; see the archives of this list for information about those. In short, if you want to use launchd to start Mailman at boot time, I think that you're going to have to look at Apple's version of mailmanctl, and make equivalent changes to the stock mailmanctl to provide a 'startf' variant. If you do that, I urge you to try to do it in a cleaner way than Apple's hack -- my memory is that there were so few differences that it was a crime that they'd just duplicated the entire block of code and commented out parts. NOTE: I was doing this comparison between the mailmanctl from Mac OS X Server 10.5, not 10.6, so it's possible that they cleaned up their act and did things differently. But a quick side-by-side compare of their mailmanctl and the stock one should get you pointed in the right direction. -- Steve Burlingmailto:s...@umich.edu University of Michigan, ICPSRVoice: +1 734 615.3779 330 Packard Street FAX: +1 734 647.8700 Ann Arbor, MI 48104-2910 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Error running bin/mailmanctl restart
I recognize some of my words in what Paul has quoted below so let me comment. The discussion Paul is quoting from dealt with running Mailman on Mac OS X CLIENT whereas Paul is dealing with Mac OS X SERVER. OS X Server comes with a bastardized version of Mailman where as OS X Client has nothing except a Mailman account (Why is the account already there? Who knows!). The undocumented changes Apple has made have been talked about much before and I thought with the conclusion that the Apple provided version in Server is unsupported here due to the kind issues Paul is having. My suggestion would be to remove the Apple provided version of Mailman, the install the official version from source. Once the Apple version is gone, I see no reason that instructions for installing from scratch that I've previously posted would not work. Heck, they might even work fine in parallel with the Apple version (which obviously then should not be allowed to run). I'm pretty sure, if I remember my own instructions correctly, that I have Mailman self-contained within /Applications/mailman except for the startup file in /Library/LaunchDaemons (which might need to be given a slightly different name to avoid a conflict), the modifications to the Apache configuration file, and the modifications to the Postfix configuration file for the aliases (all of which should be preserved by any Apple upgrades). -- Larry Stone lston...@stonejongleux.com On Thu, 17 Dec 2009, Paul Kleeberg wrote: I am ready to tear my hair out. Thanks to Mark, I got mailman up and running except for one minor hitch. In my log file I see an endless stream of: 12/17/09 11:56:49 AM com.apple.launchd[1] (org.list.mailmanctl) Throttling respawn: Will start in 10 seconds 12/17/09 11:57:00 AM com.apple.launchd[1] (org.list.mailmanctl) Throttling respawn: Will start in 10 seconds Searching the archives, I found this (The thread starts at http://www.mail-archive.com/mailman-users@python.org/msg53952.html): The only difference between my org.list.mailmanctl.plist and Apple's is my verb *start*, as opposed to Apple's *startf*. I'm baffled by *startf*, which is not supported by mailman and does nothing, either in the CLI or in org.list.mailmanctl.plist. Further on down in the messages I read: I just caught that Bryan notes that he receives an endless succession of those messages where as I see one and that's it. Comparing our launchd .plist files, I see a few differences: Bryan: keyOnDemand/key false/ Me: keyOnDemand/key true/ keyRunAtLoad/key true/ So I made that change to /System/Library/LaunchDaemons/org.list.mailmanctl.plist. Everything appeared to work fine, web interface works, creating a list works but qrunner does not to appear to start on bootup. it appears that I now have to manually run: sudo /usr/share/mailman/bin/mailmanctl start to get mailman to start. That concerns me. I need to know how to get it to start on boot and how to restart itself if it dies. When this is all done, I would be happy to summarize what I learned for http://wiki.list.org/pages/viewpage.action?pageId=4030530. Paul -- Paul Kleeberg p...@fpen.org On Dec 17, 2009, at 9:35 AM, Mark Sapiro wrote: Paul Kleeberg wrote: and get the following error: * Installation directory /var/mailman is not configured properly! * Directory must be owned by group _mailman: /var/mailman /var/mailman is has the settings root:wheel while the files inside are root:_mailman. Do I need to change the group of the /var/mailman directory for the install? I know that change is probably not significant, but I an not sure enough of my knowledge to know. It is only significant to configure in your case, but configure whant the prefix and var_prefix directories to be SETGID and Mailman's group so that subordinates created by make install will be the same. When you originally asked about this off line, I thought what you had would be OK because it was a working installation, but apparently it only works for Apple :( You need to chgrp _mailman /var/mailman chmod g+s /var/mailman to make configure happy. The prefix directory (/usr/share/mailman in your case) needs to be the same. Once I get this right, I plan on upgrading a 10.6.2 production server running 2.1.12rc1 to 2.1.12. FYI, 2.1.13rc1 is released and 2.1.13 final will be released next week barring the unexpected. It fixes several minor bugs in 2.1.12. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives:
Re: [Mailman-Users] Error running bin/mailmanctl restart
On Dec 17, 2009, at 03:35 PM, Steve Burling wrote: At one point, I compared the stock mailmanctl with that from the one Apple distributes with Mac OS X Server. The only difference was that the 'start' stanza in main() had been cloned as a 'startf' stanza, with a couple of relatively minor changes, primarily (if I remember correctly) to make it not daemonize, since things run from launchd aren't allowed to daemonize. I *think* that that's what's leading to the problem you see -- mailmanctl daemonizes, launchd cleans it up and it respawns, eventually triggering the error. Could someone submit a bug on this here: https://bugs.launchpad.net/mailman I think it would be useful to support a no-daemonize option to the 'bin/mailman start' command in Mailman 3. -Barry signature.asc Description: PGP signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Error running bin/mailmanctl restart
--On December 17, 2009 4:12:29 PM -0500 Barry Warsaw ba...@list.org wrote: Could someone submit a bug on this here: https://bugs.launchpad.net/mailman I think it would be useful to support a no-daemonize option to the 'bin/mailman start' command in Mailman 3. To which I reply: Done. -- Steve Burlingmailto:s...@umich.edu University of Michigan, ICPSRVoice: +1 734 615.3779 330 Packard Street FAX: +1 734 647.8700 Ann Arbor, MI 48104-2910 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Error running bin/mailmanctl restart
On Thu, 17 Dec 2009, Steve Burling wrote: At one point, I compared the stock mailmanctl with that from the one Apple distributes with Mac OS X Server. The only difference was that the 'start' stanza in main() had been cloned as a 'startf' stanza, with a couple of relatively minor changes, primarily (if I remember correctly) to make it not daemonize, since things run from launchd aren't allowed to daemonize. I *think* that that's what's leading to the problem you see -- mailmanctl daemonizes, launchd cleans it up and it respawns, eventually triggering the error. I forgot about the deamonizing issue. But, it can sort of be worked around. In the note Paul quoted from, we have (and I am the Me in the quote; I forget who Bryan is): I just caught that Bryan notes that he receives an endless succession of those messages where as I see one and that's it. Comparing our launchd .plist files, I see a few differences: Bryan: keyOnDemand/key false/ Me: keyOnDemand/key true/ keyRunAtLoad/key true/ With OnDemand set to false, launchctl thinks you want mailmanctl always running. But mailmanctl daemonizes and exits so launchctl tries to restart it. With my OnDemand set to true and RunAtLoad set to true, launchctl tries to run mailmanctl once at boot and is done with it. That mailmanctl exits is find. But it comes at the cost of launchctl not knowing anything about Mailman after mailmanctl exits. It won't restart it if it subsequently dies (has not been a problem for me. I have a cron job that runs hourly and e-mails me if a qrunner is missing not that one ever is once it's up and running). But Paul mentioned that he tried OnDemand = true and RunAtLoad = true and no qrunners (Paul, did you reboot or force a reload of the launchd plist for mailman?). So we'd need to see log files as to what's happening. If there's nothing in any logfile (including system.log), then I'd guess the plist was never reloaded. -- Larry Stone lston...@stonejongleux.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Error running bin/mailmanctl restart
On Dec 17, 2009, at 04:30 PM, Steve Burling wrote: Done. Thanks! -Barry signature.asc Description: PGP signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Increasing the Speed of Email Delivery
I'm currently using a dedicated cPanel server with the following specs. Xeon 3060 - Dual Core 2.4 GHz - 250GB SATA-II HDD - 2GB DDR2 RAM; RedHat/cPanel It currently takes me about 6 hours to deliver 800K emails. It's an announce only list with 20 sublists of 40K addresses. I will be upgrading to: Xeon 3450 - SATA - Quad Core 2.66 GHz - 250 GB IDE/SATA, 7200rpm - 4GB DDR3 RAM; RedHat/cPanel and wanted to know if my email deliver would be much faster. Any assistance/direction with server configuration would be greatly appreciated. -Derrick Wooden -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Increasing the Speed of Email Delivery
On Thu, Dec 17, 2009 at 04:14:03PM -0600, Derrick Wooden wrote: I will be upgrading to: Xeon 3450 - SATA - Quad Core 2.66 GHz - 250 GB IDE/SATA, 7200rpm - 4GB DDR3 RAM; RedHat/cPanel Regarding cPanel, see http://wiki.list.org/x/sYA9. and wanted to know if my email deliver would be much faster. You've not said which MTA, how that's been tweaked, how the spools are handled (or indeed, partitioned), what else the machine's doing, the connectivity of the machine, ISP infrastructure, destination servers, geography/latency, or a ~bundle~ of other things. Any assistance/direction with server configuration would be greatly appreciated. There have been some recent posts on this, that I didn't pay much attention to, but they'll be in the list archive. ISTR djb's Qmail being involved by the OP, and others suggesting the use of a different MTA. -- Go mad this weekend: buy some beef! (advert at a supermarket) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Increasing the Speed of Email Delivery
Lots of it depends on the MTA (general opinion is that postfix seems to be the fastest), connectivity, and list settings (personalized email will take much longer). Check out the FAQ for performance, and as Adam mentioned, the list archives) FWIW, before you change hardware, have you looked at which resources are constrained? Also, if it's a dedicated server, why are you using cpanel? z! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Increasing the Speed of Email Delivery
Adam McGreggor-2 wrote: You've not said which MTA, how that's been tweaked, how the spools are handled (or indeed, partitioned), what else the machine's doing, the connectivity of the machine, ISP infrastructure, destination servers, geography/latency, or a ~bundle~ of other things. The MTA is Exim. I paid someone to set up this server for Mailman 3 years ago, but am not certain about partitioning. I have access to the dedicated server. If given directions I could give you which ever settings are needed. The 4 partions are: /dev/sda5, mounted at / [root] (227GB/136GB free) /dev/sda1, mounted at /boot (99MB/78MB free), /dev/sda3, mounted at /tmp (1012 MB/927MB free), and /tmp, mounted at /var/tmp (also 1012MB/927MB free) The machine only has one domain on it and is used specifically for newsletters using Mailman. Nothing else. Not even website pages. The server is hosted by ThePlanet.com and the servers were in Houston when this was setup 3 years ago. Adam McGreggor-2 wrote: On Thu, Dec 17, 2009 at 04:14:03PM -0600, Derrick Wooden wrote: I will be upgrading to: Xeon 3450 - SATA - Quad Core 2.66 GHz - 250 GB IDE/SATA, 7200rpm - 4GB DDR3 RAM; RedHat/cPanel Regarding cPanel, see http://wiki.list.org/x/sYA9. and wanted to know if my email deliver would be much faster. You've not said which MTA, how that's been tweaked, how the spools are handled (or indeed, partitioned), what else the machine's doing, the connectivity of the machine, ISP infrastructure, destination servers, geography/latency, or a ~bundle~ of other things. Any assistance/direction with server configuration would be greatly appreciated. There have been some recent posts on this, that I didn't pay much attention to, but they'll be in the list archive. ISTR djb's Qmail being involved by the OP, and others suggesting the use of a different MTA. -- Go mad this weekend: buy some beef! (advert at a supermarket) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com -- View this message in context: http://old.nabble.com/Increasing-the-Speed-of-Email-Delivery-tp26837149p26837735.html Sent from the Mailman - Users mailing list archive at Nabble.com. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Increasing the Speed of Email Delivery
Carl Zwanzig wrote: Also, if it's a dedicated server, why are you using cpanel? When I first started experimenting with MailMan 3 years ago, I used cPanel to add/remove my mailing lists, but have since learned how to do a few things via SSH. Is the implication that cPanel would hinder the optimal performance of the MTA and/or Mailman? Carl Zwanzig wrote: Lots of it depends on the MTA (general opinion is that postfix seems to be the fastest), connectivity, and list settings (personalized email will take much longer). Check out the FAQ for performance, and as Adam mentioned, the list archives) FWIW, before you change hardware, have you looked at which resources are constrained? Also, if it's a dedicated server, why are you using cpanel? z! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com -- View this message in context: http://old.nabble.com/Increasing-the-Speed-of-Email-Delivery-tp26837149p26837773.html Sent from the Mailman - Users mailing list archive at Nabble.com. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Increasing the Speed of Email Delivery
Additional information: Mailman 2.1.11.cp3 MTA - Exim 4 Exim Config: queue_only #smtp_connect_backlog = 200 #smtp_accept_max = 500 auto_thaw = 1d ignore_bounce_errors_after = 12h timeout_frozen_after = 2d split_spool_directory = yes queue_run_max = 20 remote_max_parallel = 20 smtp_connect_backlog = 50 smtp_accept_max = 100 deliver_queue_load_max = 25 # turn off writing of logs to /var/spool/exim_incoming/msglog/ no_message_logs Derrick Wooden wrote: Adam McGreggor-2 wrote: You've not said which MTA, how that's been tweaked, how the spools are handled (or indeed, partitioned), what else the machine's doing, the connectivity of the machine, ISP infrastructure, destination servers, geography/latency, or a ~bundle~ of other things. The MTA is Exim. I paid someone to set up this server for Mailman 3 years ago, but am not certain about partitioning. I have access to the dedicated server. If given directions I could give you which ever settings are needed. The 4 partions are: /dev/sda5, mounted at / [root] (227GB/136GB free) /dev/sda1, mounted at /boot (99MB/78MB free), /dev/sda3, mounted at /tmp (1012 MB/927MB free), and /tmp, mounted at /var/tmp (also 1012MB/927MB free) The machine only has one domain on it and is used specifically for newsletters using Mailman. Nothing else. Not even website pages. The server is hosted by ThePlanet.com and the servers were in Houston when this was setup 3 years ago. Adam McGreggor-2 wrote: On Thu, Dec 17, 2009 at 04:14:03PM -0600, Derrick Wooden wrote: I will be upgrading to: Xeon 3450 - SATA - Quad Core 2.66 GHz - 250 GB IDE/SATA, 7200rpm - 4GB DDR3 RAM; RedHat/cPanel Regarding cPanel, see http://wiki.list.org/x/sYA9. and wanted to know if my email deliver would be much faster. You've not said which MTA, how that's been tweaked, how the spools are handled (or indeed, partitioned), what else the machine's doing, the connectivity of the machine, ISP infrastructure, destination servers, geography/latency, or a ~bundle~ of other things. Any assistance/direction with server configuration would be greatly appreciated. There have been some recent posts on this, that I didn't pay much attention to, but they'll be in the list archive. ISTR djb's Qmail being involved by the OP, and others suggesting the use of a different MTA. -- Go mad this weekend: buy some beef! (advert at a supermarket) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com -- View this message in context: http://old.nabble.com/Increasing-the-Speed-of-Email-Delivery-tp26837149p26838225.html Sent from the Mailman - Users mailing list archive at Nabble.com. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Meta: bringing along the newcomers
Somebody-whom-I-don't-want-to-pick-on-in-particular writes: On Thu, Dec 17, 2009 at 12:00:34PM -0500, (Some) Poor Fellow wrote: Thanks please don't (1) reply to list-posts off-list: send them to the list; (2) top-post Given the recent surge in non-traditional list admins (ie, folks without a Unix or mail admin background), I feel this is excessively curt. I don't know about this particular Poor Fellow, but the generic Poor Fellow probably had no idea it wasn't going to the right place (he probably isn't subscribed, either, so he won't notice that he didn't get his own post back). I suggest that better wording is Please be careful to ensure that your reply is addressed to the list. Actually there should be a FAQ for that in Section 1, so you can add see FAQ x.yy. I suggest adding this to FAQ 1.22. Something like 1.22 How should I write my post when asking a question on this mailing list? Customs vary on the Internet, and while we [except for the majority of us old Usenet curmudgeons ;-] don't want to impose our customs on the rest of the 'Net, your questions *will* be answered more quickly and helpfully if you observe the following: o The first thing you should do is indicate that you've done your homework. Look at the Mailman documentation linked from http://www.list.org/docs.html. Search the Frequently Asked Questions in the wiki. Search the archives of the mailing list (see How do I search the archives of the mailman-users mailing list?). Once you've looked through all the relevant pieces of documentation, FAQ entries, archive messages, etc... and you still haven't found your answer, please give us additional information as well as the question itself. See FAQ . Specifically, we would like to know: 1. What methods did you use to look through the documentation and search the FAQ, mailing list archives, etc...? 2. If there were things that initially sounded relevant but ended up not being useful to you, which ones were they? If you did miss something that is relevant, then having this information will help us go back and improve the documentation/FAQ/etc... so that the next person who does the same search will hopefully hit the correct answer. In addition, we would appreciate it if you could provide URLs and precise descriptions of the information you found but which was not helpful to you. o If you have a specific/detailed question, please proceed to FAQ entry 1.23 at I have a specific-detailed question -- What kind of information do I need to provide when posting a question to this mailing list? See also FAQ entry 4.78 Troubleshooting- No mail going out to lists members. With this information, we are much more likely to be able to provide you assistance with your question. o Be careful to ensure that your reply is addressed to the list. The widespread practice of Reply-To munging is *not* implemented on our lists because it makes it difficult (and sometimes impossible) to send a private reply. Because this need is frequent in working on Mailman issues (many questions involve details of network and host configuration that could be used by crackers to compromise security), we do not set Reply-To to the list. (Reply-To munging is not a good idea in most cases; see Chip Rosenthal's essay Reply-To Munging Considered Harmful.) o It is a very good idea to subscribe to the list, or at least follow the thread in the archives. For various reasons, related posts may *not* be addressed to you, but only to the list. It would be a shame if you missed them. o Once you've sent your post, *wait* at least 48 hours for it to be forwarded to you or appear in the archives before assuming it got lost. Because we must allow non-members to post, we are relatively vulnerable to spam, and the lists are *moderated* by rather busy volunteers. Also, make sure that any spamblocking software you have is *off* for a while; you will get no sympathy at all if you block a reply (and note you don't know where it will come from, because the respondent may feel that the required information is sensitive, and should not be discussed in public -- see #2 above). No sympathy for the delay itself, and many of the less frequent contributors will ignore you completely thereafter. (The core people will still take care of you, but about half the useful answers come from the peanut gallery -- it's a significant resource.) o Avoid top-posting (adding a quick comment to the top of a message, leaving the automatically included quoted block intact.
Re: [Mailman-Users] Increasing the Speed of Email Delivery
d-woo writes: When I first started experimenting with MailMan 3 years ago, I used cPanel to add/remove my mailing lists, but have since learned how to do a few things via SSH. Is the implication that cPanel would hinder the optimal performance of the MTA and/or Mailman? Maybe a little. The big issue is that it hinders *your* performance, because your questions on Mailman lists will often get the totally non-responsive response See FAQ http://wiki.list.org/x/sYA9. IOW, the mere mention of cPanel (or Plesk) causes Mailman-Users to abort and dump core, which is not very useful to you. P.S. Read that FAQ. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Increasing the Speed of Email Delivery
Stephen J. Turnbull wrote: IOW, the mere mention of cPanel (or Plesk) causes Mailman-Users to abort and dump core, which is not very useful to you. I have been doing a lot of reading along that wise. As a result I'm setting up the new server with no cPanel and will use Postfix as my MTA. I will do a clean install of Mailman 2.13 so that I can be on the same page as most users. I read in a 2004 (or earlier thread) where using MySQL db tables would also increase the speed. I will also utilize this option. Stephen J. Turnbull wrote: d-woo writes: When I first started experimenting with MailMan 3 years ago, I used cPanel to add/remove my mailing lists, but have since learned how to do a few things via SSH. Is the implication that cPanel would hinder the optimal performance of the MTA and/or Mailman? Maybe a little. The big issue is that it hinders *your* performance, because your questions on Mailman lists will often get the totally non-responsive response See FAQ http://wiki.list.org/x/sYA9. IOW, the mere mention of cPanel (or Plesk) causes Mailman-Users to abort and dump core, which is not very useful to you. P.S. Read that FAQ. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/lists%40nabble.com -- View this message in context: http://old.nabble.com/Increasing-the-Speed-of-Email-Delivery-tp26837149p26839632.html Sent from the Mailman - Users mailing list archive at Nabble.com. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
