Re: Broken POP3 impolementation?

["Robert G. Brown" <bob@xxxxxxx>]

I'd written (among other things)....
>>OK, anyone out there using fetchmail on a Voyager provider? Anyone see this
>>kind of problem in the past? Is fetchmail broken (I doubt it, but have to
>>ask), or has the ISP upgraded to a broken POP3 server?

On Fri, 21 Jul 2000, "Cj Stremick" <cmstremi@qwestinternet.net> wrote:
>Were the messages viewed?  If so (fetchmail with the "-k" flag, maybe),
>and you were retrieving without the "-a" flag, it will leave the messages
>on the server.  Have you tried to kill fetchmail and just run a "fetchmail
>-a"? That may have done the trick.

I use neither flag; defaulting fetchmail to download everything, erase
everything. None of the 82 messages were viewed, but perhaps this is a
clue....hmm...perhaps fetchmail THINKS they were veiwed, which implies a
new (and broken) POP3 server at Voyager...

Nope! Added -a to the fetchmail call (and restarted fetchmail), and it's
still broken!

On Fri, 21 Jul 2000, Adam Tauno Williams <adam@morrison-ind.com> wrote:
>Yes,  I occasionally get a "bum" message that causes fetchmail to flake out.  If
>I nuke the first message in the box with another POP tool (netscape, etc...)
>then it works fine again.  It seems to be something about having to many
>recpients (a total guess, but a gut feeling, because it has always been a spam
>message). 

I've seen this as well from time to time. Was the offending mail message
was downloaded and removed, proper functioning resumed.

This is a bit more serious than that. With the mailbox completely cleaned out, 
K-Mail continues to function right, and fetchmail continues to download nothing. 

                                                         Regards,
                                                         ---> RGB <---