On Tue, 17 Oct 2000, Drew Skinner wrote:
> I've adjusted my delay_warning to be much lower for the initial warning & I
> think that will take care of the sender. You almost need to have context
> sensitive warning messages (shudder).
I have to confess to wanting context (or reason) senstive warning *times*
for exactly this purpose. I don't want senders to get normal delay
warnings until after quite a few hours, but for deferrels due to quotas,
I'd like the warning to go out right away.
But I'm far from sure whether the additional complication in both code and
configuration would be worth it for that feature.
> My suggestion here would be simply to have a setting in Local/Makefile for the
> location of the vacation program. vacation=/usr/bin/vacation (or wherever).
>
> With this info it would be very simple to build an option such as :vacation:
> which would simply pipe to vacation the specified file. Granted it's frivolous,
> but the request came from end users who thought it would be easier -
> IMO it does
> make the syntax simpler _for them_.
First of all, the vacation progem is not nearly as loop-proof as a typical
Exim filter/autoresponder.
Wouldn't it be easier for everyone to just have an autoresponder director
that used require_file = /home/${local_part}/vacation.msg and unseen.
So all users would have to do is create a file vacation.msg (or whatever)
and the right thing would happen.
-j
--
Jeffrey Goldberg
I have recently moved, see
http://www.goldmark.org/jeff/contact.html
Relativism is the triumph of authority over truth, convention over justice
