Mailman 3 June 2003 - Mailman-Developers

Tracebacks from Mailman v2.1 in Debian/Testing
by J C Lawrence 28 Jun '03

28 Jun '03

Barry, Using the Debian 2.1.2-2 package I get the floowing tracebacks on attempted subscribes: File "/var/lib/mailman/scripts/driver", line 87, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 96, in main process_form(mlist, doc, cgidata, language) File "/usr/lib/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form mlist.AddMember(userdesc, remote) File "/var/lib/mailman/Mailman/MailList.py", line 831, in AddMember text=text, lang=lang) File "/var/lib/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' and this when attempting to forward mail from the admindb: File "/var/lib/mailman/scripts/driver", line 87, in run_main main() File "/var/lib/mailman/Mailman/Cgi/admindb.py", line 165, in main process_form(mlist, doc, cgidata) File "/var/lib/mailman/Mailman/Cgi/admindb.py", line 760, in process_form preserve, forward, forwardaddr) File "/var/lib/mailman/Mailman/ListAdmin.py", line 184, in HandleRequest forward, addr) File "/var/lib/mailman/Mailman/ListAdmin.py", line 355, in __handlepost lang=lang) File "/var/lib/mailman/Mailman/Message.py", line 206, in __init__ errors='replace') TypeError: __init__() got an unexpected keyword argument 'errors' -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

3 2

Handling of Return-Path headers
by J C Lawrence 28 Jun '03

28 Jun '03

Mailman should remove any Return-Path headers found in the messages it broadcasts. I've found that there are a number of MTAs out there that will _preferentially_ send bounces back to the address found in a Return-Path header (if there is one in the message) rather than the address listed in the envelope. Not good. Well behaved systems should not generate non-locally delivered messages with Return-Path headers. This is an area where Mailman should be generous in what it accepts and conservative in what it emits. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

How hard would it be...
by Marty Galyean 25 Jun '03

25 Jun '03

To put a button next to each message in the archives (labeled 'get'?) that when clicked causes MM to send that message to the logged in archive user as an email just as if it had been sent to them in non-digest mode? This would be a good way for people who have 'no-mail' or 'digest' set to reply occasionally to specific posts. And also to reply to a message the user has already deleted locally. I'm assuming private archives that would require logging in so the email address would be handy, but even so, a detour to the log in form would not be a problem if necessary. I'd like to take a shot at this, but would like some pointers and suggestions so as not to go about it the wrong way. Any suggestions? Comments? Thanks, Marty

1 0

Question about digests
by Greg Swallow 25 Jun '03

25 Jun '03

Hi, I'm running mailman 2.1.2 on Solaris 9, with Qmail 1.0.3 and Python 2.2.2. I'm testing switching mailing lists from our sendmail/majordomo system to our qmail/mailman system, and this issue is a showstopper for us. The issue is that, occasionally, mailman decides to start discarding posts to a list that we host. The vette log states that messages are discarded, but nothing else. At the same time, if I look at the digest.mbox file for this list, all posts that are being discarded are also appended to the digest.mbox file as they come in. The digest.mbox file never grew past its default maximum size of 30Kb: half an hour after digests were supposed to be sent out, its size was 29330 bytes. Only after the list started discarding posts did the size of the digest.mbox file grow past its maximum size, to 107Kb. If I cp digest.mbox digest.mbox.bak ; cat /dev/null > digest.mbox everything starts working again, as normal. Without good logs of what's going on, I have no idea how to pin this issue down. I've also searched all documentation I can find, including the mailing list archives for mailman-users and mailman-developers, and the only query I can find is my own from 6/1/2003. Does anyone have any ideas? BTW, please reply back to me directly. I'm not subscribed to mailman-developers. Thanks in advance. -- -- "I still think the odds are good that you can make a bet on what will be the odds" -- Tub Ring +--------------+--------------------+---------------+----------------+ | Greg Swallow | System Administrator | accessIndiana | 888.4IN.EGOV | +--------------+--------------------+---------------+----(446.3468)--+

1 0

Re: [Mailman-Developers] TMDA fronted Mailman v2.1 lists
by J C Lawrence 24 Jun '03

24 Jun '03

On 24 Jun 2003 08:34:24 -0400 Barry Warsaw <barry(a)python.org> wrote: > On Tue, 2003-06-24 at 00:43, J C Lawrence wrote: >> ObNote2: TMDA as of v0.75 (latest .deb)is not able to read Mailman >> v2.1 list configurations to extract the membership rosters (the >> pickle now contains bounce objects so the naive cPickle.load fails). >> This doesn't create a major problem, just means that you have to >> comment sections of your TMDA filters until that's fixed. (Jason: If >> you want example configs and other details, just give me the word and >> I'll attach them over). > That might be a simple matter of putting $prefix on your PYTHONPATH > when you start up TMDA. It needs to find the Mailman.Bouncer module > to get the _BounceInfo class. Quite! I'll give this a quick whack shortly. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

Links to mailman/python/gnu in footer, data about mailman's use?
by PieterB 21 Jun '03

21 Jun '03

Hi, I noticed that the icons at the bottom of a mailman page aren't links to resp. Mailman, Python and GNU. Wouldn't it be a good idea to turn them into hyperlinks, so that people can easily find information about the software that's running their mailinglist software. This can also be done in the pipermail footer. BTW Is there any data on the use of mailman and other mailinglist software? (e.g. number of downloads, number of lists, etc). You can see the pageranks of the various mailinglist servers at: http://directory.google.com/Top/Computers/Software/Internet/Servers/Mail/Li… I also did a quick lookup of the number of results on several queries: Mailman: about 5,030,000 hits in Google Listserv: about 2,780,000 hits in Google Majordomo: about 3,740,000 hits in Google Mailman+python: about 298,000 hits in Google Mailman+list: about 1,580,000 hits in Google Listserv+list: about 1,230,000 hits in Google Majordomo+list: about 1,140,000 hits in Google Lyris: about 135,000 hits in Google "Mojo Mail": about 9,150. hits in Google PieterB -- http://zwiki.org/PieterB

1 0

Indirect Spam Vulnerability
by Matt Helsley 20 Jun '03

20 Jun '03

I thought I'd describe a spam problem related to mailman I'm having and propose the solution. If anyone can tell me one way or another whether mailman avoids this "spam attack" I would appreciate it. I have two lists: foo(a)myhost.com moderated(a)myhost.com The spammer sends forged as foo(a)myhost.com to moderated(a)myhost.com. The mail gets held for approval and a message gets sent to foo(a)myhost.com informing it that the message has been held (often times the subject line is mentioned and contains lewd content which I'd rather not have sent out to subscribers on foo(a)myhost.com). This is why I used the word 'indirect spam'. Couldn't mailman redirect bounce/moderation notifications in the case where the FROM address is a mailman list and send it to the site/list administrator instead (or maybe drop it completely??)? I think this would avoid spamming the list subscribers while adding a minor load to the administrator's work. Does mailman 2.1.x already do this? If not, would this break something in mailman? Is it unreasonably restrictive on the site/list administrator(s)? I'm running 2.0.x (debian stable iirc) Thanks, -Matt Helsley

3 3

Re: Indirect Spam Vulnerability
by Donal Hunt 20 Jun '03

20 Jun '03

I've actually seen this result in a mail loop between two mailing lists on the same server (both moderated). As a result it can cause a DOS attack (slowing down the machine considerably). This was with Mailman 2.0, so 2.1 may resolve the problem... It's only happened once in 5 years (which i guess is fortunate!) but it something that should be looked at for current realeses if it's still possible to recreate... Regards Donal DCU Matt wrote: > I thought I'd describe a spam problem related to mailman I'm having > and propose the solution. If anyone can tell me one way or another > whether mailman avoids this "spam attack" I would appreciate it. > > I have two lists: foo(a)myhost.com > moderated(a)myhost.com > > The spammer sends forged as foo(a)myhost.com to moderated(a)myhost.com. > Themail gets held for approval and a message gets sent to > foo(a)myhost.com informing it that the message has been held (often > times the subject line is mentioned and contains lewd content which > I'd rather not have sent out to subscribers on foo(a)myhost.com). This > is why I used the word 'indirect spam'. > > Couldn't mailman redirect bounce/moderation notifications in the case > where the FROM address is a mailman list and send it to the site/list > administrator instead (or maybe drop it completely??)? I think this > would avoid spamming the list subscribers while adding a minor load to > the administrator's work. > > Does mailman 2.1.x already do this? If not, would this break something > in mailman? Is it unreasonably restrictive on the site/list > administrator(s)? > > I'm running 2.0.x (debian stable iirc) > > Thanks, > -Matt Helsley

1 0

alternate root for mailman - part 2
by marisa＠stat.umn.edu 14 Jun '03

14 Jun '03

It seems that I find the answer to the first part of my question. I should include the line: DEFAULT_URL_PATTERN = 'http://%s/mail_man/' in mm_cfg.py as well. Please tell me if I need some thing else. I still need to know how to convert existing lists from one version to other (2.0.8 to 2.1.2) as well as from one system to other. How do I change the host system in each list's configuration? Thanks again. Forwarded message: > From marisa Tue Jun 10 12:23:54 2003 > Subject: alternate root for mailman > To: mailman-developers(a)python.org > Date: Tue, 10 Jun 2003 12:23:54 -0500 (CDT) > X-Mailer: ELM [version 2.5 PL6] > Content-Length: 2948 > Lines: 98 > > > I am updating mailman to a new version but until I can test > all the changes I like to run two versions of the program. > I am working in a SuSE Linux 8.0 system. > > For the old versions I used the default settings and defined: > > ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ > Alias /pipermail/ /var/lib/mailman/archives/public/ > > For the new version (2.1.2) I am using user "mail_man" and: > > 1) a "configure" command such as: > > ./configure --prefix=/usr/local/mail_man --with-var-prefix=/var/mail_man > --with-username=mail_man --with-groupname=mail_man --with-mail-gid=65533 > --with-cgi-gid=65534 > > 2) a definition of where the Papermail directory will be in > ../Mailman/mm_cfg.py (I set this before "configure".) > > PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/piper_mail/%(listname)s' > > and > > 3) an addition to the Apache httpd configuration for the new > mail_man: > > ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/ > Alias /pipermail/ /var/lib/mailman/archives/public/ > > <Directory /var/lib/mailman/archives/> > Options +FollowSymLinks > </Directory> > > ScriptAlias /mail_man/ /usr/local/mail_man/cgi-bin/ > Alias /piper_mail/ /var/mail_man/archives/public/ > > <Directory /var/mail_man/archives/> > Options +FollowSymLinks > </Directory> > > > Things work "up to a certain point"... I can create new lists and the > lists are stored in my new paper_mail root OK. I also can locate the > lists management entry with the web page entry: > http://stat.umn.edu/mail_man/admin. > > The problem is that when I want to access any one of the new lists > that I created to be managed by the new version of the program I can not > access the information on those lists. > > If I look at the information on the configuration of the list > by using the unix "strings" command on the binary I see that that > list points to a web page in the old root: > > > strings /var/mail_man/lists/test212b/config.pck > . > . > web_page_urlqNU$http://muskrat.stat.umn.edu/mailman/qOU > > . > . > > I am so confuse that it is hard to post a question! But some how I > wander if > > 1) I am missing some information for "configure" > > or > > 2) Am I right to assume the the problem may be on the "admin" binary > that has enough information about the new root (paper_mail) to place the > list there but it is not capable of placing that information in the > configuration of the list? > > And finally, two different question that I will need to deal with as well > are: > > How can I eliminate references to "muskrat.stat.umn.edu" and use > only "stat.umn.edu"? Muskrat is an alias for our system but we may > like to change it to another piece of hardware sometime. I am not > telling the name "muskrat" to the configuration files but it seems to > pick it somewhere. > > How do I convert the old lists two the new version of mailman? > > > Thanks for your help! > -- Marisa Riviere U of M - Statistics marisa(a)stat.umn.edu 612-624-5859 "Aun es tarde, si, pero ya vamos" - N. R.

3 2

pending posts navigation
by matze 14 Jun '03

14 Jun '03

i just uploaded the following patch to sourceforge: "this patch permits to limit the number of posts shown in the pending admin interface. only mm_cfg.NUM_HELDS_PER_PAGE posts are shown per page, 'prev' and 'next' links are shown on the bottom of the page if needed" https://sourceforge.net/tracker/index.php?func=detail&aid=754661&group_id=1… /mtz -- ( ( ( i ) ) ) http://barcelona.indymedia.org ( ( ( i ) ) ) * using free software / Debian GNU/Linux | http://debian.org * gpg --keyserver keys.indymedia.org --recv-keys B9A88F6F "La guerra es un acto abominable en el que se matan personas que no se conocen, dirigidas por personas que se conocen y no se matan"

1 0