Has anyone developed any wisdom on how to setup James as a secondary mail
server? In this specific content, define this as one that is a primary for
a set of domains, but acts as a relay for another set of domains, receiving
and queueing e-mails until the other primary is available again.
The behaviors would be:
- mail intended for local user
- mail intended for a known primary
- mail intended for remote address
The salient difference is that we can't apply the anti-relay filter before
spooling for the domains we're backing up.
Since I don't need or want the other primary to handle my outgoing e-mail,
the gateway configuration doesn't seem appropriate.
Is it sufficient to insert
<mailet matcher="HostIs=<list of domains we backup>" class="ToProcessor">
<processor> relay </processor>
</mailet>
somewhere before the anti-relay portion of the transport processor?
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
