[Mailman-Users] decoding bug of non-ascii MIME encoded subject
Pipermail 0.05 (Mailman edition) does not seem to decode non-ascii MIME subject correctly under some conditions, even the Prefix for subject line of list postings has been emptied. Attached ma1 files are captured before ma2 files. The messages sent by Reed Lai are subjected with iso-8859-1 encoding for big5 characters. The messages sent by SunnyCat are subjected with big5 encoding for big5 characters. The decoding seems to be determined by last message. -- Reed Lai (key #1) [EMAIL PROTECTED] http://w3.icpdas.com/reed/ Fingerprint 7EB3 6A2B 3C32 64E9 232C D7F7 61BF F5B2 7199 EAD3 ICP DAS Co., Ltd. [EMAIL PROTECTED] http://www.icpdas.com/ ma1.png Description: PNG image From [EMAIL PROTECTED] Fri Dec 28 07:58:24 2001 From: [EMAIL PROTECTED] (Reed Lai) Date: Fri, 28 Dec 2001 15:58:24 +0800 Subject: =?iso-8859-1?Q?=A4=A4=A4=E5=BC=D0=C3D=B4=FA=B8=D5?= Message-ID: [EMAIL PROTECTED] ¤¤¤å¼ÐÃD´ú¸Õ -- Reed Lai (key #1) [EMAIL PROTECTED] http://w3.icpdas.com/reed/ Fingerprint 7EB3 6A2B 3C32 64E9 232C D7F7 61BF F5B2 7199 EAD3 ICP DAS Co., Ltd. [EMAIL PROTECTED] http://www.icpdas.com/ From [EMAIL PROTECTED] Fri Dec 28 08:02:40 2001 From: [EMAIL PROTECTED] (Reed Lai) Date: Fri, 28 Dec 2001 16:02:40 +0800 Subject: =?iso-8859-1?Q?=A4=A4=A4=E5=BC=D0=C3D=B4=FA=B8=D5?= In-Reply-To: [EMAIL PROTECTED]; from [EMAIL PROTECTED] on Fri, Dec 28, 2001 at 03:58:24PM +0800 References: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] again On Fri, Dec 28, 2001 at 03:58:24PM +0800, Reed Lai wrote: ¤¤¤å¼ÐÃD´ú¸Õ -- Reed Lai (key #1) [EMAIL PROTECTED] http://w3.icpdas.com/reed/ Fingerprint 7EB3 6A2B 3C32 64E9 232C D7F7 61BF F5B2 7199 EAD3 ICP DAS Co., Ltd. [EMAIL PROTECTED] http://www.icpdas.com/ -- Reed Lai (key #1) [EMAIL PROTECTED] http://w3.icpdas.com/reed/ Fingerprint 7EB3 6A2B 3C32 64E9 232C D7F7 61BF F5B2 7199 EAD3 ICP DAS Co., Ltd. [EMAIL PROTECTED] http://www.icpdas.com/ From [EMAIL PROTECTED] Fri Dec 28 08:50:16 2001 From: [EMAIL PROTECTED] (SunnyCat) Date: Fri, 28 Dec 2001 16:50:16 +0800 Subject: =?big5?B?pKSk5bzQw0S0+rjV?= Message-ID: 00b401c18f7c$ac55b7e0$[EMAIL PROTECTED] ¤¤¤å¼ÐÃD´ú¸Õ From [EMAIL PROTECTED] Fri Dec 28 09:11:09 2001 From: [EMAIL PROTECTED] (SunnyCat) Date: Fri, 28 Dec 2001 17:11:09 +0800 Subject: ¤¤¤å¼ÐÃD´ú¸Õ2 Message-ID: 00c401c18f7f$96e51a60$[EMAIL PROTECTED] This is a multi-part message in MIME format. --=_NextPart_000_00C0_01C18FC2.A4D5FFC0 Content-Type: text/plain; charset=big5 Content-Transfer-Encoding: 8bit ¤¤¤å¼ÐÃD´ú¸Õ2 --=_NextPart_000_00C0_01C18FC2.A4D5FFC0 Content-Type: text/html; charset=big5 Content-Transfer-Encoding: quoted-printable !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN HTMLHEAD META content=3Dtext/html; charset=3Dbig5 http-equiv=3DContent-Type META content=3DMSHTML 5.00.2919.6307 name=3DGENERATOR STYLE/STYLE /HEAD BODY bgColor=3D#ff DIVFONT = size=3D2=A4=A4=A4=E5=BC=D0=C3D=B4=FA=B8=D52/FONT/DIV/BODY/HTML --=_NextPart_000_00C0_01C18FC2.A4D5FFC0-- From [EMAIL PROTECTED] Mon Dec 31 03:01:33 2001 From: [EMAIL PROTECTED] (SunnyCat) Date: Mon, 31 Dec 2001 11:01:33 +0800 Subject: =?big5?B?pKSk5bT6uNUz?= Message-ID: 002d01c191a7$744db460$[EMAIL PROTECTED] ¤¤¤å¼ÐÃD´ú¸Õ3 From [EMAIL PROTECTED] Mon Dec 31 03:29:24 2001 From: [EMAIL PROTECTED] (Reed Lai) Date: Mon, 31 Dec 2001 11:29:24 +0800 Subject: =?iso-8859-1?Q?=A4=A4=A4=E5=B4=FA=B8=D53?= In-Reply-To: 002d01c191a7$744db460$[EMAIL PROTECTED]; from [EMAIL PROTECTED] on Mon, Dec 31, 2001 at 11:01:33AM +0800 References: 002d01c191a7$744db460$[EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Reply test. On Mon, Dec 31, 2001 at 11:01:33AM +0800, SunnyCat wrote: ¤¤¤å¼ÐÃD´ú¸Õ3 ___ ICPDAS Test mailing list -- [EMAIL PROTECTED] http://www.icpdas.com/mailman/listinfo/test -- Reed Lai (key #1) [EMAIL PROTECTED] http://w3.icpdas.com/reed/ Fingerprint 7EB3 6A2B 3C32 64E9 232C D7F7 61BF F5B2 7199 EAD3 ICP DAS Co., Ltd. [EMAIL PROTECTED] http://www.icpdas.com/ ma2.png Description: PNG image From [EMAIL PROTECTED] Fri Dec 28 07:58:24 2001 From: [EMAIL PROTECTED] (Reed Lai) Date: Fri, 28 Dec 2001 15:58:24 +0800 Subject: =?iso-8859-1?Q?=A4=A4=A4=E5=BC=D0=C3D=B4=FA=B8=D5?= Message-ID: [EMAIL PROTECTED] ¤¤¤å¼ÐÃD´ú¸Õ -- Reed Lai (key #1) [EMAIL PROTECTED] http://w3.icpdas.com/reed/ Fingerprint 7EB3 6A2B 3C32 64E9 232C D7F7 61BF F5B2 7199 EAD3 ICP DAS Co., Ltd. [EMAIL PROTECTED] http://www.icpdas.com/ From [EMAIL PROTECTED] Fri Dec 28 08:02:40 2001 From: [EMAIL PROTECTED] (Reed Lai) Date: Fri, 28 Dec 2001 16:02:40 +0800 Subject: =?iso-8859-1?Q?=A4=A4=A4=E5=BC=D0=C3D=B4=FA=B8=D5?= In-Reply-To: [EMAIL PROTECTED]; from [EMAIL PROTECTED] on Fri, Dec 28, 2001 at 03:58:24PM +0800 References: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] again On Fri, Dec 28, 2001 at 03:58:24PM +0800, Reed Lai wrote: ¤¤¤å¼ÐÃD´ú¸Õ -- Reed Lai (key #1) [EMAIL PROTECTED] http://w3.icpdas.com/reed/ Fingerprint
Re: [Mailman-Users] Re: problems setting up a mailing list
Thanks for your reply, I installed mailman with the 2.0.8 tarfile. I checked the tar file and mail/wrapper doesn't exist within it, i'm not sure if this is supposed to get created diring the 'make install' or not. I am running sendmail and I know it will resolv hostnames, etc fine. All mail services work ok for me. On Sun, 30 Dec 2001, C. Bensend wrote: On Sun, 30 Dec 2001, Justin Zygmont wrote: here is the output of bin/check_perms: Traceback (innermost last): File bin/check_perms, line 281, in ? checkmail() File bin/check_perms, line 202, in checkmail mode = statmode(wrapper) File bin/check_perms, line 74, in statmode return os.stat(path)[ST_MODE] OSError: [Errno 2] No such file or directory: '/home/mailman/mail/wrapper' OK, THAT is a problem. If wrapper isn't there, no mail is going to be handled. How did you install Mailman (pardon me if you mentioned it in a previous post, I'm just catching up on my email)? RPM? From source? .deb? here's the last 10 lines of logs/smtp: Dec 30 03:37:02 2001 (32701) All recipients refused: host not found Dec 30 03:37:02 2001 (32701) smtp for 1 recips, completed in 0.071 seconds Dec 30 03:38:02 2001 (32704) All recipients refused: host not found Dec 30 03:38:02 2001 (32704) smtp for 1 recips, completed in 0.123 seconds Dec 30 03:38:02 2001 (32704) All recipients refused: host not found Dec 30 03:38:02 2001 (32704) smtp for 1 recips, completed in 0.072 seconds Dec 30 03:39:02 2001 (32717) All recipients refused: host not found Dec 30 03:39:02 2001 (32717) smtp for 1 recips, completed in 0.115 seconds Dec 30 03:39:03 2001 (32717) All recipients refused: host not found Dec 30 03:39:03 2001 (32717) smtp for 1 recips, completed in 0.073 seconds It looks like your mailserver (or whatever host Mailman is running on) can't resolve hostnames. Check to make sure your local host has both 'localhost' and 'your-FQDN' in it's /etc/hosts file to be safe. Also, make sure your MTA can resolve the hostname and domain you subscribed yourself with. It'll need to relay from localhost (this can be a problem with QMail). Benny ~~ The onions are irritating my buttocks. - Sluggy Freelance 10-12-1998 -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Problems with undeliverable mail
On Sun, 30 Dec 2001 14:37:08 -0800 Michelle Brownsworth [EMAIL PROTECTED] wrote: That makes good sense, Charlie. Only problem is, I don't know how to accomplish it in sendmail without enabling FEATURE(relay_local_from), something I am loath to do for security reasons. According to cf/README in the sendmail source: You have just found one of the larger reasons Sendmail is well thought on these lists. If anyone on the list can tell me how to configure sendmail to accept mail from localhost without checking for a valid domain either without using FEATURE(relay_local_from) or using it without compromising security, I would greatly appreciate it. Chuq Von Rospach has posted extensive details on the area to the -developers list. Search the archives (it may also have been copied to the FAQ by now). Best advice: Install a decent MTA. -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Okay, okay... I know when to throw in the towel. :^) I'll investigate Postfix, with the hope that it's better than Qmail. After running it on a server for a couple of years, I don't care for Qmail at all. .\\ichelle -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Brain Dead
Well I am know to have my Senior Moments, But this morning I have experienced total brain death. I am trying to get the copyright character into a footer on a Announce Only list that is a daily devoitional that is published by one of my clients. I think that I tried everything under the sun but the right syntax. Someone help this old grouch please. BTW this is the list server that is verylow in horsepower and I have cloned the whole mess to a test box and trying so far in vain to get postfix to work in a total virtual domain setup. But since all 14 of the list are announce only and they become active at midnight tonight maybe it will hold up until I can get postfix up on a better server. Thanks for the postfix hints and kinks. Mel -- -- System Janitor/Network Plumber http://www.nwla.com Linux User #25446Linux 2.4.7 -- -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Mailman/Sendmail issue
The server platform is RedHat version 7.2, Sendmail 8.11 and Mailman 2.08. My problem is an error generated when the post script is run. If my sendmail config file MTA entry is set for the correct IP an error is generated in the mailman/smtp error log connection refused, but I can send email back and forth through Sendmail. If I put the loopback address 127.0.0.1 for the MTA in my sendmail config file the postings will go out but mail cannot be sent back to the server since the loopback address is in the config file not the correct ip address. I found a couple of archives referring to the connection refused error, but I could not find any response to correct the problem. Any guidance would be appreciated. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman/Sendmail issue
Well David by default Red Hat 7.2 does not port mail through the LAN. I had to do two thing first of all in /etc/mail/sendmail.mc I had to dnl this line DAEMON_OPTIONS (`Port_SMTP, ADDR=127.0.0.1, Name=MTA`) and rebuild the sendmail.cf and Then in the /etc/mail/access I had to add 127.0.0.1 RELAY and also the DOMAIN and the IP range thereof for Relay. Sorry I haven't been paying attention to the list much very bust day. Mel -- -- System Janitor/Network Plumber http://www.nwla.com Linux User #25446Linux 2.4.7 -- -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Mailman/Sendmail issue
I appreciate the response, but if I add the loopback address(127.0.0.1) in my sendmail.cf file I cannot receive mail sent to the machine from the outside since my MX or mail DNS entry is mapped to an IP other than the local loopback. -Original Message- From: mel [mailto:[EMAIL PROTECTED]] Sent: Monday, December 31, 2001 11:16 AM To: David Krebsbach Cc: '[EMAIL PROTECTED]' Subject: Re: [Mailman-Users] Mailman/Sendmail issue Well David by default Red Hat 7.2 does not port mail through the LAN. I had to do two thing first of all in /etc/mail/sendmail.mc I had to dnl this line DAEMON_OPTIONS (`Port_SMTP, ADDR=127.0.0.1, Name=MTA`) and rebuild the sendmail.cf and Then in the /etc/mail/access I had to add 127.0.0.1 RELAY and also the DOMAIN and the IP range thereof for Relay. Sorry I haven't been paying attention to the list much very bust day. Mel -- -- System Janitor/Network Plumber http://www.nwla.com Linux User #25446Linux 2.4.7 -- -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Qrunner not sending out messages
Hello, Have a weird problem with Mailman. For older lists, when messages are approved they are mailed out. For newer lists, the messages are approved then they vanish. The messages are not posted to the list. Today I figured out that if I run qrunner by hand, the messages will be posted. If the cron runs Qrunner then the messages are lost. Anyone know why this would happen? I get no error messages Redhat 6.1 Python 1.5.3 Mailman 2.0.1 cron /usr/bin/python -S /home/mailman/cron/qrunner. Jim -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Problems with undeliverable mail
On Sun, Dec 30, 2001 at 11:48:21PM -0800, Michelle Brownsworth wrote: To: [EMAIL PROTECTED] From: Michelle Brownsworth [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Problems with undeliverable mail Cc: J C Lawrence [EMAIL PROTECTED] Date: Sun, 30 Dec 2001 23:48:21 -0800 [snip] Okay, okay... I know when to throw in the towel. :^) I'll investigate Postfix, with the hope that it's better than Qmail. After running it on a server for a couple of years, I don't care for Qmail at all. In your .mc file, define(`confDELIVERY_MODE', `deferred') This will stop sendmail from doing DNS queries upon accepting the mail. It's intended for situations where you want to prevent DNS lookups (dialup, mainly). I hope that does what you want. Graham -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
RE: [Mailman-Users] Problems with undeliverable mail
This works, and works well, but If I'm correct also creates an open-relay, for security reasons this is usually unacceptable. This was the primary reason I switched to postfix, same functionality minus the security gap. -Richard Idalski -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Graham Dunn Sent: Monday, December 31, 2001 1:41 PM To: Michelle Brownsworth Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Problems with undeliverable mail On Sun, Dec 30, 2001 at 11:48:21PM -0800, Michelle Brownsworth wrote: To: [EMAIL PROTECTED] From: Michelle Brownsworth [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Problems with undeliverable mail Cc: J C Lawrence [EMAIL PROTECTED] Date: Sun, 30 Dec 2001 23:48:21 -0800 [snip] Okay, okay... I know when to throw in the towel. :^) I'll investigate Postfix, with the hope that it's better than Qmail. After running it on a server for a couple of years, I don't care for Qmail at all. In your .mc file, define(`confDELIVERY_MODE', `deferred') This will stop sendmail from doing DNS queries upon accepting the mail. It's intended for situations where you want to prevent DNS lookups (dialup, mainly). I hope that does what you want. Graham -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
RE: [Mailman-Users] Problems with undeliverable mail
This works, and works well, but If I'm correct also creates an open-relay, for security reasons this is usually unacceptable. This was the primary reason I switched to postfix, same functionality minus the security gap. -Richard Idalski I appreciate Graham's suggestion, but after having a good look-see at Postfix last night, I'm leaning toward giving it a shot. It certainly comes well-recommended. However, it might be wise to investigate Exim as well. Any thoughts as to relative strengths and weaknesses, features, ease of configuration, security, etc. between the two? .\\ichelle -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Graham Dunn Sent: Monday, December 31, 2001 1:41 PM To: Michelle Brownsworth Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Problems with undeliverable mail On Sun, Dec 30, 2001 at 11:48:21PM -0800, Michelle Brownsworth wrote: To: [EMAIL PROTECTED] From: Michelle Brownsworth [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Problems with undeliverable mail Cc: J C Lawrence [EMAIL PROTECTED] Date: Sun, 30 Dec 2001 23:48:21 -0800 [snip] Okay, okay... I know when to throw in the towel. :^) I'll investigate Postfix, with the hope that it's better than Qmail. After running it on a server for a couple of years, I don't care for Qmail at all. In your .mc file, define(`confDELIVERY_MODE', `deferred') This will stop sendmail from doing DNS queries upon accepting the mail. It's intended for situations where you want to prevent DNS lookups (dialup, mainly). I hope that does what you want. Graham -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
RE: [Mailman-Users] Problems with undeliverable mail
As far as ease of configuration goes, postfix was a snap. It's basically a drop in replacement for sendmail, simpley backup you sendmail binaries, ie; /usr/bin/mailq /usr/bin/newaliases, and /usr/sbin/sendmail. If you have any problems with postfix reverting back to sendmail is as easy as repacing the new binaries with the old. That came in handy as I was working out bugs on a live system. This was on a FreeBSD 4.3 system running mailman 2.08. I've never run Exim so I know not of the ease of it's transition. -Richard Idalski -Original Message- From: Michelle Brownsworth [mailto:[EMAIL PROTECTED]] Sent: Monday, December 31, 2001 3:22 PM To: [EMAIL PROTECTED] Cc: Richard Idalski; Graham Dunn Subject: RE: [Mailman-Users] Problems with undeliverable mail This works, and works well, but If I'm correct also creates an open-relay, for security reasons this is usually unacceptable. This was the primary reason I switched to postfix, same functionality minus the security gap. -Richard Idalski I appreciate Graham's suggestion, but after having a good look-see at Postfix last night, I'm leaning toward giving it a shot. It certainly comes well-recommended. However, it might be wise to investigate Exim as well. Any thoughts as to relative strengths and weaknesses, features, ease of configuration, security, etc. between the two? .\\ichelle -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Graham Dunn Sent: Monday, December 31, 2001 1:41 PM To: Michelle Brownsworth Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Problems with undeliverable mail On Sun, Dec 30, 2001 at 11:48:21PM -0800, Michelle Brownsworth wrote: To: [EMAIL PROTECTED] From: Michelle Brownsworth [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Problems with undeliverable mail Cc: J C Lawrence [EMAIL PROTECTED] Date: Sun, 30 Dec 2001 23:48:21 -0800 [snip] Okay, okay... I know when to throw in the towel. :^) I'll investigate Postfix, with the hope that it's better than Qmail. After running it on a server for a couple of years, I don't care for Qmail at all. In your .mc file, define(`confDELIVERY_MODE', `deferred') This will stop sendmail from doing DNS queries upon accepting the mail. It's intended for situations where you want to prevent DNS lookups (dialup, mainly). I hope that does what you want. Graham -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Postfix (was Problems with undeliverable mail)
At 03:30 PM 12/31/01 -0500, Richard Idalski wrote: As far as ease of configuration goes, postfix was a snap. It's basically a drop in replacement for sendmail, simpley backup you sendmail binaries, ie; /usr/bin/mailq /usr/bin/newaliases, and /usr/sbin/sendmail. If you have any problems with postfix reverting back to sendmail is as easy as repacing the new binaries with the old. That came in handy as I was working out bugs on a live system. Does anyone know if it's possible to run Postfix on a high port while sendmail is still running? e.g. not install Postfix's sendmail binary over real sendmail? -- Bill Moseley mailto:[EMAIL PROTECTED] -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] Hi
We've been running version 207 for linux for a while, and with the recent update to 208 mailman has been eating a ton of cpu resources (i.e. 90% of cpu time). What can we do to reduce that to a sane level? Davin Overland
Re: [Mailman-Users] Problems with undeliverable mail
On Mon, 31 Dec 2001 13:40:41 -0500 Graham Dunn [EMAIL PROTECTED] wrote: On Sun, Dec 30, 2001 at 11:48:21PM -0800, Michelle Brownsworth wrote: In your .mc file, define(`confDELIVERY_MODE', `deferred') This will stop sendmail from doing DNS queries upon accepting the mail. It's intended for situations where you want to prevent DNS lookups (dialup, mainly). I hope that does what you want. It has the side effect of disabling many of Sendmail's anti-spam traps. You may also want to re-examine the Mail-followup-To: header you are inserting: Mail-followup-to: Graham Dunn [EMAIL PROTECTED], Michelle Brownsworth [EMAIL PROTECTED], [EMAIL PROTECTED] Note the first address. Wishes vainly that mail-Followup-To was soundly ignored as the Bad Idea it is -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
[Mailman-Users] RELEASE Mailman 2.1 alpha 4
Hi all, Just wanted to let you know that I've released Mailman 2.1 alpha 4. Below is the big list of changes with this release. This will be the last alpha release for 2.1, but this still leaves open the possibility of a few new features in MM2.1. I've got everything in that I intend to get in. If you've got a pet new feature -- and have code that implements it -- please do remind me about it now and I'll work on getting in what I can for the first beta. Apologies for falling so far behind in the mailing list traffic. This is admittedly a bit of a rushed release. I really wanted to get this out before the end of the year (in my timezone at least ;). Depending on my other real-job commitments, I'll be spending all my spare time getting bugs fixed and moving toward the 2.1 final release. I'm shooting for release by the Python conference in February, but I don't know if I'll make it. Cheers, and happy new year to you all. I-swear-the-X-Oblique-Strategy-was-chosen-random-ly y'rs, -Barry snip snip 2.1 alpha 4 (31-Dec-2001) - The administrative requests database page (admindb) has been redesigned for better usability when there are lots of held postings. Changes include: o A summary page which groups held messages by sender email address. On this page you can dispose of all the sender's messages in one action. You can also view the details of all the sender's messages, or the details of a single message. You can also add the sender to one of the list's sender filters. o A details page where you can view all messages, just those for a particular sender, or just a single held message. This details page is laid out the same as the old admindb page. o The instructions have been shorted on the summary and details page, with links to more detailed explanations. - Bounce processing o Mailman now keeps track of the reason a member's delivery has been disabled: explicitly by the administrator, explicitly by the user, by the system due to excessive bounces, or for (legacy) unknown reasons. o A new bounce processing algorithm has been implemented (we might actually understand this one ;). When an address starts bouncing, the member gets a bounce score. Hard (fatal) bounces score 1.0, while soft (transient) bounces score 0.5. List administrators can specify a bounce threshold above which a member gets disabled. They can also specify a time interval after which, if no bounces are received from the member, the member's bounce score is considered stale and is thrown away. o A new cron script, cron/disabled, periodically sends notifications to members who are bounce disabled. After a certain number of warnings the member is deleted from the list. List administrators can control both the number of notifications and the amount of time between notifications. Notifications include a confirmation cookie that the member can use to re-enable their subscription, via email or web. o New configuration variables to support the bounce processing are DEFAULT_BOUNCE_SCORE_THRESHOLD, DEFAULT_BOUNCE_INFO_STALE_AFTER, DEFAULT_BOUNCE_YOU_ARE_DISABLED_WARNINGS, DEFAULT_BOUNCE_YOU_ARE_DISABLED_WARNINGS_INTERVAL. - Privacy and security o Sender filters can now be regular expressions. If a line starts with ^ it is taken as a (raw string) regular expression, otherwise it is a literal email address. o Fixes in 2.0.8 ported forward: prevent cross-site scripting exploits. - Mail delivery o Aliases have all been changed so that there's more consistency between the alias a message gets delivered to, and the script queue runner that handles the message. I've also renamed the mail wrapper script to `mailman' from `wrapper' to avoid collisions with other MLM's. You /will/ need to regenerate your alias files with bin/genaliases, and you may need to update your smrsh (Sendmail) configs.a Bounces always go to listname-bounces now, since administration has been separated from bounce processing. listname-admin is obsolete. o VERP support! This greatly improves the accuracy of bounce detection. Configuration variables which control this feature include VERP_DELIVERY_INTERVAL, VERP_PERSONALIZED_DELIVERIES, VERP_PASSWORD_REMINDERS, VERP_REGEXP, and VERP_FORMAT. The latter two must be tuned to your MTA. o A new alias [EMAIL PROTECTED] is added which directs all output to the file
