None wrote:

Currently these are trying to deliver ndr's constantly to eg amm@dhl.com
and bounce@nds.fedex.com.

Why does your system generate DSNs?
And why aren't those delivered?

Maybe you could fix those problems instead of trying to work around
them and also affecting other mails?

Nice would be if such `external' messages would only be tried to
delivered two or 3 times. For messages that have to be delivered to the

And if there is a temporary problem you want the message to fail
after 3 tries?

You could use "Queue Groups" and change the retry times,
but the overall timeout is global -- though there are
some "suboptions", see doc/op/op.*, e.g.,

If the message has a normal
(default) precedence and it is a delivery status
notification (DSN), Timeout.queuereturn.dsn and
Timeout.queuewarn.dsn can be used to give an alter-
native warn and return time for DSNs.

--
Note: please read the netiquette before posting. I will almost never
reply to top-postings which include a full copy of the previous
article(s) at the end because it's annoying, shows that the poster
is too lazy to trim his article, and it's wasting the time of all readers.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)