Saxon Jones writes:
« HTML content follows »
This is more of a rhetorical question than anything, but would it not be
simple to remove the requirement for etc/hosteddomains (and etc/locals and
etc/acceptmailfor) and reject messages based upon whether the authdaemon
lookup returns an account or not?
That's fine if most of your mail traffic is incoming. But for busy mail
servers that also handle outbound traffic this will now result in placing
additional load on the database back end.
Somewhat related to this would be that I’d like to symlink the
esmtpacceptmailfor.dat and the aforementioned config files to a copy on an
NFS share. Is this going to break if the server they’re created on is
UltraSPARC and the MX’s are Intel? Is simply having the same version of
BDB installed sufficient to make this work?
This question would better be directed to a BDB mailing list. Sparcs are
big-endians, Intels are little-endians. My guess would be that BDB is
robust enough to automatically handle endian-ness conversion.
pgp00000.pgp
Description: PGP signature
