On Friday 31 October 2003 16:03, Carlos E. R. wrote:
The Thursday 2003-10-30 at 07:27 -0500, E.F.Maurer wrote:
I got it working before this, but just added the ssl which makes me feel a little better. Did you set this up manually or did you use fetchmailconf? I'm still kinda confused as to why fetchmailconf couldn't probe the server for the right protocol or mailbox format. Because of this my .fetchmailrc had no protocol so it tried all of them making it seem like it crashed, it was slower than dialup.
I don't remember now fetchmailconf (I do it manually), but I'm running it right now to check. It has improved!
On the protocol section, you see that the default is "auto": this will set the configuration file to "auto". There is a "probe for supported protocols" as well, but seeing your original configuration file, I think you left it as "auto". In fact, the configuration file I have just created using fetchmailconf is very similar to yours.
Now, what happens in auto mode? I explained this before (2003-10-23), but you didn't notice. I'll explain now with more details:
The fetchmail programs tries to connect to the IMAP port (143). If it gets a response, ie, it is open, it tries to use IMAP - this is shown as happening in the logs you posted here. And it will try till timeout: that is, five full minutes. It is not stuck, it is waiting. You could have set a lower timeout on the config (expert mode).
After those 5 minutes of waiting, it will try the next protocol, pop3 (notice that it is a different port, 110), and even pop2 (port 109).
Who is the culprit here? Surely, your ISP, because they left the 110th port open, and did not put a configured server on it. Shame on them, but it has happened to me before.
Thanks Carlos. Sorry i missed your first post. I changed isp's and was changing my email addresses, and subscribing and unsubscribing until I got it all setup the way i wanted it, it probably fell through the cracks. i just started a new job, with comcast, I'll just have to ask about why the port for imap is left open. I guess i got impatient when i thought it stalled, I was expecting it to be faster than dialup, well it is now. I've only used fetchmailconf 2 times before and i only used the novice setup page, I'll have to check out the expert page. I used to let fetchmail probe for the right protocol and it worked for my old isp, but if all those ports are open but not working I can see how fetchmailconf was confused and left it on auto. Thanks again.