On Tue, 4 Sep 2001, Alan J. Flavell wrote:
> A sender (usually, but not always, a spammer) gets one of these kind
> of responses from us (suitably anonymised):
>
> 2001-09-04 11:55:19 15eDrS-0006Nm-00 rejected from where.ev.er
> (wotsit) [192.168.66.6]: temporarily unable to verify sender address
> <spammer@???> (try later)
>
> The sender then responds to this by sending the message to our
> secondary MX instead - and that server then spends the next few days
> hassling us in good faith to accept the message.
The only "right" way round this problem is to have both primary and
secondary MTAs running the same incoming control policies.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
