Paul Lussier said:
> In a message dated: Mon, 29 Jan 2001 10:19:55 EST
> Jeffry Smith said:
> 
> >One thing I'm still waiting for in any e-mail system that includes filtering 
> >is a tie-in to procmail.  Why write your own filtering module instead of a 
> >front end to procmail (hm.  Tie exmh to dotfile-procmail, since both are 
> >tcl/tk?).
> 
> Supposedly the latest release of exmh (2.3) has this built in.  However,
> here's the problem I see with client "built in" filtering capability; it 
> relies upon the client being up and running to filter mail.  That means that 
> everything goes into your normal spool directory.  The client then needs to 
> grab that mail and filter it.  No running client = no filtered mail.  To me, 
> this is a problem, and one easily solved by de-coupling the filter engine from 
> the mail client and having it invoked by the transport agent.

I haven't seen that version of exmh yet. My thought on the tie-in was, you 
realize you need to filter a message, pop up the window of dotfile-procmail, 
you can build your filtering, and add it to your current .procmailrc.  Now, it 
filters without being up and running.  Of course, there is still the issue of 
order of the rules (one I've been bitten by many times, so I move stuff around 
w/vim), but that's another issue.

> 
> Many people may be perfectly content with only filtering mail while their 
> client is up and running, in which case, the coupling of the client and 
> filtering agent is fine.  However, consider the following scenario:
> 
>       - You get 400+ e-mails per day
>       - You're going to be out of the office for 2 weeks
>       - You want 'vacation' to auto-respond to your mail, but not to
>         any "list" mail
>       - You may want to connect via dial-up/vpn and check to see if you
>         have any "important" mail
> 
> Under this scenario, all your mail is either in:
> 
>       - the default mail queue (usually /var/spool/mail/<username>
>       - or being filtered because you've left your mail client running.
> 
> Leaving your mail client running so that it filters your mail is a risky idea;
> what happens if the machine your client is running on crashes while you're 
> away?  You've then got unread mail in 2 places, the default mail queue and 
> your pre-sorted folders.

Big <snip> here to say I agree with you.  My home systems dials up my ISP routinely, 
snags my mail, and closes.  While it's doing so, it runs it through procmail.  While 
I'm at LWE this week, I won't even be logged into my home system.

It also means I don't have to worry about my ISP mail account filling up.

So, I want the tie-in to help the client build the scripts, but I want procmail 
running as a separate MDA, not part of the client (MUA).

jeff

-----------------------------------------------------------------------
Jeffry Smith      Technical Sales Consultant     Mission Critical Linux
[EMAIL PROTECTED]   phone:603.930.9739 fax:978.446.9470
-----------------------------------------------------------------------
Thought for today:  Marginal Hacks n. 

 Margaret Jacks Hall, a building into
   which the Stanford AI Lab was moved near the beginning of the 1980s
   (from the D. C. Power Lab).





**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to