[Mailman-Users] sending message
claw at kanga.nu
claw at kanga.nu
Fri Dec 3 02:47:58 CET 1999
On Thu, 02 Dec 1999 15:56:12 -0700
Kory Wheatley <wheakory at isu.edu> wrote:
> Why does mailman queue a message that's undeliverable and try to
> send it again later on in the Cron run_queue process.
Mailman has no particular way of determining that a message is
undeliverable outside of the very small case where the local MTA
refuses it prior to receipt for having a malformed address or
similar.
> Why doesn't it just send the message and if the user doesn't exist
> or is undeliverable not send it again later on just delete it.
The pattern is:
MailMan sends the message.
An MTA (somewhere) responds with a DSN.
MailMan attempts to parse and handle the DSN.
MailMan can't have advance intelligence here. Additionally it can't
assume that a message that didn't make it thru last time, won't make
it thru this time.
> I have configured the web interface for it to disable or delete a
> user who I know is over is quota, because I get the bounce message
> back and it doesn't work.
MailMan dos not instantly unsubscribe bad addresses, but rather
waits for a consistent pattern to emerge for an address which it
then reacts to. This prevents MailMan from reacting to temporary
conditions such as a broken router, screwed remote mail system, or
other temporary failure.
> Minimum number of days an Address has been non-fatally bad before
> we take action 0 Minimum number of posts to the list since members
> first bounce before we consider removing 3 Action when critical or
> excessive bounces are detected Remove and notify me
It could also be that MailMan does not correctly handle the bounce
format for your MTA. I don't know as I don't use sendmail. Barry?
--
J C Lawrence Home: claw at kanga.nu
----------(*) Other: coder at kanga.nu
--=| A man is as sane as he is dangerous to his environment |=--
More information about the Mailman-Users
mailing list