Re: [Mailman-Users] external web interface
Hi again
I will use the first solution for the moment as I want 2 web servers: an
internal one and one in our dmz for testing purpose.
The VIRTUAL_HOST_OVERVIEW = Off setting works great and I got no longer a 'bug'
error on list creation.
I keep the second way in mind for future usage
Continue testing...
Thx mark
-Message d'origine-
De : Mark Sapiro [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 18 octobre 2006 19:40
À : BRAVAL François; mailman-users@python.org
Objet : Re: [Mailman-Users] external web interface
Mark Sapiro wrote:
BRAVAL François wrote:
-add to mm_cfg.py :
DEFAULT_URL_HOST ='machine2.mydomain.com'
add_virtualhost('machine2.mydomain.com','machine1.mydomain.com')
This has to do with the problem - see below.
snip
Setting DEFAULT_URL_HOST and add_virtual_host in mm_cfg.py
won't affect
this. What you need in mm_cfg.py is
VIRTUAL_HOST_OVERVIEW = Off
so all lists will appear on all domain's overview pages.
Actually, if you want to access the web interface only from machine2,
the above DEFAULT_URL_HOST and add_virtual_host settings are what you
want, and you don't need VIRTUAL_HOST_OVERVIEW = Off, but you also
need to run fix_url to update the existing lists' web_page_url as
explained in
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.
069.htp.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman-Users Digest, Vol 32, Issue 43
Merci pour vos messages! mais je ne comprends pas bien l'anglais. Largement informé de vos activités, je vous suggère de supprimer mon adresse. Tous mes bons voeux, Patrice Rossel Ursprüngliche Nachricht Von: [EMAIL PROTECTED] Datum: 19.10.2006 12:00 An: mailman-users@python.org Betreff: Mailman-Users Digest, Vol 32, Issue 43 Send Mailman-Users mailing list submissions to mailman-users@python.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/mailman-users or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of Mailman-Users digest... Today's Topics: 1. external web interface (BRAVAL Fran?ois) 2. Mailman 2.1.9_rc1 (Roman Hultay) 3. Re: external web interface (Mark Sapiro) 4. Re: Mailman 2.1.9_rc1 (Mark Sapiro) 5. Re: external web interface (Mark Sapiro) 6. Can't send messages to list (Lukasz Szybalski) 7. Re: Can't send messages to list (Mark Sapiro) 8. Re: external web interface (BRAVAL Fran?ois) -- 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/ -- 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] external web interface
Err.. No
In fact, it doesn't seem to work.
The URL is machine2.domain.com but the title of the page is machine1.domain.com
When I create a new list, it uses the machine1.domain.com domain
If I remove the VIRTUAL_HOST_OVERVIEW = Off and set the DEFAULT_URL_HOST to
machine2.domain.com. I get a 'bug' error.
See my error log.
Oct 19 13:32:48 2006 (10276) command failed: /usr/sbin/postalias
/usr/local/mailman/data/aliases (status: 127, Unknown error 127)
Oct 19 13:32:48 2006 admin(10276):
admin(10276): [- Mailman Version: 2.1.9 -]
admin(10276): [- Traceback --]
admin(10276): Traceback (most recent call last):
admin(10276): File /usr/local/mailman/scripts/driver, line 101, in run_main
admin(10276): main()
admin(10276): File /usr/local/mailman/Mailman/Cgi/create.py, line 56, in
main
admin(10276): process_request(doc, cgidata)
admin(10276): File /usr/local/mailman/Mailman/Cgi/create.py, line 238, in
process_request
admin(10276): sys.modules[modname].create(mlist, cgi=1)
admin(10276): File /usr/local/mailman/Mailman/MTA/Postfix.py, line 232, in
create
admin(10276): _update_maps()
admin(10276): File /usr/local/mailman/Mailman/MTA/Postfix.py, line 53, in
_update_maps
admin(10276): raise RuntimeError, msg % (acmd, status, errstr)
admin(10276): RuntimeError: command failed: /usr/sbin/postalias
/usr/local/mailman/data/aliases (status: 127, Unknown error 127)
admin(10276): [- Python Information -]
admin(10276): sys.version = 2.4.1 (#1, May 16 2005, 15:19:29)
[GCC 4.0.0 20050512 (Red Hat 4.0.0-5)]
admin(10276): sys.executable = /usr/bin/python
admin(10276): sys.prefix = /usr
admin(10276): sys.exec_prefix = /usr
admin(10276): sys.path= /usr
admin(10276): sys.platform= linux2
admin(10276): [- Environment Variables -]
admin(10276): HTTP_COOKIE:
test3+admin=28020069d40f364573280031373330346536393039363237623233393263616130383239646231353366643932383335656338;
test+admin=280200695bcb364573280066306166346133613861626464656366333133666162353636393864393733383731383335356535
admin(10276): SERVER_SOFTWARE: Apache/2.0.54 (Fedora)
admin(10276): SCRIPT_NAME: /mailman/create
admin(10276): SERVER_SIGNATURE: addressApache/2.0.54 (Fedora) Server at
machine2.domain.fr Port 80/address
admin(10276):
admin(10276): REQUEST_METHOD: POST
admin(10276): HTTP_KEEP_ALIVE: 300
admin(10276): SERVER_PROTOCOL: HTTP/1.1
admin(10276): QUERY_STRING:
admin(10276): CONTENT_LENGTH: 151
admin(10276): HTTP_ACCEPT_CHARSET: ISO-8859-1,utf-8;q=0.7,*;q=0.7
admin(10276): HTTP_USER_AGENT: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr;
rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7
admin(10276): HTTP_CONNECTION: keep-alive
admin(10276): HTTP_REFERER: http://machine2.domain.fr
admin(10276): SERVER_NAME: machine2.domain.fr
admin(10276): REMOTE_ADDR: 194.xx.xxx.11
admin(10276): SERVER_PORT: 80
admin(10276): SERVER_ADDR: 194.xx.xxx.157
admin(10276): DOCUMENT_ROOT: /var/www/html
admin(10276): PYTHONPATH: /usr/local/mailman
admin(10276): SCRIPT_FILENAME: /usr/local/mailman/cgi-bin/create
admin(10276): SERVER_ADMIN: [EMAIL PROTECTED]
admin(10276): HTTP_HOST: machine2.domain.fr
admin(10276): REQUEST_URI: /mailman/create
admin(10276): HTTP_ACCEPT:
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
admin(10276): GATEWAY_INTERFACE: CGI/1.1
admin(10276): REMOTE_PORT: 1315
admin(10276): HTTP_ACCEPT_LANGUAGE: fr,fr-fr;q=0.8,en-us;q=0.5,en;q=0.3
admin(10276): CONTENT_TYPE: application/x-www-form-urlencoded
admin(10276): HTTP_ACCEPT_ENCODING: gzip,deflate
-Message d'origine-
De :
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
on.org] De la part de BRAVAL François
Envoyé : jeudi 19 octobre 2006 10:20
À : Mark Sapiro; mailman-users@python.org
Objet : Re: [Mailman-Users] external web interface
Hi again
I will use the first solution for the moment as I want 2 web
servers: an internal one and one in our dmz for testing purpose.
The VIRTUAL_HOST_OVERVIEW = Off setting works great and I got
no longer a 'bug' error on list creation.
I keep the second way in mind for future usage
Continue testing...
Thx mark
-Message d'origine-
De : Mark Sapiro [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 18 octobre 2006 19:40
À : BRAVAL François; mailman-users@python.org
Objet : Re: [Mailman-Users] external web interface
Mark Sapiro wrote:
BRAVAL François wrote:
-add to mm_cfg.py :
='machine2.mydomain.com'
add_virtualhost('machine2.mydomain.com','machine1.mydomain.com')
This has to do with the problem - see below.
snip
Setting DEFAULT_URL_HOST and add_virtual_host in mm_cfg.py
won't affect
this. What you need in mm_cfg.py is
VIRTUAL_HOST_OVERVIEW = Off
so all lists will
[Mailman-Users] Outgoing Lists
How would one go about changing the To: field in received mailings? i.e. it currently says '[EMAIL PROTECTED]' but is it possible for it to say the recipient? This would mean that each message is different for each recipient atleast in the header. -- 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] external web interface
BRAVAL François wrote: If I remove the VIRTUAL_HOST_OVERVIEW = Off and set the DEFAULT_URL_HOST to machine2.domain.com. I get a 'bug' error. See my error log. Oct 19 13:32:48 2006 (10276) command failed: /usr/sbin/postalias /usr/local/mailman/data/aliases (status: 127, Unknown error 127) Oct 19 13:32:48 2006 admin(10276): admin(10276): [- Mailman Version: 2.1.9 -] admin(10276): [- Traceback --] admin(10276): Traceback (most recent call last): admin(10276): File /usr/local/mailman/scripts/driver, line 101, in run_main admin(10276): main() admin(10276): File /usr/local/mailman/Mailman/Cgi/create.py, line 56, in main admin(10276): process_request(doc, cgidata) admin(10276): File /usr/local/mailman/Mailman/Cgi/create.py, line 238, in process_request admin(10276): sys.modules[modname].create(mlist, cgi=1) admin(10276): File /usr/local/mailman/Mailman/MTA/Postfix.py, line 232, in create admin(10276): _update_maps() admin(10276): File /usr/local/mailman/Mailman/MTA/Postfix.py, line 53, in _update_maps admin(10276): raise RuntimeError, msg % (acmd, status, errstr) admin(10276): RuntimeError: command failed: /usr/sbin/postalias = /usr/local/mailman/data/aliases (status: 127, Unknown error 127) This issue should have nothing to do with the settings of VIRTUAL_HOST_OVERVIEW and DEFAULT_URL_HOST in mm_cfg.py. The list has been created and the data/aliases and, if the host is in POSTFIX_STYLE_VIRTUAL_DOMAINS, the data/virtual-mailman files have been updated, and now the Postfix MTA module is calling /usr/sbin/postalias to update the data/aliases.db file, and the postalias command fails. Assuming /usr/sbin/postalias is the correct path (if not, set it in mm_cfg.py with POSTFIX_ALIAS_CMD), this is almost certainly an ownership/permissions issue. Permissions should be at least 0660 on both the aliases and aliases.db files and the owner:group should be the mailman user:group. In older versions, bin/check_perms doesn't check all this. -- 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] What is them max subject length?
Hello Mailman Users, I recently rolled out a new mailserver and decided to use Mailman as the mailing list software. Everything has been going smoothly except for one minor issue: it looks like sometimes a subject is too long and gets turned into (No Subject), while the real subject becomes the first line of the email. I'd like to either change this setting or let my end users know how long is too long, but I can't find the max subject length documented anywhere, nor did it jump out at me on the web interface. I'm sure it's documented somewhere, but after checking the FAQ, the Wiki, Google and The Fine Manuals I'm stumped. Could someone point me in the right direction? Or does Mailman not do this at all and I should look into that user's email client? Thanks, Nate Nolet -- 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] Outgoing Lists
Roman Hultay wrote: How would one go about changing the To: field in received mailings? i.e. it currently says '[EMAIL PROTECTED]' but is it possible for it to say the recipient? This would mean that each message is different for each recipient atleast in the header. This is called Full personalization, and it is one of the settings under Non-digest options if the installation is set so owners can enable list personalization. I.e., OWNERS_CAN_ENABLE_PERSONALIZATION = Yes in mm_cfg.py. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.015.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] What is them max subject length?
Nathaniel Nolet wrote: it looks like sometimes a subject is too long and gets turned into (No Subject), while the real subject becomes the first line of the email. I'd like to either change this setting or let my end users know how long is too long, but I can't find the max subject length documented anywhere, nor did it jump out at me on the web interface. I'm sure it's documented somewhere, but after checking the FAQ, the Wiki, Google and The Fine Manuals I'm stumped. Could someone point me in the right direction? Or does Mailman not do this at all and I should look into that user's email client? There is no setting per se, nor is there any limit on Subject: length per se. Mailman does manipulate Subject: headers in the process of adding the subject_prefix if any. This may result in a subject which is originally a single line being folded into multiple lines in accord with RFC 2822, but all Subject: headers sent by Mailman should conform to the RFC. Look at the raw message as sent by Mailman. If the Subject: header is not compliant with RFC 2822, then report that here. Otherwise, look at the user's MUA (email client). Note that if this only affects one or a few recipients of the message but not all recipients, it is almost certainly a user's MUA issue. -- 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] can't get mailman and exim4 talking on my debian 3.1
For some reason, after a recent nightmare with a hosed partition table, my system which had a working Mailman 2.1.5 version on it, now refuses to connect to exim4 and get my mail out to my lists. Here's a snippted from /var/log/mailman/smtp-failure. I have no idea what these things mean but hoping someone here can help: Oct 19 11:36:12 2006 (2493) Low level smtp error: (110, 'Connection timed out'), msgid: [EMAIL PROTECTED] Oct 19 11:36:12 2006 (2493) delivery to [EMAIL PROTECTED] failed with code -1: (110, 'Connection timed out') Oct 19 11:39:21 2006 (2493) Low level smtp error: (110, 'Connection timed out'), msgid: [EMAIL PROTECTED] Oct 19 11:39:22 2006 (2493) delivery to [EMAIL PROTECTED] failed with code -1: (110, 'Connection timed out') Oct 19 11:40:54 2006 (2493) Low level smtp error: (4, 'Interrupted system call'), msgid: [EMAIL PROTECTED] Oct 19 11:40:55 2006 (2493) delivery to [EMAIL PROTECTED] failed with code -1: (4, 'Interrupted system call') Oct 19 11:44:16 2006 (5556) Low level smtp error: (110, 'Connection timed out'), msgid: [EMAIL PROTECTED] Oct 19 11:44:16 2006 (5556) delivery to [EMAIL PROTECTED] failed with code -1: (110, 'Connection timed out') Oct 19 11:47:26 2006 (5556) Low level smtp error: (110, 'Connection timed out'), msgid: [EMAIL PROTECTED] Oct 19 11:47:26 2006 (5556) delivery to [EMAIL PROTECTED] failed with code -1: (110, 'Connection timed out') When I revived my system, I couldn't get mailman to even respond until I changed my exim4.conf.template file to exim4.conf.template.new, replacing it with my older exim4.conf.template file. The .new file which apparently was created during an apt-get update pass, contained NO INFORMATION ABOUT MAILMAN, while the old exim4.conf.template file had all my Mailman references. I am reading the [EMAIL PROTECTED]@%^$%*ing manual, for those who would urge the RTFM invective upon me. As yet, I can find no answers to help resolve this. It would be nice if there were some probe utility that would verify everything that needs to be in place, for mailman to work on a debian system. Thanks for any suggestions with this. btw, if I send to one of my lists, I get no response at any included list recipient addresses though the message shows up in the archives for the list as if it had gone out. Correction, the archives of all my lists work, i.e., thy collect mail sent out to each list, though none of the mail sent reaches any recipient. Scott signature.asc Description: Digital signature -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] can't get mailman and exim4 talking on my debian 3.1
Dr. Scott S. Jones wrote: For some reason, after a recent nightmare with a hosed partition table, my system which had a working Mailman 2.1.5 version on it, now refuses to connect to exim4 and get my mail out to my lists. Here's a snippted from /var/log/mailman/smtp-failure. I have no idea what these things mean but hoping someone here can help: Oct 19 11:36:12 2006 (2493) Low level smtp error: (110, 'Connection timed out'), msgid: [EMAIL PROTECTED] Oct 19 11:36:12 2006 (2493) delivery to [EMAIL PROTECTED] failed with code -1: (110, 'Connection timed out') Oct 19 11:39:21 2006 (2493) Low level smtp error: (110, 'Connection timed out'), msgid: [EMAIL PROTECTED] Oct 19 11:39:22 2006 (2493) delivery to [EMAIL PROTECTED] failed with code -1: (110, 'Connection timed out') Oct 19 11:40:54 2006 (2493) Low level smtp error: (4, 'Interrupted system call'), msgid: [EMAIL PROTECTED] Oct 19 11:40:55 2006 (2493) delivery to [EMAIL PROTECTED] failed with code -1: (4, 'Interrupted system call') Oct 19 11:44:16 2006 (5556) Low level smtp error: (110, 'Connection timed out'), msgid: [EMAIL PROTECTED] Oct 19 11:44:16 2006 (5556) delivery to [EMAIL PROTECTED] failed with code -1: (110, 'Connection timed out') Oct 19 11:47:26 2006 (5556) Low level smtp error: (110, 'Connection timed out'), msgid: [EMAIL PROTECTED] Oct 19 11:47:26 2006 (5556) delivery to [EMAIL PROTECTED] failed with code -1: (110, 'Connection timed out') See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.073.htp. When I revived my system, I couldn't get mailman to even respond until I changed my exim4.conf.template file to exim4.conf.template.new, replacing it with my older exim4.conf.template file. The .new file which apparently was created during an apt-get update pass, contained NO INFORMATION ABOUT MAILMAN, while the old exim4.conf.template file had all my Mailman references. Almost all if not absolutely all Mailman specific stuff in exim.conf has to do with delivery of incoming mail to Mailman, not with Mailman sending. Is Exim listening and accepting connects on localhost port 25? Can you successfully 'telnet localhost 25'? It would be nice if there were some probe utility that would verify everything that needs to be in place, for mailman to work on a debian system. That request/remark would be more appropriate on a Debian support list. btw, if I send to one of my lists, I get no response at any included list recipient addresses though the message shows up in the archives for the list as if it had gone out. Correction, the archives of all my lists work, i.e., thy collect mail sent out to each list, though none of the mail sent reaches any recipient. So incoming mail is reaching Mailman (presumably through the Mailman spesific router and transport in Exim) and being processed by Mailman whish is unable to send to the list members because of the errors logged in smtp-failure. This basically says everything is working except SMTP delivery from Mailman to Exim. -- 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] Auto-deleting mail from outside .no?
On 10/17/06 9:00 AM, Thomas Gramstad [EMAIL PROTECTED] wrote: I have many small lists in Norwegian and they're all being hit by a lot of spam. Yes, the spam filter holds them back -- but then I get a /lot/ of mail about new messages waiting, and it's a big job moderating them. What I really want is the option to set that anything mailed from an address that does not end with .no is automatically deleted and I never see it. Is that possible, per list or even per domain/for all lists? As has been said, the MTA is likely the better venue for doing this, as SMTP 5xx rejections can be arranged. That aside, are there *no* .com, .org, .edu etc within Norway (without the trailing .no), which contain potential list subscribers? For example, no one at hydro.com would want to be a list member. (Domain obtained on my first attempt, a Google search for Norsk Hydro.) --John -- 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 performance
Hello, I'm using Mailman 2.1.5 and Postfix to manage a small (~500) member list and I recently went through and removed everyone from the list, and then added them back in. After doing so I was watching the progress of sending the Welcome message, and noticed that Mailman is taking an exceptionally long time to send the messages out. It looks like the messages are getting stuck in the qfiles/out directory, and the smtp log shows many of the following entries: Oct 19 17:30:12 2006 (2411) [EMAIL PROTECTED] smtp for 1 recips, completed in 80.170 seconds Every message is taking almost exactly 80.1 seconds, with no derivation. Postfix's mailq is empty, and all other mail is getting through just fine. Anyone have any suggestions? Why is it taking so long for it to send each message? Thanks! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Mailman performance
Blatter, Nicholas wrote: Every message is taking almost exactly 80.1 seconds, with no derivation. Postfix's mailq is empty, and all other mail is getting through just fine. Anyone have any suggestions? Why is it taking so long for it to send each message? Because it takes Postfix that long to respond to something. The answer is in Postfix, not in Mailman. Search the FAQ http://www.python.org/cgi-bin/faqw-mm.py for performance. There may also be some clues in the archives of this 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
