In article 18516.990142668@ma-1.rootsweb.com, Charlie Summers charlie@lofcom.com writes:
At 11:28 AM -0400 5/17/01, segura@attcanada.ca is rumored to have typed:
How can I filter out the "out-of office" replies?
I've found no real good way of handling brain-damaged "vacation" responses...I've taken he tact of IMMEDIATELY unsubscribing the person, and telling them with a canned response they will be welcomed back only when their "vacation" responder properly discriminates against mailing lists...but that's primarily because I haven't come up with a better system.
I'd be _really_ interested in hearing how other folks on the list handle these annoying things.
We updated rc.submit like so:
# # The following recipe makes sure that: # The mail has a sane size (i.e. it is not inordinately big) # It does not look like an administrative request. # It wasn't sent by this list itself. # It wasn't sent by a daemon (misdirected bounce message perhaps). #
:0 * < $size_limit * !$^($X_COMMAND:|X-Loop: $\listaddr) * !^Subject: Yahoo! Mail Auto-Reply * ! B ?? $^^$X_COMMAND: * $$daemon_bias * -100^0 ^FROM_MAILER|\ ^(((Resent-)?(From|Sender)|X-Envelope-From):|>?From )\ ([^>]*[^(.%@a-z0-9])?(\ LIST(SERV|proc)|NETSERV|bounce|autoanswer|echo|mirror\ |Out_Of_Office\ )(([^).!:a-z0-9][-_a-z0-9]*)?[%@> ][^<)]*((.*).*)?)?$([^>]|$)
Note the addition of the "Out_Of_Office" tag, which works well to catch that particular autoresponse.
We added some other recipes to rc.request, right after checking for "queue warnings" and before passing mail off to procbounce:
:0 AhD * ^Subject: Message status - opened * ^X-Mailer: Novell GroupWise /dev/null
:0 Ah * ^From: mailer-daemon@prodigy.net * ^Subject: Message Rejected$ /dev/null
:0 Ah * ^From: NTMail * ^Subject: Warning - delayed mail /dev/null
:0 Ah * ^From: .*@bigfoot.com * ^Subject: Autoresponse /dev/null
I haven't seen a problem with vacation messages or DSN notices in quite some time.