In a previous post, I figured out that we are getting bounced messages back, that are sent out by the out of office auto responder. After much time, I figured out that the issue was because Exchange 2010 (or 2007) sends out the OOO message with a header of "Return-Path: <>". Spam filters seen the null return path, assume it's spam, and bounce the message.
I know that this is by design, and that Exchange 2010 sending out the OOO message with a null return-path is in compliance with RFC's, etc, etc. However, my issue is that my company demand that Out of office messages reach the client. (For the record, I'm against sending OOO to the 'net, but I was overruled.) Now, I've found on the 'net that at least one person managed to figure out how to write a custom transport rule that overrode this setting so that Exchange would send it out with a return path of "admin@example.com" rather then the null. S/he didn't give any details on how they accomplished it though. So, I'm looking for help to try and figure out how to customize a transport rule to override this setting.
Thanks in advance.
I know that this is by design, and that Exchange 2010 sending out the OOO message with a null return-path is in compliance with RFC's, etc, etc. However, my issue is that my company demand that Out of office messages reach the client. (For the record, I'm against sending OOO to the 'net, but I was overruled.) Now, I've found on the 'net that at least one person managed to figure out how to write a custom transport rule that overrode this setting so that Exchange would send it out with a return path of "admin@example.com" rather then the null. S/he didn't give any details on how they accomplished it though. So, I'm looking for help to try and figure out how to customize a transport rule to override this setting.
Thanks in advance.
