ROGERS Richard schrieb: [...]
If anyone has better suggestions, I'd like to hear them. Please don't just tell me that sending OoO off site is a Really Bad Idea (TM) - I already know that!
Don't worry, it could be worse.Exchange 2003 and 2007 won't respond with an OoO for every incoming message. Exchange 2003 won't respond if there is a header like "Precedence: junk" or "Precedence: bulk", Exchange 2007 respects some additional headers like "X-Auto-Response-Suppress: OOF". It's all in their knowledge-base, so kick your Exchange-admin if he doesn't know about it.
Anyway, if your gateway can detect spam it can mark each message in a way that prevents Exchnge from sending OoO. Here we use exim to mark each message with a spam-value which is used to route messages in an Exchange-Junk-folder and make sure there is a Precedence-Header to avoid OoO.
Of course you can use other conditions to have exim decide wheter or not Exchange should send OoO.
-- CU, Patrick.
smime.p7s
Description: S/MIME Cryptographic Signature
-- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
