Jason Bertoch a écrit : > On 1/18/2010 6:38 PM, mouss wrote: >> David B Funk a écrit : >>> On Wed, 13 Jan 2010, Jason Bertoch wrote: >>> >>>> Can a list admin disable the spamassas...@hundredacrewood.willspc.net >>>> account as we're still getting bounces? >>>> >>>> >>>> -------- Original Message -------- >>>> Subject: Delivery Status Notification (Failure) >>>> Date: Wed, 13 Jan 2010 09:36:54 -0500 >>>> From: Administrator <administra...@willspc.net> >>>> To: Jason Bertoch <ja...@i6ix.com> >>>> >>>> Subject: Re: SA not picking up rules from /var/lib/spamassassin/ >>>> Sent: Wed, 13 Jan 2010 09:36:54 -0500 >>>> >>>> did not reach the following recipient(s): >>> [snip..] >>> >> >> As far as I can tell, the major open source MTAs implement access >> control. so you don't really need calling SA for this. >> > > This is an list administration problem, not something that every poster > here should have to fix locally.
Unfortunately, that's only partially true. - if the problem is at the "MTA" side, then it will show again and again, with many different subscribers. In this case, the MTA operator should fix the problem. and if this doesn't happen, then he should be considered as part of the problem: blacklist the operator. - if the problem is in the user config, then yes, unsubscribing him will help, until he subscribes again (possibly with a new address). That said, I agree that the user should be unsusbcribed. But that's not always easy: the bounce doesn't necessary tell the subscriber (when mail is forwarded, you get the bounce for the forwarded-to address...). and VERP doesn't help here since the borked setup sends the bounce to the From: header. (one solution is to send mail with a "VERP FROM:" header to detect which one causes the bounce)... sigh!
