> My "solution" to the OOO getting to the list problem is to set the person
to
> NOPOST. I send them a messages explaining why and telling them to let me
> know when they return and I'll change them back, but generally they never
> say anything till then next time they try to post to the list.

Makes sense if the messages are going to the list, although the content
filters offered by Pete Weiss might prevent even the first one from getting
through!

We use reply to sender, so I've never seen an OOO notice through the list,
although I suppose if the autoresponder were configured to do a Reply All it
could happen. When I post, especially in the summer, I frequently see one or
two sent to my own reply address, but none of our frequent contributors has
ever found those bothersome enough to ask me to block them. Of course, the
only way I could do that is NOMAIL; the list doesn't see the OOO notice, so
I have to block the outbound trigger.

So far, the only cases where I've needed to do that are the ones that send
back to the Sender header address and hammer me with one OOO per post to the
list. (I think some better autoresponders have a
send-once-per-day-per-address provision, which I can generally live with.)

Hal