Re: [Exim] Dealing with a broken destination server.

Αρχική Σελίδα
Delete this message
Reply to this message
Συντάκτης: David S. Madole
Ημερομηνία:  
Προς: Lists, exim-users
Αντικείμενο: Re: [Exim] Dealing with a broken destination server.
> From: "Lists" <sfulton-lists@???> wrote:
>
> I have a situation in which a client is using a custom anti-spam
> solution. Unfortunately they have not bothered to read RFC 2821, and
> after the message is sent, their servers returns a 451 (temporary
> error), which causes Exim to continue to try sending the message later.
> The client has made it clear that this behavior will not be changing
> ("because everyone else does it" amongst other explainations). I have
> two questions:


Have _you_ made it clear that they will no longer be receiving mail from you
("because everyone else does it")?

Why do they think this is better than 5xx?


> 1. Is it possible to force Exim, in the instance of this host, to view
> a 451 error as permanent and drop the message after sending?


Not that I know of.

The closest thing I can think of is a retry rule for the domain that matches
timeout & refused with a reasonable retry values followed by a retry rule
for the same domain matching everything else with a cutoff time of zero.


> 2. Can I force mail for a single destination host to be queued until I
> manually initiate a queue runner for that mail?


It's domain- not host-based, but I think you might look at hold_domains:

http://www.exim.org/exim-html-4.30/doc/html/spec_14.html#IX1122

If I've misunderstood you, maybe queue_smtp_domains or queue_domains would
work better:

http://www.exim.org/exim-html-4.30/doc/html/spec_14.html#IX1251
http://www.exim.org/exim-html-4.30/doc/html/spec_14.html#IX1229

David