Stephan von Krawczynski <skraw(_at_)ithnet(_dot_)com>:
Obviously the POP3-server sees the same and thinks that UPDATE state was not
reached and therefore does not perform the deletes. So on the next fetchmail
try all the same picture.
In my eyes this is a flakey fetchmail handling of smtp error conditions, it
should read the complete mail and _then_ perform the "dele" and the "quit", at
least it should check whether the pop3-servers answers have something to do
with the RFC ...
In fact, it does work the way you describe. Your POP3 server is doing
something *very* fluky that is fooling fetchmail. We've occasionally
seen such things before.
--
<a href="http://www.catb.org/~esr/";>Eric S. Raymond</a>