On Tue, Sep 15, 2009 at 09:15:42AM +0200, Andrew Lewis wrote:
> On Tue, 15 Sep 2009 08:50:14 +0200
> Heiko Schlittermann <hs@???> wrote:
>
> > But I guess, they really need to send bounce messages. If my smarthost
> > would deny sending bounces, I'd change the smarthost.
>
> I'm happy for them to send bounces but would rather they don't send lots of them to obviously forged addresses, and that they know when their bounces aren't going anywhere.
A suggestion...
(1) Make sure these people know that you view this as a problem, and are aware
of the action you intend to take (below).
(2) Rate-limit null-sender messages from their systems. For example, you
might allow up to "n" bounces per hour per customer. When the limit is
exceeded, defer.
(3) This will probably cause the bounce messages to build up on their servers;
only a trickle will be allowed out through yours.
(4) They will then have a motive for fixing their problem (i.e. they're
probably accepting-then-bouncing), because their queues fill up with bogus
bounces.
Regards,
--
Dave Evans
http://djce.org.uk/
http://djce.org.uk/pgpkey
