? This very message came to me with the following header:
Errors-To: mailman-developers-admin(a)python.org
All my bounces come to the list admin address, set in
the admin webpage, in the second field of General Options.
Do you have that set to something, and bounces still come to root?
> 2. Bounces are sent to the poor postmaster instead of a -admin address.
> I'm not entirely certain, but I think an Errors-To: header or something
> like that in all Mailman messages might allow one to distribute that load
> somewhat.
After nearly two years of development, we are happy to announce the
release of GNU Mailman 2.1. Mailman is free software that enables
users to manage email mailing lists and e-newsletters. Its integrated
web interface provides easy-to-use access for list members and list
administrators. Mailman supports built-in archiving, automatic bounce
processing, content filtering, digest delivery, spam filters, and
more.
Mailman 2.1 is fully internationalized, supporting 17 languages
out-of-the-box. A summary of additional new features in Mailman 2.1
is outlined below. The NEWS file in the source distribution contains
more details about all the new features.
For more information on Mailman, including downloading and
installation instructions, please visit one of the following mirror
sites:
http://www.list.orghttp://www.gnu.org/software/mailmanhttp://mailman.sf.net
The Mailman developers wish to thank Control.com for their sponsorship
of several Mailman 2.1 features, Zope Corporation for their support,
and the entire Mailman community for their contributions.
-Barry Warsaw
Pythonlabs, Zope Corporation
-------------------- snip snip --------------------
- Multi-lingual support for all web pages and Mailman generated email
notices, with languages selectable on a per-site, per-list, and
per-user basis.
- Through-the-web list creation and removal; (with automatic support
depending on the MTA)
- "Real name" support for members
- Improved simple user-task operation (e.g. no passwords required for
subscription and unsubscription).
- Support for personalized deliveries and VERP-like message delivery
for foolproof bounce detection
- Emergency moderation
- MIME-based content-filtering, with demime/stripmime-like options
- Regular expression based topic-filtering
- Better membership management, including searching
- Re-organized administrative requests pages
- Moderated newsgroup support
- A new architecture for the mail delivery subsystem, removing
dependence on cron, resulting in improved responsiveness and
scalability
- New moderation and privacy controls
- Invitations
- Autoresponse governors
- Users can now change some delivery options globally, for all lists
at a site, including their password, delivery status, real name, and
more.
- Improved MIME and I18n support in the archiver
- Addition of a separate "list moderator" role
- Urgent: header support (bypasses digests to reach all users
immediately).
One of my list members forwarded me the attached traceback. I'm don't
have much clue with regard to the email package, though, so I'm
passing it along to the group.
The fact that the user who sent me the report is using the French
locale may be of note.
The attached traceback was generated when the user attempted to
unsubscribe from a mailing list to which they belonged.
--
Jon Parise (jon(a)horde.org) :: The Horde Project (http://horde.org/)
Happy New Year everyone!
Mailman 2.1 is pushed out to the web sites and the download sites.
See http://www.list.org for the new web pages.
The only thing left is to make the announcement, and I'll do that
tomorrow some time. You'll notice that these lists have been
upgraded to 2.1 final, and hopefully everything's a-okay.
Note to i18n'ers: I've created a maintenance branch for future 2.1
patch releases. This way we can continue to develop new versions on
the trunk (whether that's 2.2 or 3.0 is still up in the air). If you
are making changes to i18n stuff for 2.1.1, please for now do so on
both the trunk and the branch, which is labeled Release_2_1-maint.
I would suggest having both checked out into different directories.
If you have cvs questions, please start here:
http://www.cvshome.org/docs/manual/cvs_5.html#SEC54
And follow up on this list with questions.
Cheers and g'night.
-Barry
Bugs item #214205, was opened at 2000-09-11 16:25
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_i…
Category: nntp/news
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 7
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Barry A. Warsaw (bwarsaw)
>Summary: e-mail<->usenet gateway Reply-To header (PR#303)
Initial Comment:
Jitterbug-Id: 303
Submitted-By: orion(a)tribble.dyndns.org
Date: Mon, 24 Jul 2000 18:54:02 -0400 (EDT)
Version: 2.0beta4
OS: Debian linux potato
I'm running a plain e-mail<->usenet gateway.
When someone replies to a usenet post through the list, his e-mail client sets
an In-Reply-To: header instead of a Reply-To: header. This causes newsreaders to
improperly thread messages.
I inserted the following bit into Mailman/Handlers/ToUsenet.py at around line
82:
# if the message is a reply to a previous post, change the header so
# that newsreaders can thread it properly
if msg.getheader('in-reply-to'):
msg.headers.append('References: %s\n' % msg.getheader('in-reply-to'))
del msg['in-reply-to']
I'm happy to say that this solved the problem.
(before you laugh at me, take note that I never looked at python before.)
====================================================================
Audit trail:
None
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:07
Message:
Logged In: YES
user_id=12800
Sigh. Very doubtful I'll get to look at the threading
issues before MM2.1 final. I'll address this again after
the release.
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-23 18:38
Message:
Logged In: YES
user_id=12800
Changing the group to 2.1 beta because I want to look at
threading issues for gated messages before 2.1 final is
released.
----------------------------------------------------------------------
Comment By: Giovanni Lopedote (giuans)
Date: 2002-05-01 08:34
Message:
Logged In: YES
user_id=531451
What a coincidence! I had the same problem and I looked
into the code, then modified it to work properly. The
coincidence is that my patch is *identical* to yours. So,
for sure it works :-)
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2000-09-27 17:00
Message:
RFC 2076 says nothing about using In-Reply-To for news, so it might not be a bad idea to copy In-Reply-To to References when gating a message from mail to news.
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2000-09-19 12:48
Message:
This sounds like the email client in question is broken. Mine for example, correctly inserts References: headers and the news readers properly thread the messages. I'm not inclined to cater to broken email or news clients.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=214205&group_i…
Bugs item #621689, was opened at 2002-10-10 23:10
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_i…
Category: (un)subscribing
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 7
Submitted By: Mark Dadgar (mdadgar)
Assigned to: Nobody/Anonymous (nobody)
Summary: Subscribe requests dropped from admin db
Initial Comment:
Occasionally, subscribe requests (via the web page) to a list that
requires moderator approval for subscriptions never make it to the
admin db for that list. They are listed in the subscribe log file, but
never show up on the admin db page.
Log file entries look like this:
Oct 10 18:43:43 2002 (31168) eventmasters: pending
XXXXXX.swfla.rr.com
But the admin db page for the list shows no outstanding issues.
I have verified that there was an actual subscription request
behind this log entry.
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-12-24 00:06
Message:
Logged In: YES
user_id=12800
I definitely need more information. I've neve been able to
reproduce the problem. Do you think it could be related to
the unofficial patches you've applied?
----------------------------------------------------------------------
Comment By: Mark Dadgar (mdadgar)
Date: 2002-12-06 02:29
Message:
Logged In: YES
user_id=598228
Ok, I verified that it's still a problem under 2.1b5 with the htdig and
indexing patches.
It's a real drag, too. :(
Please let me know if you need more debug info.
----------------------------------------------------------------------
Comment By: Mark Dadgar (mdadgar)
Date: 2002-11-22 01:08
Message:
Logged In: YES
user_id=598228
Unfortunately, it's still occurring under 2.1b4.
I'll check it under 2.1b5 as soon as the patches for htdig integration are
released, as I need those to implement.
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-10-22 10:11
Message:
Logged In: YES
user_id=12800
I'm going to defer this one until 2.1b4 goes out. I've
fixed some related bugs in cvs, so hopefully this will be
fixed in the new version.
----------------------------------------------------------------------
Comment By: Mark Dadgar (mdadgar)
Date: 2002-10-20 13:14
Message:
Logged In: YES
user_id=598228
Sorry - I'm running 2.1b3.
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-10-20 11:48
Message:
Logged In: YES
user_id=12800
What version of Mailman are you using. It's import to know
the exact version, i.e. 2.1beta3, or if you're running from
cvs. A lot of these problems have been fixed in cvs, which
will soon be released as 2.1 beta 4.
----------------------------------------------------------------------
Comment By: Mark Dadgar (mdadgar)
Date: 2002-10-11 00:29
Message:
Logged In: YES
user_id=598228
I just verified, by cat'ing pending.pck, that the appropriate changes
seem to be in there. But the web interface never picks them up.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=621689&group_i…
Bugs item #657443, was opened at 2002-12-22 03:08
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=657443&group_i…
Category: mail delivery
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 5
Submitted By: Demeilliez Bruno (dive_bruno)
Assigned to: Nobody/Anonymous (nobody)
Summary: Header and footer in multipart
Initial Comment:
Hi,
I have install mailman 2.1b6 on redhat 7.1.
My mailling list is in french and when I received mail
from the list with theBat, the header and the footer is
in multipart (like at the end).
I would like the bady and the footer was in the same
message.
Can you tell me if it's a bug or a configuration problem ?
And how I can resolve it ?
Thank's for your help.
Bruno
Example :
....
From: Bruno Demeilliez <webmaster(a)aquanaute.com>
X-Mailer: The Bat! (v1.62 Christmas Edition)
Organization: Aquanaute.com
X-Priority: 3 (Normal)
Message-ID: <11916819925.20021222110418(a)aquanaute.com>
To: test2(a)aquanaute.com
MIME-Version: 1.0
Subject: Test
X-BeenThere: test2(a)aquanaute.com
X-Mailman-Version: 2.1b6
Precedence: list
Reply-To: Bruno Demeilliez <webmaster(a)aquanaute.com>,
test2(a)aquanaute.com
List-Id: <test2.aquanaute.com>
List-Help:
<mailto:test2-request@aquanaute.com?subject=help>
List-Post: <mailto:test2@aquanaute.com>
List-Subscribe:
<http://www.aquanaute.com/mailman/listinfo/test2>,
<mailto:test2-request@aquanaute.com?subject=subscribe>
List-Archive: <http://www.aquanaute.com/pipermail/test2>
List-Unsubscribe:
<http://www.aquanaute.com/mailman/listinfo/test2>,
<mailto:test2-request@aquanaute.com?subject=unsubscribe>
Content-Type: multipart/mixed;
boundary="===============2617006012765839=="
Sender: test2-bounces(a)aquanaute.com
Errors-To: test2-bounces(a)aquanaute.com
--===============2617006012765839==
Content-Transfer-Encoding: 8bit
content-type: text/plain
Bonjour test2,
Amicalement,
Bruno
---
Pour l'équipe d'Aquanaute.comhttp://www.aquanaute.com
SARL de presse Aquanaute.com
8 rue Duployé
38100 Grenoble
France
Tél et Fax : 04 76 99 93 77
--===============2617006012765839==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
_______________________________________________
Liste de discussion Test2
Liste hébergée et administrée gratuitement par
Aquanaute.com
Présentation de la liste, Abonnement / Désabonnement :
http://www.aquanaute.com/mailman/listinfo/test2
Archives de la liste :
http://aquanaute.com/listes/Test2/
--===============2617006012765839==--
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=657443&group_i…
Bugs item #219808, was opened at 2000-10-30 17:13
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=219808&group_i…
Category: configuring/installing
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 7
Submitted By: Thomas Wouters (twouters)
Assigned to: Thomas Wouters (twouters)
Summary: Missing dependancy for 'configure'.
Initial Comment:
The Mailman makefile is missing a dependancy on 'configure', so when 'configure' is updated, it isn't re-run automatically, and you aren't warned to reconfigure. (definately low-priority bug though :)
(I also ran into something weird when running 'config.status' to do the reconfiguring for me... it set 'MAILMAN_UID' in Defaults.py to 'mailman', without quotes, instead of the numeric uid. That might be caused by a mix of an old config.status and a new configure, though, as I wasn't able to reproduce it on another box.)
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=219808&group_i…
Bugs item #451475, was opened at 2001-08-16 03:55
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=451475&group_i…
Category: nntp/news
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 7
Submitted By: CrackMonkey (monkeymaster)
Assigned to: Barry A. Warsaw (bwarsaw)
Summary: header munging ruins threading
Initial Comment:
The header hacking done by ToUsenet.py ruins threading
in mail! It takes a perfectly good message ID, and
throws it away! news replies to a mail message appear
to be replies to the parent (since the news messag
references contain the references of the parent + some
crazy mailman message ID).
This is bogus.
At the very least, could you add the real message ID
somewhere so that newsreaders will include it in the
references headers? Some of us actually use threaded
mailers, you know!
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-04-12 12:16
Message:
Logged In: YES
user_id=12800
The problem is that many NNTP servers are really picky about
message-id's; they won't allow duplicates, and they won't
allow cross-postings with the same message-id. I suppose if
the message had an id we could try to preserve it, attempt a
post, and if that's rejected by the nntpd, we could try
again with our own crafted message-id.
I'm up for any suggestions that are rfc-compliant and work
with the widest range of currently existing nntpds.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=451475&group_i…
Bugs item #659014, was opened at 2002-12-27 09:25
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659014&group_i…
Category: mail delivery
>Group: 2.1 final
Status: Open
Resolution: None
Priority: 5
Submitted By: Jost Krieger (jkrieger)
Assigned to: Nobody/Anonymous (nobody)
Summary: decoration problems with German lists
Initial Comment:
1. German is one of the languages where the mapping
to a acharacter set is currently ambiguous:
If you want a Euro sign, you have to use iso-8859-15,
most people still have iso-8859-1 and some have
iso-8859-2 (which also contains all German glyphs).
2. People hat getting there mails in three text/plain parts
(partly due to the deficiencies of their mail readers).
3. List owners tend to put plain ASCII into their
header and
footer files, but this doesn't help, unfortunately, as
Mailman
still thinks it *must* be iso-8859-1.
4. MIME RFCs recommend taking the lowest compatible
charset. This sometimes leads to Mailman messages
consisting of three ASCII parts.
One longtime solution would be to upgrade everything to
Unicode and downgrade it later on as far as possible.
This sounds expensive, though.
Another, cheaper possibility might be to attach a
character set to haeders and footers.
Jost
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=659014&group_i…