Yes, you just return the 550 error code in response to the RCPT command.
At that point, its up to the sending server/client software to handle the
550. I've seen a bunch of freeware PC clients that just give up on the
first 550, even if there are other valid RCPT's. Any reasonable piece of
software, would report the error back to the sending user.
Sent by: duval.rick@???
To: Dan_Mitton@???
cc: "exim users" <exim-users@???>
Subject: Re: [exim] How to not reply to bad mail
LSN: Not Relevant
User Filed as: Not a Record
Ok, I think I was mistaken in where the denial message was actually
generated.
If I understand you guys correctly, my server give the 550 to the
delivering server and if it's a spammer hes just going to ignore it
and move on. If its a legitimate email server THAT server is the one
generating the email back to ITS sender notifying them of the error.
Is that right?
On Thu, Nov 20, 2008 at 5:55 PM, <Dan_Mitton@???> wrote:
> Where are your accept and deny statements? If they are in the RCPT ACL,
> that should return a 550 error code for each failed recipient, rather
then
> accepting the email and generating bounce messages from within a router.
>
>
>
> Sent by: exim-users-bounces@???
> To: "exim users" <exim-users@???>
> cc: (bcc: Dan Mitton/YD/RWDOE)
> Subject: Re: [exim] How to not reply to bad mail
> LSN: Not Relevant
> User Filed as: Not a Record
>
> But my server gets thousands of messages to non-existent local_parts
> and some spammers send them all from some poor guys address (I know
> I've been on the victim side of that where someone is spamming and
> using my address in the from header).
>
> I'm not only concerned that I'll be flooding that server with rejected
> emails but also that my server could end up blacklisted because of the
> potential flood of replies generated.
>
> Rick
>
> On Thu, Nov 20, 2008 at 5:44 PM, Kjetil Torgrim Homme
> <kjetilho@???> wrote:
>> On Thu, 2008-11-20 at 17:24 -0500, Rick Duval wrote:
>>> I now have a lookup that accepts emails only for addresses that are in
>>> the database.
>>>
>>> accept condition = ${lookup mysql{SELECT count(*) from addresses \
>>> WHERE active AND domain='${quote_mysql:$domain}'
> \
>>> AND local_part='${quote_mysql:$local_part}'}}
>>>
>>> deny
>>>
>>> It works great but I don't want to contribute to backscatter by
>>> sending denial messages back to the sender everytime an address is
>>> rejected. Right now it sends out and email like:
>>>
>>> SMTP error from remote mail server after RCPT TO:<bob@???>:
>>> host duvals.ca [74.51.38.171]: 550 5.1.1 <bob@???>:
>>> Recipient address rejected: User unknown in virtual alias table
>>>
>>> Can I turn that off and just not have it reply at all?
>>
>> well, you can blackhole the message, but your current method is the
>> recommended way of setting it up. if someone mistypes an address, say
>> "bpb@???", you will typically want him to know about it so that
he
>> can resend it using the correct address.
>>
>> you won't be contributing to backscatter unless someone forwards e-mail
>> to you -- and typoes in forwarding targets should definitely be
>> reported.
>>
>> it's a bit different if your denial is due to a SpamAssassin score or
>> something like that -- then the forwarding system may have more lax
spam
>> filtering than your system, but it's the forwarding's system which will
>> be spreading backscatter. even here, it's not really your fault.
>>
>> --
>> regards, | Redpill _
>> Kjetil T. Homme | Linpro (_)
>>
>>
>> --
>> This message has been scanned for
>> viruses and dangerous content by
>> Accurate Anti-Spam Technologies
>> and is believed to be clean.
>>
>>
>
> --
> ## List details at http://lists.exim.org/mailman/listinfo/exim-users
> ## Exim details at http://www.exim.org/
> ## Please use the Wiki with this list - http://wiki.exim.org/
>
>
>
>
> --
> This message has been scanned for
> viruses and dangerous content by
> Accurate Anti-Spam Technologies
> and is believed to be clean.
>
>
