SMTP works fine now. It must have been one of those out-of-a-blue-moon server maintenance breaks. This ISP is normally very reliable. Thanks for your help. I updated my first post to "resolved/ignore".
Update: RESOLVED. Please ignore this thread. CrossLoop works fine with PM v4.31. The problem was due to ISP's smtp server maintenance.
-----------
My PM won't send SMTP mail any more, it times out. I suspect CrossLoop (pc remote control app) that I have just installed and used a few times to access a remote PC. CrossLoop is now completely turned off. Incoming POP3 works ok. Any idea how to troubleshoot this? I would prefer not to install v4.52, too much work setting up the configuration. My ISP has not made any changes to authentication protocol and the ping to smtp server is ok:
http://img843.imageshack.us/img843/8571/11212010175605.png
http://img843.imageshack.us/img843/8862/11212010175655.png
> After I have installed CrossLoop (pc remote control app) my PM won't send SMTP mail any more, it times out. Incoming POP3 works ok. Any
> idea how to troubleshoot this? I would prefer not to install v4.52, too much work setting up the configuration. My ISP has not made any
> changes to authentication protocol and the ping to smtp server is ok
I have no idea how Crossloop will affect TCP/IP but Go to File | Network configuration | General and turn on "Create Internet session logs (advanced diagnostic use only)"
Checking this control tells Pegasus Mail to create special log files that show the entire exchange of information between it and the servers it connects to. Each session will be created in a file called TCPxxxx.WPM in your home mailbox directory (the "xxxx" is replaced by four digits). Creating session logs will slow down the performance of your system somewhat, and you should be aware that any username and password information exchanged between Pegasus Mail and the server will be shown in the log, *even* if you use SSL to secure the connection. Session logs are primarily useful if you need to debug a problem between Pegasus Mail and one of the servers it connects to - you should enable the option only on instructions from a system administrator or from Pegasus Mail technical support. [ Technical note: this control has the same effect as using a "-Z 32" commandline switch when you run Pegasus Mail ]
You can now try again to send/receive the mail and then look at the resulting TCP/IP debug file. Review of this file will tell you exactly what is going on between WinPMail and the server.
If you want you can post the file in a replay to this list, it's just a text file, for other to analyze. Munge your password in the session log if you post here.
Thanks for your prompt response. Here is "send" log. Not much info in it, though:
TCP0007.WPM
--- Sun, 21 Nov 2010 18:25:36 ---
Connect to 'smtp.primus.ca' port 25, timeout 30.
18:25:36.906 [*] Connection established to 216.254.136.21
18:26:06.906 8: Socket read timeout.
18:26:11.031 --- Connection closed normally at Sun, 21 Nov 2010 18:26:11. ---\0A\0A
After analyzing time stamps on past sent messages, it looks like CrossLoop is not the source of a problem. A few days back both CrossLoop and sending smtp mail worked ok. So the issue must be elsewhere.
> Thanks for your prompt response. Here is "send" log. Not much info in it, though:
> TCP0007.WPM
> --- Sun, 21 Nov 2010 18:25:36 ---
> Connect to 'smtp.primus.ca' port 25, timeout 30.
> 18:25:36.906
> Connection established to 216.254.136.21
> 18:26:06.906 8: Socket read timeout.
> 18:26:11.031 --- Connection closed normally at Sun, 21 Nov 2010 18:26:11. ---\0A\0A
Looks like a good server to me. Are you sure your ISP is not blocking port 25 outbound?
220 mail.primus.ca mail-05.primus.ca ESMTP Daemon - Outbound1
ehlo thomas
250-mail-05.primus.ca Hello mail.tstephenson.com [209.128.94.2]
250-SIZE 104857600
250-PIPELINING
250-AUTH PLAIN LOGIN
250-STARTTLS
250 HELP
