Mailman 3 April 2002 - Mailman-Developers

message posting in a loop with mailman 2.1b1
by Marc MERLIN 19 Apr '02

19 Apr '02

I just upgraded one of my servers to exim 4 and mailman choked badly on having exim refuse a message because exim did this: DNS lookup of scruznet.com (MX) gave TRY_AGAIN scruznet.com in dns_again_means_nonexist? no (option unset) returning DNS_AGAIN lookuphost router: defer for champney(a)scruznet.com message: host lookup did not complete ----------- end verify ------------ accept: condition test deferred SMTP>> 451 Temporary local problem - please try later The problem is that mailman decided that the whole post failed, and started to resend it in a loop. Apr 15 08:13:56 2002 (17389) post to keskydee from jean-luc(a)maisiere.com, size=3527, 9 failures Apr 15 08:17:54 2002 (17389) post to keskydee from jean-luc(a)maisiere.com, size=3527, 7 failures Apr 15 08:22:08 2002 (17389) post to keskydee from jean-luc(a)maisiere.com, size=3527, 8 failures (...) This also caused bounce scores against all the users and angered the membership obviously. I'm not sure how mailman could deal better with that, granted, it can be fixed on the exim side, but the problem is not obvious and the looping post is nasty. Since mailman doesn't know who many receipients it delivered to when it gets an error from the MTA (4xx or 5xx), I recommend that mailman moves the message in a separate queue dir, logs an error (possibly Emailing the list owner in the process) and gives up on the message. Resending it is only going to piss off the users that are getting the message each time mm tries. BTW, on the exim 4 side, I had: accept hosts = +localadds:+relay_from_hosts verify = recipient I solved the problem by adding this at the beginning of my rcpt ACL: accept hosts = 127.0.0.1 Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

3 5

problem with digest mode
by Veronica Loell 19 Apr '02

19 Apr '02

Sorry for the format, but I thought it was easiest to send it like this. We have encountered a problem that only appears in the digest-mode. Regular mode and the archives work fine. This is a sourceforge list I think it's mailman version 2.0.9-sf.net. Since this only appears in digest and not in archiving etc, it does seem like a bug. Please note that this is not about the header-subject-line. This is the text in the body of the message. I know that I occasionally have come across this, that is the chars being reported as unknown with their hex-code, but I'm not all that knowledgable about why it happens. - Veronica Loell mindtrader(a)users.sourceforge.net -------------------------------- Following is a copy of the bug-thread: -------------------------------- Bugs item #545956, was opened at 2002-04-19 01:25 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=545956&group_id… Category: None Group: None >Status: Open Resolution: Out of Date Priority: 5 Submitted By: Veronica Loell (mindtrader) Assigned to: Nobody/Anonymous (nobody) Summary: digest mode dont recognize latin-1 Initial Comment: We just started a list where we commicate in swedish and hence use åäö from Latin-1. One of the members have choosen digest-mode and we have discovered a problem. All our mails use latin-1, and in the non-digest form and also in the archives all charachters are displayed correctly. In digest form however, the letters äåö are marked as unknown, with their hex-numbers given. I have tested this by having both digest and non-digest delivered to me, using the same mailer etc. --------- Digest --------- Date: Thu, 18 Apr 2002 07:55:22 +0200 (W. Europe Daylight Time) From: Veronica Loell <info(a)nakawe.se> To: <ag-cling- cvs(a)lists.sourceforge.net> Subject: [cvs] =?ISO-8859- 1?Q?test_med_=E5=E4=F6?= Detta =E4r bara ett test f=F6r att utreda problemet med latin-1 i digestversionen. =C5=C4=D6 =E5=E4=F6 --------- Non-digest --------- Date: Thu, 18 Apr 2002 07:55:22 +0200 (W. Europe Daylight Time) From: Veronica Loell <info(a)nakawe.se> To: ag-cling- cvs(a)lists.sourceforge.net Subject: [cvs] test med åäö Detta är bara ett test för att utreda problemet med latin-1 i digestversionen. ÅÄÖ åäö ---------------------------------------------------------------------- >Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-19 14:40 Message: Logged In: YES user_id=12800 Well, now I'm not positive. Can you send a message to mailman-developers and see what other people think? ---------------------------------------------------------------------- Comment By: Veronica Loell (mindtrader) Date: 2002-04-19 14:04 Message: Logged In: YES user_id=156789 Actually mailman does handle it perfectly, it only happens in the digest mode. And it is also not the header that is the problem it's the body of the email. But if this has been corrected I'll report it to sourceforge because they apperantly are using an old version. I do get plenty of email where the header is messed up, but the rest of the message is not. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-19 13:53 Message: Logged In: YES user_id=12800 Mailman 2.1 will correctly handle non-ascii characters in headers. The problem is (probably) that the addition of the prefix breaks rfc2047 encoding of the non-ascii characters in the Subject: header. ---------------------------------------------------------------------- Comment By: Veronica Loell (mindtrader) Date: 2002-04-19 01:28 Message: Logged In: YES user_id=156789 I forgot to say. This is the listmanager managed by Sourceforge. ----------------------------------------------------------------------

1 0

RELEASED Mailman 2.0.10
by barry＠zope.com 19 Apr '02

19 Apr '02

Hot on the heels of the last release, I'm announcing Mailman 2.0.10 which fixes a few minor problems. See the NEWS file entries below. This is not a critical fix, although it will eliminate a confusing (but harmless) error message, and could provide better support for sites which use the qmail MTA. As usual, I've made both full source tarballs and patches available. See http://sourceforge.net/project/showfiles.php?group_id=103 for links to download all the patches and the source tarball. If you decide to install the patches, please do read the release notes first: http://sourceforge.net/project/shownotes.php?release_id=63042 See also: http://www.gnu.org/software/mailman http://www.list.org http://mailman.sf.net Cheers, -Barry 2.0.10 (09-Apr-2002) - Closed another small race condition. - Add the RFC-2822 recommended Message-ID: header on internally generated outgoing messages. Not all MTAs add this field if missing (read: Qmail).

2 5

Re: [Mailman-checkins] mailman/Mailman/Gui Topics.py,2.4,2.5
by Ron Jarrell 19 Apr '02

19 Apr '02

At 03:24 PM 4/18/02 -0700, you wrote: >+ # Make sure the pattern was a legal regular expression >+ try: >+ syslog('error', 'pattern: %s', pattern) >+ re.compile(pattern) >+ except (re.error, TypeError): Hey, Barry, this change to Topics? Did you really want to syslog every possible pattern to the error log, or did you perchance leave a debugging syslog in there again :-)

2 1

Fw: [Mailman-Developers] 2.1b1 "bad character range" error
by Sarah K. Miller 19 Apr '02

19 Apr '02

I discovered that this error is caused when there is a dash (-) entered in the Regexp for the topic keywords. Remove the dash, end of error. > ----- Original Message ----- > From: "Sarah K. Miller" <techgrrl(a)beeze.com> > To: <mailman-developers(a)python.org> > Sent: Tuesday, April 16, 2002 4:56 PM > Subject: [Mailman-Developers] 2.1b1 "bad character range" error > > > > I'm seeing quite a few of these in my 2.1b1 logs. Any idea what might be causing them? > > > > Apr 16 16:00:26 2002 (27714) Uncaught runner exception: bad character range > > Apr 16 16:00:26 2002 (27714) Traceback (most recent call last): > > File "/usr/local/mailman/Mailman/Queue/Runner.py", line 103, in __oneloop > > self.__onefile(msg, msgdata) > > File "/usr/local/mailman/Mailman/Queue/Runner.py", line 153, in __onefile > > keepqueued = self._dispose(mlist, msg, msgdata) > > File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 111, in _dispose > > status = self._dopipeline(mlist, msg, msgdata, pipeline) > > File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 134, in _dopipeline > > sys.modules[modname].process(mlist, msg, msgdata) > > File "/usr/local/mailman/Mailman/Handlers/Tagger.py", line 54, in process > > cre = re.compile(pattern, re.IGNORECASE | re.VERBOSE) > > File "/usr/local/lib/python2.2/sre.py", line 178, in compile > > return _compile(pattern, flags) > > File "/usr/local/lib/python2.2/sre.py", line 228, in _compile > > raise error, v # invalid expression > > error: bad character range

2 1

2.1b1 "bad character range" error
by Sarah K. Miller 18 Apr '02

18 Apr '02

I'm seeing quite a few of these in my 2.1b1 logs. Any idea what might be causing them? Apr 16 16:00:26 2002 (27714) Uncaught runner exception: bad character range Apr 16 16:00:26 2002 (27714) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 103, in __oneloop self.__onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 153, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 111, in _dispose status = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 134, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/Tagger.py", line 54, in process cre = re.compile(pattern, re.IGNORECASE | re.VERBOSE) File "/usr/local/lib/python2.2/sre.py", line 178, in compile return _compile(pattern, flags) File "/usr/local/lib/python2.2/sre.py", line 228, in _compile raise error, v # invalid expression error: bad character range -- Sarah Plus ça change, plus c'est la même chose

2 1

feature removal request: web_page_url
by Joern Nettingsmeier 17 Apr '02

17 Apr '02

hello ! i'd like to ask for a removal of the web_page_url field in the admin web interface. i don't see why a list admin would want or should even be allowed to change this. maybe i'm overlooking something ? (yeah, i filled something in, read the details, wanted to discard the changes, and on the next submit, i got screwed over by my browser's form cache :((( ) best regards, and thanks for putting mailman together, jörn -- Watch out where the huskies go and don't you eat the yellow snow ! - Frank Zappa

1 0

Stripping binaries attachments
by Gian Franco Baroni 16 Apr '02

16 Apr '02

Hi, I didn't find a way to filter out binary attachments from the mails sent to a Mailman server. Anyone has a clue? Thanks GFB

3 2

Re: [Mailman-Developers] Stripping binaries attachments
by J C Lawrence 16 Apr '02

16 Apr '02

On Tue, 16 Apr 2002 10:18:23 +0200 Gian Franco Baroni <fbaroni(a)axoadi.it> wrote: > I didn't find a way to filter out binary attachments from the > mails sent to a Mailman server. Anyone has a clue? Please see the FAQ: http://www.python.org/cgi-bin/faqw-mm.py -- 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

Re: [Mailman-Developers] Changing web_page_url in mm 2.1
by ml+mm-dev＠riyescott.com 16 Apr '02

16 Apr '02

On 13 Apr 2002 00:32:51 -0700, Marc MERLIN <marc_news(a)vasoftware.com> wrote: > I have web_page_url set to the wrong value for a list I just created. > Outside of using config_list, is there any easier way to change the domain > the list is in? I also noticed this wasn't in config_list. After an interesting learning experience, I wrote the script below, which I used with withlist. It would be better if it took the new domain name from the command line. HTH. Invocation to change *all* lists: bin/withlist -l -r urllist.urlfix -a File urllist.py ---------------------------------------------------------------- # List web_page_url # To invoke: bin/withlist [-q] -r urllist -a def urllist(mlist): print 'List: ', mlist.internal_name() print ' web_page_url: ', mlist.web_page_url # Update web_page_url, which doesn't seem to be covered in bin/config_list. # To invoke: bin/withlist [-q] -l -r urllist.urlfix -a def urlfix(mlist): print 'List: ', mlist.internal_name() print ' web_page_url before: ', mlist.web_page_url mlist.web_page_url = "http://newname.com/mailman/" print ' web_page_url after: ', mlist.web_page_url mlist.Save() ---------------------------------------------------------------- -- Dale

1 0