[Mailman-Users] Please, help me
Hello. Excuse me for my English Please, Could you help me? Our mailing list is crashed. http:\\list.webaltair.com --- perico --- password: perico We make a list, we recived the welcome mail, but when we send a mail to the list, we recived this mail inmediatly: This is the Postfix program at host llwb403.servidoresdns.net. I'm sorry to have to inform you that the message returned below could not be delivered to one or more destinations. For further assistance, please send mail to postmaster If you do so, please include this problem report. You can delete your own text from the message returned below. The Postfix program [EMAIL PROTECTED]: Command died with status 2: /var/mailman/mail/mailman post webaltair.com.perico. Command output: Failure to exec script. WANTED gid 99, GOT gid 200. (Reconfigure to take 200?) Reporting-MTA: dns; llwb403.servidoresdns.net Arrival-Date: Thu, 20 Oct 2005 16:59:28 +0200 (CEST) Final-Recipient: rfc822; [EMAIL PROTECTED] Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; Command died with status 2: /var/mailman/mail/mailman post webaltair.com.perico. Command output: Failure to exec script. WANTED gid 99, GOT gid 200. (Reconfigure to take 200?) Thank you very much Javier Peix -- 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] attachments are not scrubbed
Hello, yesterday I upgraded mailman to 2.1.5 version and noticed that attachment no more were scrubbed (in non-digest emails) although in previous version they were scrubbed. Is the a bug or where should I 'switch on' that attachments were srubbed automaticaly (i.e. attachment would be in some place and message contain link to it)? By, Saulius -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Strange errors
Mark Sapiro wrote: Dan Szkola wrote: The python 2.4.1 was compiled from source and is the only python version on the box. In a later post, you say it wasn't, but you removed the Sun Gnome Python 2.3. I hope that fixes it, but I doubt it will. It did not. It was doubtful mailman could find that python, due to it being in /usr/sfw, but one never knows for sure. Here's something else to try if it fails again. As the mailman user in the /usr/local/mailman directory, give the command python2.4 -S /usr/local/mailman/scripts/admin listname file Except for the fact that this doesn't edit the environment passed to the script, it is the same as invoking the script from the wrapper. If it works, it will produce an 'unrecognized bounce' which will be forwarded to the list owner if the option to do so is selected. If it doesn't work, it will produce a similar output to the above, but the key is that if it doesn't work, we'll know that the problem, even though fixed by restarting sendmail and not by restarting Mailman, occurs even though sendmail doesn't directly invoke the script via the wrapper. If it does work, we'll know that it involves the script being invoked through the wrapper. It did work, 5 straight times I got the normal Uncaught bounce notification message. You could then try /usr/local/mailman/mail/mailman admin listname file to see if it occurs when you rather than sendmail invoke the wrapper, but this has to be done from the group that sendmail uses, i.e., the group that the wrapper expects to be invoked by. Otherwise, the wrapper will complain because this is exactly the security violation the wrapper is supposed to catch. Same here, works every time, sending the Uncaught bounce notification message. Only seems to happen when run by the sendmail process. -- Dan Szkola Sr Unix Systems Programmer Northern Illinois University -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Strange errors
OK, I found something extremely odd. For some reason, the Utils.pyc in /usr/local/mailman/Mailman/Logging direcotry is being removed and then the compile of it seems to fail and I'm left with a 0 byte file. It is owned by the daemon user and later it gets compiled and is owned by the mailman user. # ls -l total 60 -rw-r--r-- 1 root mailman 3380 May 31 08:39 Logger.py -rw-r--r-- 1 www mailman 3175 May 31 08:43 Logger.pyc -rw-r--r-- 1 root mailman 2559 May 31 08:39 MultiLogger.py -rw-r--r-- 1 root mailman 2133 May 31 08:43 MultiLogger.pyc -rw-r--r-- 1 root mailman 3204 May 31 08:39 StampedLogger.py -rw-r--r-- 1 www mailman 2933 May 31 08:43 StampedLogger.pyc -rw-r--r-- 1 root mailman 2221 May 31 08:39 Syslog.py -rw-r--r-- 1 www mailman 1709 May 31 08:43 Syslog.pyc -rw-r--r-- 1 root mailman 1912 May 31 08:39 Utils.py -rw-r--r-- 1 daemon mailman0 Oct 21 09:27 Utils.pyc -rw-r--r-- 1 root mailman 785 May 31 08:39 __init__.py -rw-r--r-- 1 www mailman 126 May 31 08:43 __init__.pyc # ls -l total 64 -rw-r--r-- 1 root mailman 3380 May 31 08:39 Logger.py -rw-r--r-- 1 www mailman 3175 May 31 08:43 Logger.pyc -rw-r--r-- 1 root mailman 2559 May 31 08:39 MultiLogger.py -rw-r--r-- 1 root mailman 2133 May 31 08:43 MultiLogger.pyc -rw-r--r-- 1 root mailman 3204 May 31 08:39 StampedLogger.py -rw-r--r-- 1 www mailman 2933 May 31 08:43 StampedLogger.pyc -rw-r--r-- 1 root mailman 2221 May 31 08:39 Syslog.py -rw-r--r-- 1 www mailman 1709 May 31 08:43 Syslog.pyc -rw-r--r-- 1 root mailman 1912 May 31 08:39 Utils.py -rw-r--r-- 1 mailman mailman 1308 Oct 21 09:30 Utils.pyc -rw-r--r-- 1 root mailman 785 May 31 08:39 __init__.py -rw-r--r-- 1 www mailman 126 May 31 08:43 __init__.pyc -- Dan Szkola Sr Unix Systems Programmer NOrthern Illinois University -- 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] How to make one-way list?
I need to create one-way list. Like an annoucement list that allows only one email address to post to the 300-member list. Is this possible? -- 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 install: dealing with 10.0.0.n(local server address) [BYPASSED]
Hi,
I tried a few server configurations, using VIRTUAL_HOSTS_OVERVIEW = Off
AND without that line, but indeed Mailman treats lists created under
10.0.0.3 as seperate from http://mysubdomain.ourdomain.com. It can't
figure out from just the requested url, from which network this web
request is coming (my local network or the rest of the world).
So that doesn't help me when I want to configure -using the
webinterface- the lists which I host from my machine.
Fortunately for me my isp has a server which I can login to using ssh.
And now I using that route and links (the command line text browser)
instead of my normal browser on my local machine.
localhost - ssh to remote.server.net - links
http://mysubdomain.ourdomain.com/mailman/admin
And that solution works just fine for me. Thought of sharing that with
you lot.
best,
d
On 7-okt-05, at 05:54, Mark Sapiro wrote:
Dirk van Oosterbosch, IR labs wrote:
However when I want to access my server from my local network, I have
to go to http://10.0.0.n/ because my router would not understand
http://mysubdomain.ourdomain.com.
...
http://10.0.0.n/mailman/admin returns a
page and also http://10.0.0.n/mailman/create shows the returns the
right page, but all the links on those pages refer to
mysubdomain.ourdomain.com instead of 10.0.0.n.
...
Is there anyway I can keep these default email and url hosts and still
have those web interface pages respond correctly browsing them through
10.0.0.n?
You will need to modify source to make everything work.
I am guessing you have VIRTUAL_HOSTS_OVERVIEW = Off or No in mm_cfg.py
although you don't mention it above. This enables several things which
will cease working if you remove this or set it On.
Among the things which won't work are:
http://10.0.0.n/mailman/admin and http://10.0.0.n/mailman/listinfo will
not show any lists unless you add_virtual_host('10.0.0.n',
'10.0.0.n') and then it will show those lists created in the 10.0.0.n
domain, but these in turn will not show on the
http://mysubdomain.ourdomain.com/mailman/admin and
http://mysubdomain.ourdomain.com/mailman/listinfo pages.
You also won't be able to create lists from the
http://10.0.0.n/mailman/create page unless you
add_virtual_host('10.0.0.n', '10.0.0.n') and then those list will be
created in the 10.0.0.n domain.
However, I think if you do remove VIRTUAL_HOSTS_OVERVIEW from
mm_cfg.py, then the links in the admin interface will reflect the host
domain in the invoking URL.
Of course, if you don't have VIRTUAL_HOSTS_OVERVIEW = Off or No in
mm_cfg.py (and haven't changed it in Defaults.py which you should
never do), then I don't know what I'm talking about and you can ignore
this post.
-
Dirk van Oosterbosch
de Wittenstraat 225
1052 AT Amsterdam
the Netherlands
W http://labs.ixopusada.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] some lists cannot receive emails after acrash(Incorrect padding)
jay alvarez wrote: We just had a hardware failure with our mailserver running mailman+qmail, the smtpd as well as mailman daemons died because of hard disc space lost due to some logs overgrowned that were not rotated. The problem has already been fixed and the qmail daemons as well as mailman have been restarted, however, some mailing list cannot receive emails. Looking at smtpd logs, it seems like the client can successfully deliver emails to the mailserver but the mailman couldn't distribute it properly to list members. What's more suprising is that other lists can receive emails, but few can't. Below is the series of mailman error logs continuesly appearing from time to time during the normal operation, but I don't think it has something to do with the root of the problem. Hope you can help me.. Thanks. Oct 21 10:23:09 2005 (19519) SHUNTING: 1118201593.7484629+ca85708cae103ebea5e28102d9aecb0ae1991f3f Oct 21 10:23:49 2005 (19519) Uncaught runner exception: Incorrect padding Oct 21 10:23:49 2005 (19519) Traceback (most recent call last): File /usr/local/mailman/Mailman/Queue/Runner.py, line 105, in _oneloop self._onefile(msg, msgdata) File /usr/local/mailman/Mailman/Queue/Runner.py, line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/local/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /usr/local/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 82, in process send_digests(mlist, mboxfp) File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 123, in send_digests send_i18n_digests(mlist, mboxfp) File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 303, in send_i18n_digests print plainmsg, msg.get_payload(decode=1) File /usr/local/mailman/pythonlib/email/Message.py, line 189, in get_payload return Utils._bdecode(payload) File /usr/local/mailman/pythonlib/email/Utils.py, line 75, in _bdecode value = base64.decodestring(s) File /usr/lib/python2.1/base64.py, line 44, in decodestring return binascii.a2b_base64(s) Error: Incorrect padding Oct 21 10:23:49 2005 (19519) SHUNTING: 1118204475.9834571+22369a18d9473e03619ce8224a5e274504872f9a I think the offending list/lists has/have a corrupt digest.mbox file that was being written when the system crashed. Either that or a bad message has gotten into the file. Look at lists/list_name/digest.mbox. The last message is probably truncated. If you move it aside and then run bin/unshunt to reprocess the messages in the shunt queue, things will probably get going normally again, but the initial messages in the old digest.mbox will be missing from the next digest. If this is important, you could try to edit digest.mbox and remove the offending message instead of moving the file aside. If this is not the problem with the lists not processing, it may be that they are locked. Look in Mailman's locks/ directory and manually remove the old lock files. -- 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] Please, help me
Javier --- Altairwrote: Failure to exec script. WANTED gid 99, GOT gid 200. (Reconfigure to take 200?) http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.004.htp, http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.001.htp and http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.016.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] How to make one-way list?
James wrote I need to create one-way list. Like an annoucement list that allows only one email address to post to the 300-member list. Is this possible? Yes. Search the FAQ wizard Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py either one-way or announcement will return the detailed answer. -- 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] attachments are not scrubbed
Saulius wrote: yesterday I upgraded mailman to 2.1.5 version and noticed that attachment no more were scrubbed (in non-digest emails) although in previous version they were scrubbed. Is the a bug or where should I 'switch on' that attachments were srubbed automaticaly (i.e. attachment would be in some place and message contain link to it)? In Mailman 2.1.6, there is an option to scrub attachments from individual messages (non-digest emails). Prior to that, attachments were only scrubbed from archives and plain text format digests. Are you sure you didn't downgrade to 2.1.5? -- 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] Archiving
David wrote: Im on a hosted server. I am trying to decide if I want to archive my lists or not. I don't seem to see any place that allows trimming the archives if they start taking up too much space or just get too many in general if I want to do it on weekly basis. Is that option available some place? There is no option within Mailman to prune old messages from the archives. -- 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] Archiving
On Fri, 21 Oct 2005, Mark Sapiro wrote: lists or not. I don't seem to see any place that allows trimming the archives if they start taking up too much space or just get too many in general if I want to do it on weekly basis. Is that option available some place? There is no option within Mailman to prune old messages from the archives. If the archive file is just an mbox file, you should be able to use any mail program that uses mbox format to remove messages -- mail, elm, pine, etc. Then regenerate the web archive. -Chris == Chris Candreva -- [EMAIL PROTECTED] -- (914) 967-7816 WestNet Internet Services of Westchester http://www.westnet.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
[Mailman-Users] old files in the shunt queue directory
Courtesy of this list I latched onto the Mailman daily status report script. Consequently I'm now aware of something I wasn't before... I have 85 files in the shunt queue directory, most dated from 2 thru 4 May and a pair dated 25 Aug. They are all data files, so I can't simply 'more' thru them for content. The few I checked with 'strings' (and the old dates) lead me to believe they can all be trashed. ~ QUESTION: Is it safe to simply delete files from ../mailman/qfiles/shunt? ~ I have tried to find out for myself about what shunt is and what I can do with the directory, but there isn't much info available. All I could find was to run ../bin/unshunt to handle the files. But I don't want them handled, I want them gone. Help! -- Steve Lindemann Network Administrator Marmot Library Network, Inc. url: http://www.marmot.org email: mailto:[EMAIL PROTECTED] voice: +1.970.242.3331 ext 16 fax: +1.970.245.7854 /\ \ / ASCII Ribbon Campaign X against HTML email, vCards / \ micro$oft attachments -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] to install MAILMAN at a provider
Hallo, I have a account at a provider (1 1) (space on their Server) with Python implemented and actived. Is it possible to install Mailman ? thanks ! antoine -- 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] Archiving
Ok Thanks I was just finding this out in the FAQ (Who ever checks these thingsSorry) and the List Home Page. How ever I see it is on the wish list for 2.2 or 3.0 or some future release so I think I am just gonna go ahead archive as the list is new on a new site and by the time the archives get unruly that option should be available and I should be fine. Thanks again!! Thanks David Mark Sapiro wrote: David wrote: Im on a hosted server. I am trying to decide if I want to archive my lists or not. I don't seem to see any place that allows trimming the archives if they start taking up too much space or just get too many in general if I want to do it on weekly basis. Is that option available some place? There is no option within Mailman to prune old messages from the archives. -- No Smoking Forum - Http://www.nicodemon.info/community Lansing Forum - Http://www.greater-lansing.com/community He's Not My President!!! Blue States Rock~ -- 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] Who can view subscription list?
David wrote: Seems my other post explains it. Email has nothing to do with it but the admin password does. You can put anything you want or nothing into the email box but putting the admin password lets you see. I was using test email with same password so it let me in. So in other words the box for the email address isnt even needed. I have created a FAQ at http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.060.htp to help clarify this issue. Suggestions/improvements welcome. -- 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] to install MAILMAN at a provider
On Fri, 2005-10-21 at 19:33 +0200, antoine wrote: Hallo, I have a account at a provider (1 1) (space on their Server) with Python implemented and actived. Is it possible to install Mailman ? No. Mailman requires integration with other system services (MTA, httpd, cron) that you almost certainly would not have access to. -- John Dennis [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] old files in the shunt queue directory
Steve Lindemann wrote: I have 85 files in the shunt queue directory, most dated from 2 thru 4 May and a pair dated 25 Aug. They are all data files, so I can't simply 'more' thru them for content. The few I checked with 'strings' (and the old dates) lead me to believe they can all be trashed. bin/show_qfiles qfiles/shunt/* | more ~ QUESTION: Is it safe to simply delete files from ../mailman/qfiles/shunt? ~ Yes I have tried to find out for myself about what shunt is and what I can do with the directory, but there isn't much info available. All I could find was to run ../bin/unshunt to handle the files. But I don't want them handled, I want them gone. If you still have Mailman's error log covering those dates, you should find a detailed entry for each of the 85 errors that caused those 85 messages to be shunted. -- 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] to install MAILMAN at a provider
Hello antoine, On Friday, October 21, 2005, antoine I have a account at a provider (1 1) (space on their Server) with Python implemented and actived. Is it possible to install Mailman ? No, because 11 has their mail system running on different servers so you cannot get your mails to the mailman installation. To run mailman you will need a root server. Bye Markus -- E-Mail: [EMAIL PROTECTED] Homepage: http://www.kachelonline.de -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] add_members and email confirmation
Hello,
I have a signup sheet that subscribes people to a Mailman list by using
PHP to call add_members (the PHP is below, FYI). My problem is that
add_members seems to ignore the email confirmation settings from the
admin interface. Even though my list is configured to send a
confirmation message, subscribers only get the Thanks for signing up!
email.
Does anyone know of a way to use add_members in a confirmed-opt-in
list? Thanks very much!
-Ren
=-=-=-=-=-=-=-
h2Subscription Results/h2
?php
// The path to your add_members program here:
$ADD_MEMBERS = '/your/path/to/add_members';
// The name of your mailing list:
$LIST = 'FakeList';
// The email address from the form, run through a process
// that removes nasty scripting attacks
$adrs = escapeshellcmd($_GET['email']);
// Runs the pipeline and stores the output in an array
exec(echo $adrs | $ADD_MEMBERS -r - $LIST, $output, $return_var);
// Implodes the array into a string
$msg = implode('', $output);
// Search for 'Subscribed' in $msg. Then we know if it worked or not.
if (strpos($msg, 'Subscribed') === FALSE) {
print Crap! Something went wrong and you were not subscribed.;
} else {
print It worked!;
}
?
--
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] add_members and email confirmation
On Fri, 2005-10-21 at 14:23 -0400, Ren Bucholz wrote: Hello, I have a signup sheet that subscribes people to a Mailman list by using PHP to call add_members (the PHP is below, FYI). My problem is that add_members seems to ignore the email confirmation settings from the admin interface. Even though my list is configured to send a confirmation message, subscribers only get the Thanks for signing up! email. Does anyone know of a way to use add_members in a confirmed-opt-in list? Thanks very much! Not is its current manifestation. The reason is that manual adding of members assumes this is an approved action. You have two choices: 1) redirect them to the signup page for the list (this has the advantage of allowing the user to set some preferences and see some basic info). 2) Copy the add_members script to a new name and edit it so that it calls AddMember instead of AddApprovedMember. See Mailman/Cgi/subscribe.py for an example of how to do this and the various exceptions you'll have to catch and handle. -- John Dennis [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Strange errors
Dan Szkola wrote: OK, I found something extremely odd. For some reason, the Utils.pyc in /usr/local/mailman/Mailman/Logging direcotry is being removed and then the compile of it seems to fail and I'm left with a 0 byte file. It is owned by the daemon user and later it gets compiled and is owned by the mailman user. # ls -l total 60 -rw-r--r-- 1 root mailman 3380 May 31 08:39 Logger.py -rw-r--r-- 1 www mailman 3175 May 31 08:43 Logger.pyc -rw-r--r-- 1 root mailman 2559 May 31 08:39 MultiLogger.py -rw-r--r-- 1 root mailman 2133 May 31 08:43 MultiLogger.pyc -rw-r--r-- 1 root mailman 3204 May 31 08:39 StampedLogger.py -rw-r--r-- 1 www mailman 2933 May 31 08:43 StampedLogger.pyc -rw-r--r-- 1 root mailman 2221 May 31 08:39 Syslog.py -rw-r--r-- 1 www mailman 1709 May 31 08:43 Syslog.pyc -rw-r--r-- 1 root mailman 1912 May 31 08:39 Utils.py -rw-r--r-- 1 daemon mailman0 Oct 21 09:27 Utils.pyc -rw-r--r-- 1 root mailman 785 May 31 08:39 __init__.py -rw-r--r-- 1 www mailman 126 May 31 08:43 __init__.pyc # ls -l total 64 -rw-r--r-- 1 root mailman 3380 May 31 08:39 Logger.py -rw-r--r-- 1 www mailman 3175 May 31 08:43 Logger.pyc -rw-r--r-- 1 root mailman 2559 May 31 08:39 MultiLogger.py -rw-r--r-- 1 root mailman 2133 May 31 08:43 MultiLogger.pyc -rw-r--r-- 1 root mailman 3204 May 31 08:39 StampedLogger.py -rw-r--r-- 1 www mailman 2933 May 31 08:43 StampedLogger.pyc -rw-r--r-- 1 root mailman 2221 May 31 08:39 Syslog.py -rw-r--r-- 1 www mailman 1709 May 31 08:43 Syslog.pyc -rw-r--r-- 1 root mailman 1912 May 31 08:39 Utils.py -rw-r--r-- 1 mailman mailman 1308 Oct 21 09:30 Utils.pyc -rw-r--r-- 1 root mailman 785 May 31 08:39 __init__.py -rw-r--r-- 1 www mailman 126 May 31 08:43 __init__.pyc Presumably daemon is the user that sendmail uses to invoke the wrapper. When you tried invoking the wrapper manually and did not get the error, were you running it as the daemon user? If not, you might try that. The recompiling is strange in itself. Normally, if the .pyc is more recent than the .py, accessible and not corrupt, it is just used, so once you have a good one, why is python trying to recompile it? And if Python is recompiling this module when invoked in the 'odd' way, is it also doing others, and why does this cause a problem (if it is a cause)? Do any other Mailman .pyc files have way more recent dates than the corresponding .py, or are any others owned by 'daemon'? Maybe next time try something like find /usr/local/mailman -type f -a \( -mtime 0 -o -user daemon \) Also, try running the /usr/local/mailman/mail/mailman admin listname file as user daemon and the appropriate group if you haven't already. I really don't understand what's happening since sendmail should always be invoking the wrapper with the same user:group and that works at first. In order to even more closely mimic sendmail, you could try cat file | /usr/local/mailman/mail/mailman admin listname instead of the above. Beyond that, the only difference I can see is the environment, but we say previously, after the wrapper got done with the environment, all that was there was PYTHONPATH /usr/local/mailman AGENT sendmail and PYTHONPATH is always put there by the wrapper and presumably AGENT is always put there by sendmail. So, why does it only seem to fail when sendmail invokes it and only after some successful invocations, and why does restarting sendmail fix it while restarting Mailman (which will recompile /usr/local/mailman/Mailman/Logging/Utils.py) doesn't fix it? Maybe we need to take this to comp.lang.python. -- 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] attachments are not scrubbed
Hello, In Mailman 2.1.6, there is an option to scrub attachments from individual messages (non-digest emails). Prior to that, attachments were only scrubbed from archives and plain text format digests. Are you sure you didn't downgrade to 2.1.5? No. Previous version was 2.1.4. And new version (2.1.5) I installed via deb (Debian package). In 2.1.4 attachments were scrubbed in simple non-digest format (there was one bug with encoding). But after I upgraded it to 2.1.5, attachments were not scrubbed any more (but scrubber still works in archives). Hm, is there any posibility to turn it on (maybe in code) - until there will be 2.1.6 in Debian packages. Bye, Saulius This message was sent using IMP, the Internet Messaging Program. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Strange errors
Mark Sapiro wrote: Dan Szkola wrote: OK, I found something extremely odd. For some reason, the Utils.pyc in /usr/local/mailman/Mailman/Logging direcotry is being removed and then the compile of it seems to fail and I'm left with a 0 byte file. It is owned by the daemon user and later it gets compiled and is owned by the mailman user. Presumably daemon is the user that sendmail uses to invoke the wrapper. When you tried invoking the wrapper manually and did not get the error, were you running it as the daemon user? If not, you might try that. Did that, same thing: $ id uid=1(daemon) gid=1(other) $ /usr/local/mailman/mail/mailman admin esstest /var/tmp/testmessage HZ TERM vt100 SHELL /usr/bin/sh TZ US/Central PYTHONPATH /usr/local/mailman LOGNAME daemon MAIL /var/mail/daemon HOME / before = /usr/local/mailman/scripts before = /usr/local/mailman before = /usr/local/lib/python24.zip before = /usr/local/lib/python2.4/ before = /usr/local/lib/python2.4/plat-sunos5 before = /usr/local/lib/python2.4/lib-tk before = /usr/local/lib/python2.4/lib-dynload after = /usr/local/mailman/pythonlib after = /usr/local/mailman after = /usr/local/mailman/scripts after = /usr/local/mailman after = /usr/local/lib/python24.zip after = /usr/local/lib/python2.4/ after = /usr/local/lib/python2.4/plat-sunos5 after = /usr/local/lib/python2.4/lib-tk after = /usr/local/lib/python2.4/lib-dynload after = /usr/local/lib/python2.4/site-packages The recompiling is strange in itself. Normally, if the .pyc is more recent than the .py, accessible and not corrupt, it is just used, so once you have a good one, why is python trying to recompile it? And if Python is recompiling this module when invoked in the 'odd' way, is it also doing others, and why does this cause a problem (if it is a cause)? Very odd, I agree. A truss of the persistent queue runner that handled one of the test mails shows this (12762 is the pid that mailman gets when sendmail exec's it): 12762: open64(/usr/local/mailman/Mailman/Logging/Utils.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/Utilsmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/Utils.py, O_RDONLY) = 66 12762: fstat64(66, 0xFFBF8928) = 0 12762: open64(/usr/local/mailman/Mailman/Logging/Utils.pyc, O_RDONLY) = 256 12762: close(256) = 0 12762: fstat64(66, 0xFFBF83C8) = 0 12762: fstat64(66, 0xFFBF8270) = 0 12762: ioctl(66, TCGETA, 0xFFBF8354) Err#25 ENOTTY 12762: read(66, # C o p y r i g h t .., 8192)= 1912 12762: read(66, 0x001F902C, 8192) = 0 12762: unlink(/usr/local/mailman/Mailman/Logging/Utils.pyc) = 0 12762: open64(/usr/local/mailman/Mailman/Logging/Utils.pyc, O_WRONLY|O_CREAT|O_TRUNC|O_EXCL, 0666) = 256 12762: fcntl(256, F_GETFD, 0xFEFE7F18) = 0 12762: stat64(/usr/local/mailman/Mailman/Logging/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/traceback.py, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/traceback.pyc, O_RDONLY) Err#2 ENOENT 12762: stat64(/usr/local/mailman/pythonlib/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/mailman/pythonlib/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/pythonlib/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/pythonlib/traceback.py, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/pythonlib/traceback.pyc, O_RDONLY) Err#2 ENOENT 12762: stat64(/usr/local/mailman/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/mailman/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/traceback.py, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/traceback.pyc, O_RDONLY) Err#2 ENOENT 12762: stat64(/usr/local/mailman/scripts/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/mailman/scripts/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/scripts/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/scripts/traceback.py, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/scripts/traceback.pyc, O_RDONLY) Err#2 ENOENT 12762: stat64(/usr/local/mailman/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/mailman/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/traceback.py, O_RDONLY) Err#2 ENOENT 12762:
[Mailman-Users] Sender Name
Why does the sender name on my list include the word bounces? V2.1.6. Thanks. -- Pete Holsberg Columbus, NJ -- Age is not a particularly interesting subject. Anyone can get old. All you have to do is live long enough. Groucho Marx -- 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] attachments are not scrubbed
[EMAIL PROTECTED] wrote:
No. Previous version was 2.1.4. And new version (2.1.5) I installed via deb
(Debian package). In 2.1.4 attachments were scrubbed in simple non-digest
format (there was one bug with encoding).
Just to be sure I understand, you are saying that attachments were
scrubbed (stored elsewhere and replaced with a link) from individual
messages sent to non-digest subscribers. If this was the case in your
2.1.4, you must have had a local patch to do it which was 'removed'
when you upgraded to 2.1.5.
But after I upgraded it to 2.1.5,
attachments were not scrubbed any more (but scrubber still works in archives).
Hm, is there any posibility to turn it on (maybe in code) - until there
will be
2.1.6 in Debian packages.
If you want to scrub attachments from everything in 2.1.5, it may be as
simple as adding 'Scrubber' to GLOBAL_PIPELINE.
You could try copying the definition of GLOBAL_PIPELINE from
Defaults.py into mm_cfg.py and then add 'Scrubber', following
'MimeDel',. or you could add the following to mm_cfg.py which will
add 'Scrubber' if it isn't already there:
if not GLOBAL_PIPELINE.count('Scrubber'):
GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('MimeDel') + 1,
'Scrubber')
--
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] Sender Name
Pete Holsberg wrote: Why does the sender name on my list include the word bounces? V2.1.6. So that if the mail bounces, the bounce will be returned to [EMAIL PROTECTED] instead of to the list or the OP, and automated bounce processing will work. Actually, it should suffice that this address is the envelope sender, but some non-compliant MTAs send the bounce to Sender: or Errors-To: so SMTPDirect.py sets these to the envelope sender. -- 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] Strange errors
Dan Szkola wrote: Very odd, I agree. A truss of the persistent queue runner that handled one of the test mails shows this (12762 is the pid that mailman gets when sendmail exec's it): 12762: open64(/usr/local/mailman/Mailman/Logging/Utils.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/Utilsmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/Utils.py, O_RDONLY) = 66 12762: fstat64(66, 0xFFBF8928) = 0 12762: open64(/usr/local/mailman/Mailman/Logging/Utils.pyc, O_RDONLY) = 256 12762: close(256) = 0 12762: fstat64(66, 0xFFBF83C8) = 0 12762: fstat64(66, 0xFFBF8270) = 0 12762: ioctl(66, TCGETA, 0xFFBF8354) Err#25 ENOTTY 12762: read(66, # C o p y r i g h t .., 8192)= 1912 12762: read(66, 0x001F902C, 8192) = 0 12762: unlink(/usr/local/mailman/Mailman/Logging/Utils.pyc) = 0 12762: open64(/usr/local/mailman/Mailman/Logging/Utils.pyc, O_WRONLY|O_CREAT|O_TRUNC|O_EXCL, 0666) = 256 12762: fcntl(256, F_GETFD, 0xFEFE7F18) = 0 12762: stat64(/usr/local/mailman/Mailman/Logging/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/traceback.py, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/Mailman/Logging/traceback.pyc, O_RDONLY) Err#2 ENOENT 12762: stat64(/usr/local/mailman/pythonlib/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/mailman/pythonlib/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/pythonlib/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/pythonlib/traceback.py, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/pythonlib/traceback.pyc, O_RDONLY) Err#2 ENOENT 12762: stat64(/usr/local/mailman/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/mailman/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/traceback.py, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/traceback.pyc, O_RDONLY) Err#2 ENOENT 12762: stat64(/usr/local/mailman/scripts/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/mailman/scripts/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/scripts/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/scripts/traceback.py, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/scripts/traceback.pyc, O_RDONLY) Err#2 ENOENT 12762: stat64(/usr/local/mailman/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/mailman/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/traceback.py, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/mailman/traceback.pyc, O_RDONLY) Err#2 ENOENT 12762: stat64(/usr/local/lib/python24.zip/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/lib/python24.zip/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/lib/python24.zip/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/lib/python24.zip/traceback.py, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/lib/python24.zip/traceback.pyc, O_RDONLY) Err#2 ENOENT 12762: stat64(/usr/local/lib/python2.4/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/lib/python2.4/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/lib/python2.4/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/lib/python2.4/traceback.py, O_RDONLY) = 257 12762: close(257) = 0 12762: open64(/usr/local/lib/python2.4/traceback.pyc, O_RDONLY) = 257 12762: close(257) = 0 12762: stat64(/usr/local/lib/python2.4/plat-sunos5/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/lib/python2.4/plat-sunos5/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/lib/python2.4/plat-sunos5/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/lib/python2.4/plat-sunos5/traceback.py, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/lib/python2.4/plat-sunos5/traceback.pyc, O_RDONLY) Err#2 ENOENT 12762: stat64(/usr/local/lib/python2.4/lib-tk/traceback, 0xFFBF7AD0) Err#2 ENOENT 12762: open64(/usr/local/lib/python2.4/lib-tk/traceback.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/lib/python2.4/lib-tk/tracebackmodule.so, O_RDONLY) Err#2 ENOENT 12762: open64(/usr/local/lib/python2.4/lib-tk/traceback.py, O_RDONLY) Err#2
Re: [Mailman-Users] Strange errors
Mark Sapiro wrote: Dan Szkola wrote: You can see it actually unlink the compiled version and then look for, find, and seemingly reject the traceback.py and traceback.pyc that it finds. I thought it may be a too many open files problem or a file descriptor limit problem because the FD returned on the open64(/usr/local/mailman/Mailman/Logging/Utils.pyc, O_RDONLY) was 256. But it doesn't return an error. I did see that the ulimit does say 256 open files is the max, but that doesn't seem to be the problem. Are you sure this isn't the problem? This is the first thing I've seen in this entire thread that begins to make sense, and it appears to me as if it can explain the whole thing. This was my initial thought as well. I know truss is not showing an error, but it is too much of a coincidence that the open of /usr/local/mailman/Mailman/Logging/Utils.pyc returns fd=256 (presumably the 257th file) and then Python wants to create a new one and then the opens of /usr/local/lib/python2.4/traceback.py and /usr/local/lib/python2.4/traceback.pyc return fd=257 and Python doesn't see them. It does not explain why it takes some amount of time to be exposed. Is sendmail leaking file descriptors? How is it that it always runs out of file descriptors at that exact point? I thought too many open files should throw an Err#24 EMFILE, but I'm seeing evidence from googling that shows what we are seeing. Is it possible that at the level of truss, there is no error and the limit of 256 files (fd = 255 ?) is enforced higher up where the resulting error doesn't get traced? Maybe so. I read where someone said that the close immediately following the open means the FD was rejected. Still raises questions, but at least I feel like we got somewhere in debugging this issue. -- Dan Szkola Sr Unix Systems Programmer Northern Illinois University -- 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] Sender Name
Mark Sapiro wrote: Pete Holsberg wrote: Why does the sender name on my list include the word bounces? V2.1.6. So that if the mail bounces, the bounce will be returned to [EMAIL PROTECTED] instead of to the list or the OP, and automated bounce processing will work. Actually, it should suffice that this address is the envelope sender, but some non-compliant MTAs send the bounce to Sender: or Errors-To: so SMTPDirect.py sets these to the envelope sender. The reason I ask is that AOL is identifying email from the list as SPAM, and I would like to tell the list members that they can put a certain address in their AOL addressbooks. Would that address be the [EMAIL PROTECTED] Thanks. -- Pete Holsberg Columbus, NJ -- Age is not a particularly interesting subject. Anyone can get old. All you have to do is live long enough. Groucho Marx -- 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] Sender Name
Pete Holsberg said the following on 10/21/2005 5:42 PM: So that if the mail bounces, the bounce will be returned to [EMAIL PROTECTED] instead of to the list or the OP, and automated bounce processing will work. Actually, it should suffice that this address is the envelope sender, but some non-compliant MTAs send the bounce to Sender: or Errors-To: so SMTPDirect.py sets these to the envelope sender. The reason I ask is that AOL is identifying email from the list as SPAM, and I would like to tell the list members that they can put a certain address in their AOL addressbooks. Would that address be the [EMAIL PROTECTED] This is a separate issue that really doesn't have anything to do with Mailman, per-se. You need to check out: http://postmaster.aol.com/ Follow their instructions for Is your mail to AOL being blocked? and Would you like to apply for the AOL Whitelist? Once I did that, I no longer had anyone complaining about mail from lists on my server being blocked. Best, --Glenn -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. ~Benjamin Franklin, Historical Review of Pennsylvania, 1759 -- 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
