[fetchmail]RE: Socket Error

[Lucky Me]

I wanted to repost this, as I fear I may have broken protocal with my last
response.

"Matthias Andree" <ma@dt.e-technik.uni-dortmund.de> writes:

>> Using Fetchmail 6.2.5

>Are you still using fetchmail or have you switched to getmail instead,
>given your post on that list an hour later?

First of all thank you for your reply.  I have been experimenting a little
with getmail because I have been struggling with this fetchmail socket error
problem for about 3 week.  I would rather use fetchmail.  It seems a little
more straight forward and easier to configure.  And as I mentioned before,
when it works, it works very well for me.  And I have found that the
fetchmailconf utility is very helpful.

>> postfix will also give a message after the fetchmail socket error of:
>>
>> "postfix/smtpd[3695]: lost connection after DATA from
>> localhost[127.0.0.1]"

>This information isn't complete...

The section of the log file created when I used the "fetchmail -v -v -L
/var/log/mail" command it located here:

http://wpffl.netfirms.com/fetchmail.txt - Please ignore the banner text that
is added to the top of the page by this web host provider.

>> I noticed it hung on the same spam message two different times, so maybe
it
>> is a problem with the type or formating of the email.

>...but such things can happen, when, for instance, the POP3 server fails
>to send a proper message end marker. There may be other problems, but to
>debug this, we need a copy of the mail or session captured with
>"tcpdump -w debug.dump host pop3.example.org".

>You MUST change your password before uploading the file to some FTP or
>web server. Please post only the URL, not the whole file.

The output I get with the "tcpdump -w debug.dump host mail.server.com" is
located here:

http://wpffl.netfirms.com/debug.dump.txt - Again, please ignore the banner
text that is added to the top of the page by this web host provider.

>> My Linux box is behind a firewall, are there any ports I should open or
>> forward to the Linux box to diagnose the problem?

>As long as it doesn't firewall 127.0.0.1, it should be fine.

Again, I appreciate your help.