HylaFAX The world's
most advanced open source fax server
|
|
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
Re: [hylafax-users] Fw: Attached TIFF mail delivery
On 2004.05.24 15:38 Matt wrote:
On Fri, 21 May 2004 09:36:31 -0700
Lee Howard wrote:
> I am worried about how many possible WITH_THIS and WITH_THAT options
we
> could end up having, though, if we don't generalize some. And, at
that
> point, isn't it easier just to tell the administrator to hack
faxrcvd
> directly?
>
> Maybe it would be easier to have a kind of "fax notification mail
> template" file that includes keywords that the administrator could
> modify. faxrcvd would produce the mail based on that template
file...
> just a thought.
> Lee.
>
Exactly what type of options would be the normal for including in
this type of
setup?
Well, initially I had considered some kind of "template", like:
-=-=-=-=-=-
From: The HylaFAX Recieve Agent %%FROMADDR%%
To: %%SENDTO%%
Subject: Facsimile received from %%SENDER%%
=-=-=-=-=-=-=
and so on, and then faxrcvd would simply replace the %%SOMETHING%% and
that would be how it would produce the mail.
However, I'm not so sure that this would be the best approach, either.
Traditionally I've not been fond of the requirement for admins to hack
faxrcvd in order to customize the mail message. I've felt this way for
two reasons 1) faxrcvd can get replaced in an upgrade procedure, and if
a backup wasn't made..., and 2) requiring admins to hack shell
maintains HylaFAX administration at a "shell-savvy" required level of
expertise for customization, and I'm not sure if that is desireable.
But, as I indicated, sometimes I'm not so sure that these things are
bad.
Lee.
____________________ HylaFAX(tm) Users Mailing List _______________________
To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
*To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*