Open Source Applications Foundation

[Design] filters: Subject to automation

Bruce Dykes Sun, 10 Nov 2002 23:54:59 -0800 (PST)


--- Ray Ryan <ray.ryan@pobox.com> wrote:

> I wonder if it could/should be more general than you
> describe. People 
> have been proposing having rules for outgoing mail.
> Does that take care 
> of this feature for you? You could have an outgoing
> rule like (pardon 
> heinous syntax):
> 
> if (${Project} != null) Subject = "[${Project}]
> ${Subject}";

Ugh. If I have to write that to take advantage of a
feature, that's a feature I won't be using. (which
seems to be a good design mantra)

> The obvious problem with this approach is that it
> doesn't let the user 
> see the mod'd subject line, assuming outgoing rules
> are executed on 
> Send.

Which is a Bad Thing. Anything a user is reasonably
expected to have authored, such as addresses,
subjects, and bodies, should be vettable by the user
before sending.

Which is not to say Send Rules are bad. I would love
to use the spammer trick of finding an open relay, and
using whichever one is open to send my mail. But in my
case, Chandler would only be selecting between my
ISP's relay, which isn't available from my job, and my
job's relay, which isn't available when I'm home on my
ISP.

Bruce


__________________________________________________
Do you Yahoo!?
U2 on LAUNCH - Exclusive greatest hits videos
http://launch.yahoo.com/u2