On Thu, 2010-07-22 at 22:48 +0200, Karsten Bräckelmann wrote: > Interesting. After years of fetchmail usage, and way above single-figure > millions of messages fetched (just a very conservative estimate), I have > yet to find even one mail stuck on a server. > It worked well for me for a couple of years, but then the unpurged message rate rose dramatically about a year ago. When it was consistently getting to tens of messages a week I moved. Tis was probably some arcane interaction between it, my ISP's POP3 server and my broadband provider and/or BT's pipes. I must admit this is about the only really obnoxious bug I found in fetchmail - the others are a documentation bug (I never did work out how to make it work in multi-user mode) and an odd shutdown bug: "service fetchmail stop" didn't work.
> Well, I won't go down the route of arguing fetchmail, getmail, or > alternatives. I don't mind. :) > I wasn't intending to start a war - just provide a heads-up for anybody else having fetchmail problems. If you look, you can find grousing about undefined bugs that Eric Raymond allegedly refuses to fix, but I have no idea whether these are genuine or just bitching by somebody with a grudge. > However, I know SA does understand fetchmail headers, and correctly > re-starts header parsing. I guess it is the same with getmail, or does > it simply not add any header? > It adds a 'Received ..... with POP3' header, but you have to know this was added by getmail because it doesn't identify itself. Martin
