I have written my own vacation program to fit in with some unusual
configs we have here. My question is this: What other considerations
in designing a good vacation program have I not thought of? I know
there are all sorts of ways a poorly implemented vacation program can
cause all sorts of nasty loops.
So far the only feature I have in place to prevent that is that it keeps
a flat text file containing the addresses to which it has already sent
it's vacation message. Subsequent messages from the same sender are
safely stored in the Maildir but not replied to.
Any thoughts/recommendations? Should I be looking for any special
headers or similar thoughts?
Ben
--
Ben Beuchler [EMAIL PROTECTED]
MAILER-DAEMON (612) 321-9290 x101
Bitstream Underground www.bitstream.net
