Chris Bartram wrote:
It might be reasonable to suggest that no repeat messages get sent as long
as the "vacation" command/action is in effect. If it is changed/deleted-and-
added-back, then a new log is to be created
I tend to agree with Chris B. about oneshot vacation notices. At least
it allow side-stepping the issues he described. It seem to me that
having a vacation notice repeated at some interval is more a function of
the original sender's individual memory refresh rate (which may vary
from time to time :) than anything else.
Is there any strong arguments for having repeated vacation notices?
A nice touch would be if the originator's MUA understood the vacation
notice good enough to politely make a reminder during the vacation
period each time the sender tries to submit another message. I guess
it's only a dream of mine...
--
Hälsningar/Regards
Tomas Fasth <tomas(_dot_)fasth(_at_)twinspot(_dot_)net>
Tel: +46-13-218-181 Cel: +46-708-870-957 Fax: +46-708-870-258
EuroNetics Operation, Mjärdevi Science Park, 58330 Linköping, Sweden
(TwinSpot Network is a subsidiary of EuroNetics Operation)