well this is much comforting, meaning that there is nothing to worry about
the configuration.. I turned on the "Should Mailman notify you, the list
owner, when bounces cause a member's subscription to be disabled?" to yes to
see what happens..
but still this does not answer the main question, what causes the existing
real members to be unsubscribed? is it because hotmail and yahoo are
rejecting the mail flow that needs to be controlled?
this leads to another question, should this (control mail flow) be
considered in the next version of mailman? this will also answer the million
dollars question: CAN mailman handle huge lists like those of TV stations
like mine (300,000 subscribers)?
final question: is there any advice about my current situation (hardware,
configuration...etc.)?
Thanks mate, you're the best :)
-----Original Message-----
From: Mark Sapiro
Sent: Sunday, January 23, 2011 8:21 PM
To: Khalil Abbas
Cc: mailman-users@python.org
Subject: Re: [Mailman-Users] control mail distribution ..
On 1/23/2011 7:46 AM, Khalil Abbas wrote:
attached are the Jan 16, and Jan 17th logs: error, smtp, qrunner,
locks.. I replaced my domain name with the word (DOMAIN) cause I believe
this is shown to public ..
there are several smtp-failure files (failure.1, .2, .3...) but they are
all empty (0 bytes size)..
The locks log shows one broken expired lock, possibly due to your
frequent reboots.
The error log shows only unparseable messages but there are over 3000 of
them in about 26 hours. Correlation with the qrunner log shows these are
all processed by BounceRunner. Thus they are unparseable messages sent
to the LIST-bounces addresses. Normally, unparseable messages are spam,
but possible they are real bounces from some broken MTA.
The next time you have an accumulation of
/var/spool/mailman/bounce/*.pck files, examine some of them with
Mailman's bin/dumpdb or bin/show_qfiles tool. If they look like
legitimate bounce messages, they may give you some information about
your bounces, but note that the particular messages that are unparseable
do not get scored for any user.
If they look like spam, then your problem may just be massive amounts of
spam sent to your LIST-bounces addresses.
--
Mark Sapiro <m...@msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
