On Thu, 29 Jun 2000, Nigel Metheringham wrote:
>
> allan@??? said:
> > In the case of spam, like the one below, the bounce back message goes
> > to a unknown user and that is why I don't want to send an email back
> > to them. I'd like that to work or...
>
> I think you are expecting that fail to be able to produce an SMTP time
> error code - which is the ideal way to do things. Unfortunately
> filters of any sort do not kick in until the delivery attempt - after
> the incoming SMTP transaction has completed.
>
> fail will cause a bounce message, to the original envelope sender
>
> > when it does send an email to the unknown user, this shows up in my
> > log and the message is frozen!! WHY??
>
> You have an undeliverable error reply - the docs say this is always
> frozen for the admin to deal with.
Unless of course you set ignore_errmsg_errors, which I always do. I
can't think of any case where I really care if an undeliverable
message notification can't be delivered.
For mail sent from outside our network, if the sender address is not
deliverable, it usually spam.. If not, then its some idiot with a
misconfiguration. Bouncing spam on the floo is a good thing, and its
not my problem if some moron on NT can't setup their stuff right..
For mail sent from within our network, almost all of the sender
addresses are validated at SMTP time (sender_verify, and the outgoing
server can do full verification on local parts in all local domains).
So I dont have too many undeliverable outgoing messages that cant be
returned to sender.
>
> You would do better to bit bucket the message - ie seen finish
>
> Nigel.
>
>
--
