Is outbound scanning limited to per-domain rules (using the folder/subfolder method) or can per-user config files placed within the domain folders still be used?
Outbound scanning settings are systemwide, except that you can have per-domain or per-user settings for the *recipient's* domain.
So you could have per-domain settings that would apply to all E-mail sent to @hotmail.com, or you could have per-user settings that would apply to all E-mail sent to [EMAIL PROTECTED] But it is not possible to have per-user or per-domain configurations based on the return address for outgoing E-mail.
1. Provide a secondary MX record/server for increased reliability of our mail server
For this to work for #1, we need to be able to continue to run our per-domain, and per-user configuration rules. As far as our clients are concerned, we want the offload to a new server to be transparent to them.
This will work. Even though the E-mail is on a gatewayed domain and isn't stored on the secondary server, Declude JunkMail will still use the per-domain and per-user configurations.
Assuming we can do per-user using the folder/username config files, it sure would be nice if we could use the newer junkmail config file with the REDIRECT keywords to move our existing configurations right over.
The REDIRECT keyword should work fine in this situation. :) -Scott
--- [This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
--- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
