[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: postfix delivery options



* Vineet Kumar (debian@virtual.doorstop.net) [011010 16:13]:
> Personally, I've switched from fetchmail to getmail. I can't give it a
> wholehearted recommendation, though: I have it delivering straight to
> procmail but since (as pointed out from fetchmail(1)) procmail is a
> "safe" or "careful" mda, it occasionally farts out with a -1 return
> value, meaning I have to run getmail a few times to grab all hundreds of
> messages that trickle in from these mailing lists =) Fortunately, as
> getmail is in python, it was easy to modify its default behavior of
> giving the POP3 server a (doh!) RSET on such errors. That was a real
> horror when I had a few hundred messages to download. One procmail stall
> and it would RSET the server and try to start at the beginning next
> time. (Maybe I should have filed a bug report with a patch...) Now at
> least it just picks up where it left off, and a procmail rule keeps me
> from getting duplicates when that happens.

Okay, I can now give getmail the wholehearted recommendation it
deserves! Since procmail was being so weird and reterning strange things
(not to mention that its syntax is pure voodoo) I ditched it, and hard.
I've been using maildrop instead, and it's sweet. And it hasn't choked
once, meaning that getmail can continue doing things The Right Way
without any hacks for a tweakish MDA.

Better still, I can do some basic filtering within getmail itself: mail
to certain addresses (as it decides by looking at a configurale list of
common headers) can be delivered straight to an appropriate maildir from
within getmail itself. I'm still using the default delivery going
through maildrop, though, so I can do duplicate elimination before
filtering.

Better *still*, I got exim set up using suffixes a la qmail, so it hands
off to .forward-suffix (if it exists) or runs maildrop with $1 set to
the local part suffix. (Or runs procmail with $1 set to suffix, but I'm
not looking back there!)

> 
> I should warn that I would guess that fetchmail would behave the same
> way when delivering straight to procmail, so watch out. (Do let me know
> if it handles the problem better, though!)

Since it was procmail wqeirdness, I'd imagine any mail fetcher would
behave the same way. The best answer I can give is to switch to maildrop
from procmail, even if you do stay with fetchmail.

good times,

-- 
Vineet                                   http://www.anti-dmca.org
Unauthorized use of this .sig may constitute violation of US law.
echo Qba\'g gernq ba zr\!             |tr 'a-zA-Z' 'n-za-mN-ZA-M'

Attachment: pgpEPMXUdr_xW.pgp
Description: PGP signature


Reply to: