John Jetmore wrote: > it appears that all retry rules are based on destination
> addresses/domains. Is there any way to create transport-specific
> retries? I have a couple of transports that have many domains routed to
> them. I'd like them to have very low retry times while the standard
> transports/routers have the normal retry time, w/o having to add a new
> rule everytime I add a new domain. It doesn't look like this is possible
> from the look I had at spec.txt, but I wanted to confirm.
I'm not sure (never really fiddled with retry-rules) but IIRC you can
use a domainlist as a match.
<quote>
The pattern is any single item that may appear in an address list (see
section 10.12). It is in fact processed as a single-item address list,
which means that it is expanded before being tested against the address
which has been delayed. Address list processing treats a plain domain
name as if it were preceded by '*@', which makes it possible for many
retry rules to start with just a domain. For example,
</quote>
