Re: [exim] Stopping Bounces being generated...

Góra strony
Delete this message
Reply to this message
Autor: Dave Lugo
Data:  
Dla: exim-users
Temat: Re: [exim] Stopping Bounces being generated...
On Wed, 8 Dec 2010, Chris Russell wrote:
>
> Hi All,
>
> RFC, best practise etc etc aside for one moment, is there a way to stop
> exim generating bounce messages for a particular domain ?
>
> We do backup MX for a couple of customers, who have their own Anti-Spam
> solution - using callouts (recipient verification), this works well
> until their Anti-Spam appliance generates a bounce after SMTP DATA (and
> actually in some RCPT TO instances) - in which case we then generate the
> bounce:
>
> Ie:
>
> 2010-12-08 11:38:45 1PQIEA-0002tR-N2 ** user@??? R=dnslookup T=remote_smtp: SMTP error from remote mail server after RCPT TO:<user@???>: host spam appliance [1.1.1.1]: 550 5.5.0 <user@???>... no such recipient - user@???
> 2010-12-08 11:38:45 1PQIM9-0004Jz-5F <= <> R=1PQIEA-0002tR-N2 U=exim P=local S=8369
>
> And
>
> 2010-12-08 09:21:50 1PQGDc-0000Jm-3j ** user2@??? R=dnslookup T=remote_smtp: SMTP error from remote mail server after end of data: host otherspamappliance [2.2.2.2]: 554 rejected due to spam content
> 2010-12-08 09:21:50 1PQGDe-0000OB-0a <= <> R=1PQGDc-0000Jm-3j U=exim P=local S=4609
> 2010-12-08 09:21:50 1PQGDc-0000Jm-3j Completed
>
> I agree with comments related to: don't this is, against RFC's etc etc
> however this causing issues with various blacklists.. and the customer
> is adamant they wish to continue this.
>
> So the question is, is there any option in the routers to stop bounces being generated ?
>
> Thanks
>
> Chris
>



You could do an smtp call forward for rcpt verification
in your rcpt acl, and at least reject (if the customer
rejects after rcpt_to) those items during the original
smtp session, instead of having a bounce to deal with.


-- 
--------------------------------------------------------
  Dave Lugo     dlugo@???      No spam, thanks.
  Are you the police?  . . .  No ma'am, we're sysadmins.
--------------------------------------------------------