On 5/9/05, russ(_dot_)pridemore(_at_)comcast(_dot_)net
<russ(_dot_)pridemore(_at_)comcast(_dot_)net> wrote:
<---SNIP--->
**.*fetchmail: message
russ(_dot_)pridemore(_at_)mail(_dot_)comcast(_dot_)net:1 was not the expected
length (81887 actual != 596379 expected)
And that's what you were looking for. The message was truncated by the ISP.
Now, you may want to trawl the archive for this list if you haven't
already. I've a vague memory of Comcast having a broken POP service.
If I'm right, there's a fix buried in the list.
Off the top of my head, fetchmail uses TOP to pull down messages and
some servers don't behave "correctly" with TOP. You can force
fetchmail to use RETR by using the "fetchall" keyword.
--
Please keep list traffic on the list.
Rob MacGregor
Whoever fights monsters should see to it that in the process he
doesn't become a monster. Friedrich Nietzsche