Mailman 3 February 2004 - Mailman-Developers

mailman 2.1.4 problem
by Ako Ito 08 Feb '04

08 Feb '04

hello gurus, encountered this problem below in one of my mailing list.. any ideas on how to resolve this? thanks Bug in Mailman version 2.1.4 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/adb/data/pkg/mailman/2.1.3/scripts/driver", line 87, in run_main main() File "/adb/data/pkg/mailman/2.1.3/Mailman/Cgi/admin.py", line 198, in main show_results(mlist, doc, category, subcat, cgidata) File "/adb/data/pkg/mailman/2.1.3/Mailman/Cgi/admin.py", line 498, in show_results form.AddItem(membership_options(mlist, subcat, cgidata, doc, form)) File "/adb/data/pkg/mailman/2.1.3/Mailman/Cgi/admin.py", line 870, in membership_options all = [_m.encode() for _m in mlist.getMembers()] UnicodeError: ASCII decoding error: ordinal not in range(128) -------------------------------------------------------------------------------- Python information: Variable Value sys.version 2.2.2 (#1, Feb 24 2003, 19:13:11) [GCC 3.2.2 20030222 (Red Hat Linux 3.2.2-4)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 -------------------------------------------------------------------------------- Environment variables: Variable Value HTTP_REFERER SCRIPT_FILENAME /pkg/mailman/2.1.3/cgi-bin/admin PYTHONPATH /pkg/mailman/2.1.3 SERVER_SOFTWARE Apache/2.0.48 (Unix) mod_ssl/2.0.48 OpenSSL/0.9.7b PHP/4.3.4 SERVER_ADMIN SCRIPT_NAME /mailman/admin SERVER_SIGNATURE Apache/2.0.48 (Unix) mod_ssl/2.0.48 OpenSSL/0.9.7b PHP/4.3.4 Server on example.com 80 REQUEST_METHOD GET HTTP_HOST PATH_INFO /waterforallnews/members SERVER_PROTOCOL HTTP/1.1 QUERY_STRING REQUEST_URI /mailman/admin/waterforallnews/members HTTP_ACCEPT */* HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) HTTP_CONNECTION Keep-Alive HTTP_COOKIE watersports+admin=; homemakers+admin=; swrc+admin=; gis+admin=; waterforallnews+admin=28020000006925141f40732800000064306434613337636262623662323134653837376366376665653134303239333637373562626263 SERVER_NAME REMOTE_ADDR REMOTE_PORT 4079 HTTP_ACCEPT_LANGUAGE en-us PATH_TRANSLATED / SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip, deflate SERVER_ADDR DOCUMENT_ROOT /

2 1

RELEASED: Mailman 2.0.14 patch-only release
by Barry Warsaw 08 Feb '04

08 Feb '04

I have just released Mailman 2.0.14 as a patch-only release. This fixes a DoS bug to be described in CAN-2003-0991. See here for details: https://sourceforge.net/project/shownotes.php?release_id=97760 Please note that since I am no longer actively maintaining Mailman 2.0, this release has had only limited testing. It is recommended that all sites running Mailman 2.0 upgrade to 2.1 where ever possible. For those sites that cannot upgrade, this patch may be useful. Also note that it is no longer possible to download tarballs of Mailman 2.0 from SourceForge. Enjoy, -Barry

1 0

High memory usage of MailMan 2.1's runners
by JP Hindin 06 Feb '04

06 Feb '04

Greetings all; I run a reasonably active mailing list service, with a fair number (read > 20) lists with subscriber numbers in the range of anywhere from 5,000 to 50,000. We are currenty migrating from an existing Majordomo service (That'd be another 20 lists to go to Mailman), and are pleased with how friendly Mailman seems to be with customers, not to mention configurable. Unfortunately Mailman seems to be a fairly serious resource hog. The CPU spikes I can handle, I realise that when you're churning out 50,000 mails you need a little processing power - but the memory usage seems a little excessive; When the mail starts a flowin', the memory starts a goin'. Currently I've had mailman running for 5 hours, and clearly have had a couple mailing lists go out - because Mailman is sucking up 405MB of memory. The worst culprits are BounceRunner with 56MB, IncomingRunner and VirginRunner with 105MB a piece and the OutgoingRunner with 112MB. I've seen mention of performance issues that most seem to be saying is just part of Mailman - but this seems a little silly. What suggestions do you folks have for relieving this... Is there much I can do? This seems highly suggestive of a memory leak somewhere, I can't imagine it should ever use this - and given I would call this a Bad Thing - what's on Mailmans plate in the future to alleviate this? Thanks for the insight; JP

1 0

Approve subscriptions by email?
by zimmy＠nc.rr.com 06 Feb '04

06 Feb '04

New potential mailman user here... one functional requirement we have that I have not been able to pin down... - can I approve/deny subscription requests via email ? Our situation is a large club that has a club roster already, which contains email addrs for everyone. Thus we can automate the process of approve/deny by passing an "approve XYZ" email by comparing XYZ against our list. We have this arrangement working with Yahoogroups already (tho things get a bit flaky at times...), and while I haven't worked with a majordomo list in 10+ years, I remember it working this way too. So far I cannot find anything in the documentation about this, and searches of the mail archives have turned up only a few indefinite things. (sorry if I'm asking recurring question #1 or if I missed something obvious, but I did attempt a thorough search). I did find: http://www.mail-archive.com/mailman-developers@python.org/msg00038.html http://mail.python.org/pipermail/mailman-users/2003-July/030023.html The 2nd one seemed promising, so I tried to subscribe a person to a test list of mine. Mailman kicked out an email to the admin addr, and I was able to construct the group-add URL and thus "remotely" subscribe the requesting member.. http://mail.xyz.org/mailman/admin/test_xyz.org/members?subscribees=me@home.… BUT there is (at least) one major problem with this method... it does not seem to clear out the "pending" queue... so I'm getting reminder emails to the web interface and approve this poor chap ;-) Also doesn't really cover the situation of wanting to "deny" someone's request. If it matters, my concerns about security are much less than my concerns about functionality. Also, in this case, mailman is supplied by my host and I do not have access to modify the code (no root access). (at best could set up a forwarder to procmail to something, but that starts to seem ugly). Nor are the files of subscribers stored anywhere within my space to edit them directly (at least not that I can find). Thanks, Mike -- "The difference between perseverance and obstinacy is that one comes from a strong will, and the other comes from a strong won't" - Henry Ward Beecher zimmy(a)nc.rr.com

1 0

genaliases and templates problem
by Ako Ito 06 Feb '04

06 Feb '04

hello sirs, how can i add an entry whenever genaliases is executed it can add a field below with the unsub field.. in 2.1.3 i manually add it on the aliases file and upon issuing genaliases, but upon upgrading to 2.1.4 whenever i execute the genaliases script.. all manually added line on the aliases file gets discarded.. :-( example: "|mailman post example" example-admin: "|mailman admin example" example-bounces: "|mailman bounces example" example-confirm: "|mailman confirm example" example-join: "|mailman join example" example-leave: "|mailman leave example" example-owner: "|mailman owner example" example-request: "|mailman request example" example-subscribe: "|mailman subscribe example" example-unsubscribe: "|mailman unsubscribe example" example-unsub: "|mailman leave example" what do i need to edit to generate the extra line above.. and lastly.. they say that on mailman 2.1 templates can be configured per mailing list as opposed to the 2.0 version which whatever templates you edit it applies to all list.. how can i implement this... can i just copy the $mailman/templates/en on all mailing list and edit each templates per mailing list? thanks, allan

1 0

Empty module name
by Dan Langille 06 Feb '04

06 Feb '04

I'm running mailman-2.1.3 with postfix-2.0.16,1 on FreeBSD 4.9. Mailman was installed a few months ago. A few days ago, mail stopped being delivered. Viewing /var/log/maillog, I can see the mail is coming in, but never being delivered. In mailman/log/errors, I see this. Feb 02 16:19:01 2004 (33670) uncaught archiver exception at filepos: 0 Feb 02 16:19:01 2004 (33670) Uncaught runner exception: Empty module name Feb 02 16:19:01 2004 (33670) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose mlist.ArchiveMail(msg) File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 208, in ArchiveMail h.processUnixMailbox(f) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 544, in processUnixMailbox m = mbox.next() File "/usr/local/lib/python2.3/mailbox.py", line 35, in next return self.factory(_Subfile(self.fp, start, stop)) File "/usr/local/mailman/Mailman/Mailbox.py", line 89, in scrubber return mailbox.scrub(msg) File "/usr/local/mailman/Mailman/Mailbox.py", line 109, in scrub return self._scrubber(self._mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 311, in process t = t.encode(charset, 'replace') File "/usr/local/lib/python2.3/encodings/__init__.py", line 84, in search_function globals(), locals(), _import_tail) ValueError: Empty module name >From the archives, I see this is not a new problem, and found a patch at http://www.mail-archive.com/mailman- developers(a)python.org/msg06317.html. I applied the patch and recompiled: cd /usr/local/mailman/Mailman/Handlers python -c "import py_compile as p; p.compile('Scrubber.py')" I then ran unshunt and saw the errors continue. FWIW, I also retstarted the qrunners and tried again. Same symptoms. This problem has been raised before and seem to becoming more common. I found these recent references: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=871050&gr oup_id=103 http://www.mail-archive.com/mailman-users@python.org/msg21490.html Any suggestions please? -- Dan Langille : http://www.langille.org/ BSDCan - http://www.bsdcan.org/

2 5

cronpass.txt error
by Michael Heydekamp 05 Feb '04

05 Feb '04

Hi, cronpass.txt has not been sent out this month. Can anybody explain what's going wrong here? ----------8<---------- > Traceback (most recent call last): > File "/usr/lib/mailman/cron/mailpasswds", line 238, in ? > main() > File "/usr/lib/mailman/cron/mailpasswds", line 214, in main > text += (header + '\n' + NL.join(table)) > UnicodeDecodeError: 'ascii' codec can't decode byte 0xdf in position 43: > ordinal not in range(128) ----------8<---------- Michael

1 2

Small patch to templates/en/verify.txt
by Todd 04 Feb '04

04 Feb '04

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Here is a very simple patch to correct a small typo I noticed in templates/en/verify.txt. It's included below and attached as a unified diff against the current CVS, just in case that makes some developers life a little easier. -If you do not wish to be subscribed from this list, please simply +If you do not wish to be subscribed to this list, please simply Thanks as always for the great software! - -- Todd OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp ====================================================================== A snooze button is a poor substitute for no alarm clock at all. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQFAHu5Iuv+09NZUB1oRAnAmAJ9j+QlcB5Vp7tKI4ymV+jf8ONlIUwCePFTA STtdhdsrNSvAin1BvL9SMs8= =HlPT -----END PGP SIGNATURE-----

3 5

Admins not getting admin messages
by Skip Montanaro 03 Feb '04

03 Feb '04

I'm sorry to bomb this list with user issues. I've sent a couple notes to mailman-users about this and received no responses, not even "i don't know" or "what have you been smokin'?" mails. After upgrading from MM 2.0 to 2.1 several months ago, admin messages (pending subscriptions, mail from non-members) stopped going to the three of us who administer the cedu mailing list. We don't learn about this stuff until the daily summary of administrative requests comes out. Furthermore, mail sent to the cedu-admin address generates an uncaught bounce notification. We used to use that address to communicate amongst ourselves. The alias definitions for the list are cedu: "|/etc/smrsh/mailman post cedu" cedu-admin: "|/etc/smrsh/mailman admin cedu" cedu-bounces: "|/etc/smrsh/mailman bounces cedu" cedu-confirm: "|/etc/smrsh/mailman confirm cedu" cedu-join: "|/etc/smrsh/mailman join cedu" cedu-leave: "|/etc/smrsh/mailman leave cedu" cedu-owner: "|/etc/smrsh/mailman owner cedu" cedu-request: "|/etc/smrsh/mailman request cedu" cedu-subscribe: "|/etc/smrsh/mailman subscribe cedu" cedu-unsubscribe: "|/etc/smrsh/mailman unsubscribe cedu" /etc/smrsh/mailman is a symlink to /home/mailman21/mail/mailman. Mail sent to the cedu-owner address seems to go to all three of us. What I don't understand is what the cedu-admin address is for and where the admin messages are going. It seems clear that I missed something during the 2.0->2.1 upgrade, but I'm at a loss to see what. Any guidance would be much appreciated. Thanks, -- Skip Montanaro Got gigs? http://www.musi-cal.com/submit.html Got spam? http://spambayes.sf.net/ skip(a)pobox.com

2 4

AOL's requirements for spam complaints
by Somuchfun 03 Feb '04

03 Feb '04

Ok, I just got off the phone with AOL's postmaster dept. and found out the whole scoop why they have to strip out the To: address from complaints. There was a lawsuit of breach of privacy so AOL can no longer share the To: field in their feedback loop. So here is the solution: Mailman needs to create something like an x-client-id header that has the recipient email address in it because this header will stay intact when a complaint comes back. This header needs to be created whether mailman runs in personalization mode or not. So the questions is not can mailman do it or not?

10 54