In our current smail setup, mailbagging works like "magic". That is, we
can add any domain we want to use our servers as secondary MX and we don't
have to make any configuration changes. The similar thing in exim seems
to be using the relay_domains_include_local_mx option, but that doesn't
give us quite the flexibility that we had under smail (never thought I'd
say that =)).
under smail:
visible_name = real-machine-name.domain.com
hostname = real-machine-name.domain.com:\
mail1.domain.com
by having a separate 'visible_name' field, the machine name in the 220
header is the real machine. Because mail1.domain.com is included in
hostname, any domain that lists mail.domain.com as an MX record will be
bagged on this machine.
The reason we do this is so we can move the IP addresses of our mail
baggers around from machine to machine as needed and not have to worry
about making DNS changes, as we would have to using exim. The other
alternative is using a list of domains we bag for, which is impractical
because we've been using mail1 and mail2 as baggers for 6 years now. I
don't think there's anyway we could make a comprehensive list of everyone
that uses them.
Is there anyway to get this ability to differentiate between the visible
hostname and a hostname list in exim? I'm working on a fairly massive
migration plan and so far this is the only thing I've found that smail can
do and exim can't (that we use, anyway. our last uucp customer canceled a
year ago or so =)).
Thank you for any help or comments.
--John
