I've blocked OoO messages from leaving our network, so this isn't a
problem for us. In this day and age, I was able to convince the CIO's
that proliferating SPAM by providing confirmation of valid email
addresses via automatic replies to the internet was going to cause their
users more problems than the small convenience of the OoO replies.

It's a sign of the times, I suppose, that in Exchange 5.5 we enabled
automatic replies to the internet, but by the time we got around to
installing Exchange 2003 we did not.

-- 
Larry Wahlers
Concordia Technologies
The Lutheran Church - Missouri Synod
mailto:[EMAIL PROTECTED]
direct office line: (314) 996-1876




> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of 
> [EMAIL PROTECTED]
> Sent: Tuesday, September 26, 2006 10:33 PM
> To: [email protected]
> Subject: [ActiveDir] blocking OOO in the listserv?
> 
> Wouldn't it be more reliable to configure the listserv to 
> automatically
> drop such e-mails?  Then you're not dependent on hundreds or 
> thousands of
> mail servers all being correctly configured (which seems 
> unlikely to me).
> 
> I would think that most OOO messages are flagged as such 
> using some SMTP 
> header, and/or can be flagged fairly reliably with a regular 
> expression.
> (e.g., grep -i "out.*of.*office" should catch 90% or more of them)
> 
> 
> -- 
> Idan Shoham
> Chief Technology Officer
> M-Tech Information Technology, Inc.
> [EMAIL PROTECTED]
> http://mtechIT.com
> 
> On Mon, 25 Sep 2006, Derek Harris wrote:
> 
> > There have been some good threads on the Exchange List 
> about ways to NOT
> > send OOOs to listservers:
> > http://intm-dl.sparklist.com/read/?forum=exchange
> >
> -snip-
> List info   : http://www.activedir.org/List.aspx
> List FAQ    : http://www.activedir.org/ListFAQ.aspx
> List archive: http://www.activedir.org/ml/threads.aspx
> 
List info   : http://www.activedir.org/List.aspx
List FAQ    : http://www.activedir.org/ListFAQ.aspx
List archive: http://www.activedir.org/ml/threads.aspx

Reply via email to