
hi there... wondering if fake email addresses in a mailman list can get cleaned up with the bounces options. just testing with one and the mail log says (correctly) it could not resolve the host. is this considered a hard bounce by mailman?! i have enabled the bounce processing, the maximum bounce score is 1.0, the bounce_you_are_disabled_warnings are set to 0 expecting immediate removal. now that i sent a couple of test messages out that fake address is still in the members list. what needs to happened?
thanks..

kalin m wrote:
Is it considered a hard bounce by your MTA? I.e. is it a 5xx or a 4xx status. That's what determines whether Mailman consideres it a bounce or not.
Your MTA needs to return a 5xx for the recipient to Mailman during SMTP or to send a 5xx DSN to listname-bounces.
Is the message still queued and being retried in the MTA, or is it still being retried by Mailman?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

so if it's not 5xx it's not a bad email? i see dsn=4.0.0. that's not enough?
i'm assuming it's retried by the mta. the settings in mailman clearly state that it should be discarded right away...
bounce settings:
bounce_score_threshold = 1.0 bounce_info_stale_after = 10 bounce_you_are_disabled_warnings = 0 bounce_you_are_disabled_warnings_interval = 0
not sure about the bounce_info_stale_after. the way i interpret this is that the bounce information will be kept for about 10 days in case the score rises. if i put this down to zero the score will start clean every day. is that correct? or is this the reason for the repeated log entries
- lots of to=<vvv@zzzzzz.com> attempts...
here, from the maillog: to=<vvv@zzzzzz.com>, delay=03:42:23, xdelay=00:00:00, mailer=esmtp, pri=785918, relay=zzzzzz.com., dsn=4.0.0, stat=Deferred: Name server: zzzzzz.com.: host name lookup failure
thanks...
Mark Sapiro wrote:

kalin m wrote:
so if it's not 5xx it's not a bad email? i see dsn=4.0.0. that's not enough?
In SMTP 4.y.z DSNs are "temporary" errors. They could be caused by a spam filter over loaded, or the system shutting down, or...
i'm assuming it's retried by the mta. the settings in mailman clearly state that it should be discarded right away...
The 4.y.z should be seen as an invitation for the SMTP server to try sending the message again at a later time.
The MTA will eventually time out the message and generate a permanent error.
Grant. . . .

Grant Taylor wrote:
Or, if the MTA returns the 4xx status directly to Mailman during SMTP, Mailman will retry the send every DELIVERY_RETRY_WAIT (default 1 hour) for DELIVERY_RETRY_PERIOD (default 5 days), but in this case, mailman will eventually give up but not record a bounce.
If this is the case and you want Mailman to record a bounce, you have to arrange for your MTA to return a 5xx status for an invalid recipient domain.
So the first question is where is the message. Is it queued in the MTA, or is it in Mailman's retry queue. If it's queued in the MTA, as Grant says, the MTA will eventually time out on this message and return a hard bounce to Mailman. If it is queued in Mailman, mailman will eventually give up and no bounce will be recorded.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

kalin m wrote:
Is it considered a hard bounce by your MTA? I.e. is it a 5xx or a 4xx status. That's what determines whether Mailman consideres it a bounce or not.
Your MTA needs to return a 5xx for the recipient to Mailman during SMTP or to send a 5xx DSN to listname-bounces.
Is the message still queued and being retried in the MTA, or is it still being retried by Mailman?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

so if it's not 5xx it's not a bad email? i see dsn=4.0.0. that's not enough?
i'm assuming it's retried by the mta. the settings in mailman clearly state that it should be discarded right away...
bounce settings:
bounce_score_threshold = 1.0 bounce_info_stale_after = 10 bounce_you_are_disabled_warnings = 0 bounce_you_are_disabled_warnings_interval = 0
not sure about the bounce_info_stale_after. the way i interpret this is that the bounce information will be kept for about 10 days in case the score rises. if i put this down to zero the score will start clean every day. is that correct? or is this the reason for the repeated log entries
- lots of to=<vvv@zzzzzz.com> attempts...
here, from the maillog: to=<vvv@zzzzzz.com>, delay=03:42:23, xdelay=00:00:00, mailer=esmtp, pri=785918, relay=zzzzzz.com., dsn=4.0.0, stat=Deferred: Name server: zzzzzz.com.: host name lookup failure
thanks...
Mark Sapiro wrote:

kalin m wrote:
so if it's not 5xx it's not a bad email? i see dsn=4.0.0. that's not enough?
In SMTP 4.y.z DSNs are "temporary" errors. They could be caused by a spam filter over loaded, or the system shutting down, or...
i'm assuming it's retried by the mta. the settings in mailman clearly state that it should be discarded right away...
The 4.y.z should be seen as an invitation for the SMTP server to try sending the message again at a later time.
The MTA will eventually time out the message and generate a permanent error.
Grant. . . .

Grant Taylor wrote:
Or, if the MTA returns the 4xx status directly to Mailman during SMTP, Mailman will retry the send every DELIVERY_RETRY_WAIT (default 1 hour) for DELIVERY_RETRY_PERIOD (default 5 days), but in this case, mailman will eventually give up but not record a bounce.
If this is the case and you want Mailman to record a bounce, you have to arrange for your MTA to return a 5xx status for an invalid recipient domain.
So the first question is where is the message. Is it queued in the MTA, or is it in Mailman's retry queue. If it's queued in the MTA, as Grant says, the MTA will eventually time out on this message and return a hard bounce to Mailman. If it is queued in Mailman, mailman will eventually give up and no bounce will be recorded.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Grant Taylor
-
kalin m
-
Mark Sapiro