You must setup your relay domains on your relay (secondary MX) server within Exim4U's domain administration function (logging in as siteadmin). For each relay domain you must specify the appropriate relay server address (to the primary MX host) within the domain administration function. Then, on the primary installation, add the relay server to /etc/exim/exim4U_backup_mx_host_names which will exempt mail relayed by the backup MX server from spam filtering and ratelimit checks (since the relay server will already have performed spam filtering). As far as I understood your message, one can do the spam filtering on
Hello, On Mon, Feb 14, 2011 at 04:54:44PM -0500, Gordon Dickens wrote: the backup-MX or/and on the primary MX. But if now spam filtering is done on the backup-MX how does the primary MX know about this? Doing no spam filtering at all for mails coming in through the backup-MX would be a problem, I think. If I decide to do spam-checking (spamassassin) only on the primary-MX and not on the relay, then I guess I should add the relay MX to the file etc/exim/exim4u_backup_mx_rl_host_names on the primary-MX host instead of /etc/exim/exim4u_backup_mx_host_names, right?
http://exim4u.org/svn/exim4u_src/trunk/NOTES - Refer to section 3 in the NOTES file. http://exim4u.org/svn/exim4u_src/trunk/etc/exim/exim4u_global_spam_virus - Refer to BACKUP MX SERVERS (OR RELAY SERVERS) CONFIGURATION NOTE. http://exim4u.org/svn/exim4u_src/trunk/etc/exim/exim4u_backup_mx_host_names http://exim4u.org/svn/exim4u_src/trunk/etc/exim/exim4u_backup_mx_rl_host_nam...
Note that Exim4U does not rely on DNS MX records for relaying mail from a relay host to its destination host. Instead, the destination host is specified in the Exim4U web interface in the Relay Server Address field in Domain Administration. Therefore, multiple relay hosts may be deployed along with the destination host and the MX records can all be set to the same value or any set of values for that matter but all mail will ultimately be delivered to the destination host. Exim4U is then used to specify whether spam processing, tagging and/or spam header rewriting is done by the relay host(s) or the destination host. These features also provide the capability for Exim4U installations to be used as spam filters for any other mail host. Is there also an easy way to rely on the DNS MX information? I simple setups it is more administrative work to keep up to date the primary MX both in DNS and in the exim4u database. Maybe one could introduce some keyword in the field for the primary-MX to indicate that exim should rely on DNS MX information? I would appreciate this.
Best regards, Udo