6 messages in net.sourceforge.lists.courier-maildrop[maildropl] maildrop and getmail (was...
FromSent OnAttachments
Payal RathodOct 6, 2002 1:13 am 
Alexander LazicOct 6, 2002 1:59 am 
Payal RathodOct 6, 2002 6:07 am 
Alexander LazicOct 6, 2002 7:42 am 
Mark WeinemOct 6, 2002 12:26 pm 
Payal RathodOct 7, 2002 5:08 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] maildrop and getmail (was: a lot of filter problems)Actions...
From:Mark Weinem (mark@uni-duisburg.de)
Date:Oct 6, 2002 12:26:41 pm
List:net.sourceforge.lists.courier-maildrop

On Sun, 06 Oct 2002, Payal Rathod wrote:

But my main problem is still where do I apply maildrop. As getmail does not require a SMTP, where do I use maildrop.

cat .getmail/getmailrc |grep maildrop postmaster = |/usr/local/bin/maildrop

Please read the good documentation that ships with getmail - it's all there!

Also, PLEASE PLEASE tell me where to get docs about this so called filtering language of maildrop.

Read the maildropfilter and maildropex manpages, scan the mailinglist archives for examples. There are two example .maildroprc files at http://dotfiles.com

I have a feeling that procmail docs are more extensive and simpler.

Maybe. But you could thange this: learn something about maildrop and start writing "more extensive and simpler" documentation.

I want to learn but I get ANGRY when filter (read procmail/maildrop) and email clients (read mutt) get more difficult than the server (read qmail).

If maildrop and mutt frustrate you, why don't you use a simpler mailprogram with GUI and integrated filter functionality? Mutt and maildrop are not easy to use.

Ciao, Mark