Re: [exim] Using DEFER instead of DENY or DROP for spam

But you can specify a message when deferring. So a real user should
still see this message, or am I wrong?

For example, I defer messages where the HELO changed in the last 24
hours for the same IP. During my tests (telnet 25 tests), I got a "451
HELO changing from$acl_m7 to $sender_helo_name, mail temporarily
rejected.", so the real mail server should get this error message.

Do you mean mail servers don't handle properly messages with a 451
error?

On Mon, 27 Dec 2004 09:53:08 +0100
Giuliano Gavazzi <eximlists@???> wrote:

> this is indeed what I do. The real benefit is that a relatively
> simple script can be used to show what messages have been rejected
> multiple times (same pair sender/recipient), and (some) false
> positives will be amongst those.
> The main drawback is that you cannot let a genuine sender know that
> there are problems with they server, short of sending a report
> manually or automatically denying at the Nth attempt.
> It cannot be used at the DATA phase as the bandwidth cost is
> potentially high.
>