Recently Tin Tvrtković tried to subscribe to the pypy-dev mailing list.
He got the "Bug in Mailman version 2.1.15 We're sorry, we hit a bug!" message.
When he tried to reply to the confirmation message, he got it again.
It looks like it could possibly be this 10 year old bug that Mark was
unable to reproduce at the time ....
but we don't have a traceback, so maybe not.
We can reproduce the problem all we like; it is with the last character
in Tin's name, which is U+0107. Tin is Croatian, so I assume that is what
his character set is on his machine, but I get this here, too. pypy-dev
is configured with a default lanaguage of English(USA).
Should I make a bug report, or is this already fixed in later versions
Hi Mailman users,
I moved a list to a newer server today and was able to succesfully load the users and the private archives.
All works well except when loged in the admin interface and I want to go to the archives.
The link is not correct and point to /pipermail/mylist instead of /cgi-bin/mailman/private/mylist/
I've ran the fix URL as this was of course broken and repimported the archives with new URL.
This is the last piece that drives me crazy :)
Many thanks for your help.
Unless Google App Engine has changed recently, it cannot receive any
mail at all. So you need to move your mailing list software to
someplace else, mailman friendly. There is no hope of doing what you
Sorry about that,
I am pleased to announce the second release candidate for Mailman 2.1.19.
Python 2.4 is the minimum supported, but Python 2.7 is recommended.
This release has several new features since 2.1.18-1, some newly
implemented and some backported from the now truly defunct 2.2 branch -
there is nothing left in that branch that isn't in this release.
Associated with those changes are many things that have i18n impacts
including new and modified strings in the message catalog, a new
adminaddrchgack.txt template and a minor change to the
I strongly encourage anyone with an interest in translations of Mailman
to get this release and help with updating the translations.
There are also bug fixes.
See the attached README for more details.
The differences between this and the first 2.1.19 candidate are the
The subscribe_auto_approval feature in the first candidate has been
augmented to accept @listname to auto approve members of another list.
Organization: headers are unconditionally removed from posts to
anonymous lists and a bug involving ANONYMOUS_LIST_KEEP_HEADERS has been
fixed. (LP: #1419132)
The admindb interface display of a held message body has been fixed to
not stop in the middle of a multi-byte character and not fail to convert
to the display character set message bodies with invalid characters.
Additionally, and the main reason for this second candidate, Mailman's
character set for both Romanian and Russian has been changed to utf-8.
(LP: #1418735) and (LP: #1418448). This may be disruptive in that
following this change, some archive pages and some list attributes for
lists whose preferred_language is one of those two languages may not
display correctly. Archives can be fixed by running 'bin/arch --wipe'
for the affected lists, but list attributes will probably have to be
fixed manually. I hope the benefits of this change will outweigh the
pain, and I encourage anyone with Romanian or Russian Language lists to
try this release and report your experience. It may be possible to fix
at least some list attributes programmatically as part of the version
I plan to release the final 2.1.19 release at the end of February, and
it would be good to have as many i18n updates as possible by then.
Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.
For more information, please see:
Mailman 2.1.19rc2 can be downloaded from
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
>> Anything obviously wrong with this idea?
>It doesn't seem that the 'mover' should be checking the age of things in
>queue 1. The idea is just to not send messages more than a few times a
>day, not to introduce extra delay.
>Also, it's easy to configure Mailman to use some smtp port other than 25
>for sending and thus send only to to the first sendmail and be the only
>thing that does so, but you may not want to delay all Mailman mail, e.g.
>an on demand password reminder or a held message notification. The mover
>needs to be smart. I think it should check queue1 frequently and if a
>queued message has a Mailman generated Message-ID: of the form
><mailman\.\d+\.\d+\.\d+\..+@.+> move it right now, otherwise wait until
>x hours since the last "bulk move" at which time it moves everything and
>updates the last bulk move time.
>Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
>San Francisco Bay Area, California better use your sense - B. Dylan
Well, after giving the problem a night's worth of thought, I think the
best idea for this problem is to use sendmail. Or rather to use 2
of them. The first one just receives mail and queues it. But
it is configured to _not_ process the mail queue.
The second one is configured so that it processes its own mail queue.
Then you write an external program that wakes up every so often, and
checks to see if anything in queue1 is old enough to send. If it is,
it moves it off to queue2, where the second sendmail will deal with it.
Anything obviously wrong with this idea?
Hello, I setup on VPS many mailman lists and on info page of all the public
mailing lists on ”Description” I see wrong russian encoding like ”ðÒÅÓÓ
ÃÅÎÔÒ”, there you can see error http://list.ournet.biz/cgi-bin/mailman/
listinfo, can you consult? Thank you.
We recently set up an announcement mailing list (MM 2.1.18) for a local
music non-profit organization for which my wife is the treasurer, and at
this point the sole authorized (un-moderated) poster to the list.
She wants to be able to post completely anonymously, and so we've set
the list up as an anonymous list, with the Reply-To address of the
MM duly posted her first post to the list, and all the required headers
are fine and as expected, but her original post to the list had the
Organization header set to the name of her bookkeeping business, and
this was preserved in the distributed announcement.
Is there, and if not, shouldn't there be a way to _completely_ anonymize
a post to a list? There should be some way to have MM remove the
Organization header and replace it with an arbitrary one, in this case
the name of the organization on behalf of which the announcement was
Granted, she could set up a special account, w.o. an organization name
for posting to the list, or temporarily remove this from her account
profile, but she may have others posting to this list as well, and there
needs to be some way of dealing with this on a general basis.
Lindsay Haisley | "Everything works if you let it"
FMP Computer Services |
512-259-1190 | --- The Roadie
If in mailman server configuration file mm_cfg.py we turn off the sending monthly password reminders below,
DEFAULT_SEND_REMINDERS = No
but the setting " Send monthly password reminders?" for one mailman mailing list is set to "Yes", Can each subscriber of this list receive a monthly email reminder of what mailman lists they were subscribed to and the password for this list?
Carl Xie (Wei Xie)
I'm on to the next layer of the onion for my migration. Now I have
admin/moderator requests to handle. When I click the appropriate radio
buttons and click the submit button, nothing happens. The page refreshes
but the requests remain. TIA.