I find I am being removed from mailman mailing lists left and right. I believe
the default values for the bounce removal should be reconsidered. It's
possible that you haven't had many users in my situation and so haven't really
had a chance to tune these parameters on the low end yet. But they clearly
aren't working for me at a few sites.
My particular situation is that my site has seen fit to filter viruses by
refusing delivery. This causes a bounce from the remote MTA every time someone
sends me an Outlook virus. Why my site administrators felt this was necessary
is a question for another day, it's not like I use Outlook or like my spam
filters wouldn't have thrown these messages away anyways, but whatever.
The net result is that some small fraction of messages to me bounce and list
management software notices this. The only reason I became aware of the
problem was because ezmlm also does this type of processing but it sends a
warning message before removing users. It only removes you if the warning
message itself bounces. In fact it sends two such warning messages and only
removes the user if *both* bounce. This provides the user with a chance to
react to the first message and fix the problem -- if they ever see the
I could beg for a similar feature in mailman, but I'm not sure it's necessary.
But I am sure it's necessary to tune the bounce processing parameters. The
relatively few bounces I'm generating shouldn't be causing me to get removed
when all the real messages are being delivered fine.
It seems the legitimate messages that are correctly delivered should reset the
count of bounces to 0. Reading the source it seems it has to see
DEFAULT_MAX_POSTS_BETWEEN_BOUNCES such legitimate posts between messages. I'm
fairly convinced this parameter should always be 0. If any successful delivery
occurs the user should never be removed due to bounces.
What I don't understand is how DEFAULT_MAX_POSTS_BETWEEN_BOUNCES relates to
the parameters I see in the admin. None of the parameters in the admin
corresponds to this. How is it calculated?
After power was restored and the machine came up, Mailman (2.1.2) is now
spitting out errors:
Traceback (most recent call last):
File "/usr/local/mailman/bin/qrunner", line 270, in ?
File "/usr/local/mailman/bin/qrunner", line 230, in main
File "/usr/local/mailman/Mailman/Queue/Runner.py", line 59, in run
filecnt = self._oneloop()
File "/usr/local/mailman/Mailman/Queue/Runner.py", line 88, in _oneloop
msg, msgdata = self._switchboard.dequeue(filebase)
File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 144, in dequeue
data = self._ext_read(dbfile)
File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 246, in _ext_read
dict = marshal.load(fp)
ValueError: bad marshal data
Any suggestions? Worked fine before power got yanked...
Things have been a bit busy, but I've finally moved to v2.1.* and Exim4,
and in the process have had to adapt my setup for fronting Mailman lists
with TMDA and an external optional/controllable MIME processor
(MimeFilter, can be turned off on a per-message basis by a custom
If there's sufficient interest I'll update the HOWTO with the details.
There's nothing really hard in the deal, just an excess of details.
ObNote: If you don't know what I'm talking about, please see the
UserFAQ and the archives of this list for definitions, implementation
details and implications, and prior discussion of same.
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).
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.
Does anyone know if there is a patch to strip an attachment from list mail, save it to disk (in the web directory), and insert a URL to the file in it's place with Mailman 2.x? If not, some clues on where this might fit in would be appreciated (I would be willing to look at coding it).
(see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=204196 for the
Debian bug report)
There's an error in the dutch translation where the keyword used is
the wrong one. This causes Mailman to shunt large (> 40KB by default)
mails on Dutch mailing lists.
@@ -7406,7 +7406,7 @@
"%(kb)d KB in size."
"Uw bericht was te groot.Het mag maar\n"
-"%(limit)d KB groot zijn."
+"%(kb)d KB groot zijn."
msgid "Posting to a moderated newsgroup"
Tollef Fog Heen ,''`.
UNIX is user friendly, it's just picky about who its friends are : :' :
> --- NEW FILE: README.txt ---
> This is a very rough work in progress. All Mailman 3.x work will
> occur in this directory under the top level CVS repository. Because I
> intend to reorganize the source tree, I think it's just better to
> start fresh. This does however mean that for anything we copy over
> (and hopefully that will be a good bit of code), we'll lose the CVS
> history for it.
It might be a bit of extra work, but why not just copy the files around in
the repository? History is important! :-)
linux.conf.au 2004: Adelaide, Australia http://lca2004.linux.org.au/
"Ah, now we see the violence inherent in the system." - From Monty
Python to ESR, by way of Al Viro
Has anyone created a script they'd like to share that kills off the sobig
stuff sitting on hold?
I'll make one but if there's one already out there, it'd save me some time.
I'm leaving on vacation Friday night. Lots to do 'till then...
Democracy is two wolves and a lamb voting on what to have for
lunch. Liberty is a well-armed lamb contesting the vote.
In the mailinglist I use the subscribers only can read the postings of the admins and moderators.
The only functionality the subscribers should have is subscribing and unsubscribing from the list by mail.
e.g. mailing-subscribe(a)domain.xx and mailing-unsubscribe(a)domain.xx
That's all ok, but for that use only my subscribers obtain to much information and get confused when they subscribe now.
because the got a mail like this:
<start of mail>
Mailing list subscription confirmation notice for mailing list
We have received a request from 18.104.22.168 for subscription of
your email address, "jochen(a)d-mission.be", to the
mailman-developers(a)python.org mailing list. To confirm that you want
to be added to this mailing list, simply reply to this message,
keeping the Subject: header intact. Or visit this web page:
Or include the following line -- and only the following line -- in a
message to mailman-developers-request(a)python.org:
Note that simply sending a `reply' to this message should work from
most mail readers, since that usually leaves the Subject: line in the
right form (additional "Re:" text in the Subject: is okay).
If you do not wish to be subscribed from this list, please simply
disregard this message. If you think you are being maliciously
subscribed to the list, or have any other questions, send them to
<end of mail>
Instead I should prefer that they only get a mail where they can read that they should confirm by replying with an empty mail, not by logging in etc.
idem dito for the welcome mail with all the urls. They're useless and only confusing for my subscribers.
Is there a way to change this?
I allready tried with the welcome_msg function but that doesn't replace the original text.
Sorry to bother the developers with this but I tried the users list
of couple of times to no avail. Plus, it almost seem like there a
bug or an incombatibility with something somewhere...
I've just upgraded from Mailman 2.0.x to 2.1.2 using Python 2.2.2 on
a Solaris 8 box.
The "qrunner --runner=OutgoingRunner:0:1 -s" process starts okay and
stays okay to send one message (either confirmation or post) and
than is just hangs. It does not die but doesn't send anything else.
After that one message, even a "mailmanctl stop" won't stop it. I
have to manually kill -9 it. And outgoing stuff just accumulates in
I'm not sure what to do or where to look. I looked in all the logs
and tried running it by hand. Same result. I even tried to truss it
to see if I could find something.
Charles Gagnon | My views are my views and they
http://unixrealm.com | do not represent those of anybody
charlesg at unixrealm.com | but me.
640K ought to be enough for anybody.
-- Bill Gates, 1981
Lately I've been getting a lot of spam to many of the lists that I
While reading an article about spam-prevention it hit me that one way to
easily cut down on spam on an open list, would be to have mailman send out a
confirmation message for non-member posts. If the sender confirms then,
address gets added to the accept_these_nonmembers, if not the message gets
dropped after some time and the adress perhaps added to
I think there should perhaps be a way to tell mailman that the From: address
was forged, so forget the whole deal...