I have a sudden inability to connect to Yahoo pop/ssl through Popfile, from Outlook 2003 on XP Pro SP2. Nothing on my end has changed (famous last words), however using identical port/ssl settings directly to Yahoo work fine. I need some help. Here's what I know:
Yahoo admitted to server problems earlier but they were supposedly on the smtp side. These are now fixed.
The error message I now get from Outlook is:
Task 'Yahoo - Receiving' reported error (0x800CCC0F): 'The connection to the server was interrupted. If this problem continues' <yada yada>
Telnetting to localhost on popfile's listening port and entering user and password commands works fine.
However the log for attempts using Outlook shows, e.g.:
2008/2/8 22:20:02 3520: pop3: 301: +OK POP3 POPFile (v1.0.0) server ready[0d][0a]
2008/2/8 22:20:02 3520: pop3: 301: -ERR unknown command or bad syntax[0d][0a]
2008/2/8 22:20:02 3520: pop3: 301: -ERR unknown command or bad syntax[0d][0a]
2008/2/8 22:20:02 3520: pop3: 668: POP3 proxy done
2008/2/8 22:20:03 3520: pop3: 301: +OK POP3 POPFile (v1.0.0) server ready[0d][0a]
2008/2/8 22:20:03 3520: pop3: 668: POP3 proxy done
Are there debug settings I can use to see what Popfile is receiving from Outlook that it can't swallow?
Or is that coming directly from Yahoo? Again, Outlook talks directly to Yahoo pop3 servers (now) without problems, using the same port and ssl settings I use with popfile.
I have stared at my Outlook settings til I'm cross-eyed and can't see a problem.
I haven't traced through doc for "runpopfile" settings vs popfileb settings to see if I can change the invocation, so a short blow-by-blow for any debug options would be helpful. Or any other troubleshooting ideas. It feels awfully naked to be pulling mail down without Popfile in front of it :-(
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
More info: the other combinations of client and popfile config work, including ssl without popfile and non-ssl with popfile.
Something I do NOT see in the popfile log in the problematic case of ssl/popfile, is:
Attempting to connect to SSL server at pop.mail.yahoo.com:995
-- the next message after OK POP3 POPFile server ready is the -ERR unknown command or bad syntax (twice)
The attempting-to-connect message shows up in logs of the older version in happier days, and the equivalent shows up in the current version for non-ssl connections.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think this means Outlook has sent a command which POPFile does not expect or understand.
Are you sure that Outlook is _not_ configured to use SSL for this account? That error message will appear if the email client tries to use SSL to connect to POPFile.
If you want to use POPFile with SSL then SSL is only used for the "POPFile to email server" part of the connection - Outlook must not try to use SSL to talk to POPFile (because POPFile cannot accept an SSL connection from Outlook).
If you are using Outlook and POPFile to check other (non-SSL) accounts then the Yahoo account settings in Outlook should use similar settings for communication with POPFile. The only thing that needs to change is the account logon username.
You specify that POPFile should use SSL for the Yahoo account by appending ":ssl" to the account name setting in Outlook which gets sent to POPFile (e.g. pop.mail.yahoo.com:username:ssl).
The ":ssl" at end tells POPFile to use SSL for this connection.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, I had the :ssl but during the period Yahoo was flaky the correct settings didn't work and at some point while checking all the other combinations, restarting everything etc. I must have checked the SSL box on the POP side, duh. The Yahoo servers really didn't quite get their act together until today, plus I don't use POPFile for SMTP so SSL is checked on Outlook for that side of things. I think all the pieces are back together now, thanks very much!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a sudden inability to connect to Yahoo pop/ssl through Popfile, from Outlook 2003 on XP Pro SP2. Nothing on my end has changed (famous last words), however using identical port/ssl settings directly to Yahoo work fine. I need some help. Here's what I know:
Yahoo admitted to server problems earlier but they were supposedly on the smtp side. These are now fixed.
The error message I now get from Outlook is:
Task 'Yahoo - Receiving' reported error (0x800CCC0F): 'The connection to the server was interrupted. If this problem continues' <yada yada>
Telnetting to localhost on popfile's listening port and entering user and password commands works fine.
However the log for attempts using Outlook shows, e.g.:
2008/2/8 22:20:02 3520: pop3: 301: +OK POP3 POPFile (v1.0.0) server ready[0d][0a]
2008/2/8 22:20:02 3520: pop3: 301: -ERR unknown command or bad syntax[0d][0a]
2008/2/8 22:20:02 3520: pop3: 301: -ERR unknown command or bad syntax[0d][0a]
2008/2/8 22:20:02 3520: pop3: 668: POP3 proxy done
2008/2/8 22:20:03 3520: pop3: 301: +OK POP3 POPFile (v1.0.0) server ready[0d][0a]
2008/2/8 22:20:03 3520: pop3: 668: POP3 proxy done
Are there debug settings I can use to see what Popfile is receiving from Outlook that it can't swallow?
Or is that coming directly from Yahoo? Again, Outlook talks directly to Yahoo pop3 servers (now) without problems, using the same port and ssl settings I use with popfile.
I have stared at my Outlook settings til I'm cross-eyed and can't see a problem.
I haven't traced through doc for "runpopfile" settings vs popfileb settings to see if I can change the invocation, so a short blow-by-blow for any debug options would be helpful. Or any other troubleshooting ideas. It feels awfully naked to be pulling mail down without Popfile in front of it :-(
More info: the other combinations of client and popfile config work, including ssl without popfile and non-ssl with popfile.
Something I do NOT see in the popfile log in the problematic case of ssl/popfile, is:
Attempting to connect to SSL server at pop.mail.yahoo.com:995
-- the next message after OK POP3 POPFile server ready is the -ERR unknown command or bad syntax (twice)
The attempting-to-connect message shows up in logs of the older version in happier days, and the equivalent shows up in the current version for non-ssl connections.
>> -ERR unknown command or bad syntax <<
I think this means Outlook has sent a command which POPFile does not expect or understand.
Are you sure that Outlook is _not_ configured to use SSL for this account? That error message will appear if the email client tries to use SSL to connect to POPFile.
If you want to use POPFile with SSL then SSL is only used for the "POPFile to email server" part of the connection - Outlook must not try to use SSL to talk to POPFile (because POPFile cannot accept an SSL connection from Outlook).
If you are using Outlook and POPFile to check other (non-SSL) accounts then the Yahoo account settings in Outlook should use similar settings for communication with POPFile. The only thing that needs to change is the account logon username.
You specify that POPFile should use SSL for the Yahoo account by appending ":ssl" to the account name setting in Outlook which gets sent to POPFile (e.g. pop.mail.yahoo.com:username:ssl).
The ":ssl" at end tells POPFile to use SSL for this connection.
Brian
Thanks, I had the :ssl but during the period Yahoo was flaky the correct settings didn't work and at some point while checking all the other combinations, restarting everything etc. I must have checked the SSL box on the POP side, duh. The Yahoo servers really didn't quite get their act together until today, plus I don't use POPFile for SMTP so SSL is checked on Outlook for that side of things. I think all the pieces are back together now, thanks very much!