Thank you for the input, and I apologize for the long delay in my reply. 

In my case I also could not Telnet into the server, but because I could use a web-based tool I knew the server was accessible.

It took a while, but the problem turned out to be a configuration change way up the corporate food chain. Once that was undone, the POP access was restored.

Thank you again for the assistance.

My Pegasus 4.41 had been working perfectly until a few days ago when it stopped downloading mail from the company's Exchange server. I can see it apparently connecting but just as quickly it disconnects. After reading a few posts here I tried to increase the timeout, and then turned on session logs but the log is so short I don't know what to make of it.

--- Sat, 31 Jan 2009 21:29:02 ---
Connect to 'xxxxxxxxxx' port 110, timeout 90.
21:29:02.375 [*] Connection established to xxx.xxx.xxx.xxx
21:29:02.375 << 0006 QUIT\0D\0A
21:29:02.375 --- Connection closed normally at Sat, 31 Jan 2009 21:29:02. ---\0A\0A

I also tried the 'Selective mail download' but nothing appeared -- no window, no prompt, nothing. 

Any guidance on where to look next would be appreciated.

[quote user="BailwyWTNH"]My Pegasus 4.41 had been working perfectly until a few days ago when it stopped downloading mail from the company's Exchange server. I can see it apparently connecting but just as quickly it disconnects. After reading a few posts here I tried to increase the timeout, and then turned on session logs but the log is so short I don't know what to make of it.

--- Sat, 31 Jan 2009 21:29:02 ---
Connect to 'xxxxxxxxxx' port 110, timeout 90.
21:29:02.375 [*] Connection established to xxx.xxx.xxx.xxx
21:29:02.375 << 0006 QUIT\0D\0A
21:29:02.375 --- Connection closed normally at Sat, 31 Jan 2009 21:29:02. ---\0A\0A

I am going to assume that the xxxxxxxx points to the IP address of the Exchange host and not some proxy or other software/hardware between WinPMail and the host. I am also assuming that yuo are not running a firewall blocking WinPMail's access to the internet.  FWIW, it would have been a lot more helpful if you were to have provided the IP address of the server.

I also tried the 'Selective mail download' but nothing appeared -- no window, no prompt, nothing. 

Any guidance on where to look next would be appreciated.

It sure looks to me like either the Exchange host is down or at least not running since it immediately rejects the connection.  What happens when you telnet directory to this IP address into port 110?[/quote]

Hello Gents,

I have an apparently worse problem with my exchange server too. All was well until at some point during last Thurday, I connected to my server (exchange.mcgill.ca) and had Pegasus stuck running 100%CPU. I tried to close it, but apparently only the window closes and the program remains open, accordingly to Process Explorer.

 I contacted tech support from my mail server and they gave me some instructions (use port 993 or 995, SSL, etc) but the same problem.

Notable programs running: WIndows 2000 with latest updates, AVG antivirus, ZoneAlarm firewall. All my other email programs run well even Pegasus can download POP3 from another account without problems.

 Any thoughts?

[quote user="alexD"]

Hello Gents,

I have an apparently worse problem with my exchange server too. All was well until at some point during last Thurday, I connected to my server (exchange.mcgill.ca) and had Pegasus stuck running 100%CPU. I tried to close it, but apparently only the window closes and the program remains open, accordingly to Process Explorer.

 I contacted tech support from my mail server and they gave me some instructions (use port 993 or 995, SSL, etc) but the same problem.

Notable programs running: WIndows 2000 with latest updates, AVG antivirus, ZoneAlarm firewall. All my other email programs run well even Pegasus can download POP3 from another account without problems.

 Any thoughts?

Here's a few

1.  There is a really big message on the Exchange host and you are timing out.  Use File | Selective mail download to see what's on the server.  

2.  If you are using AVG between the Exchange host and PMail turn it off.

3.  Check to make sure the firewall is not blocking PMail.

[/quote]

[quote user="Thomas R. Stephenson"][quote user="alexD"]

Hello Gents,

I have an apparently worse problem with my exchange server too. All was well until at some point during last Thurday, I connected to my server (exchange.mcgill.ca) and had Pegasus stuck running 100%CPU. I tried to close it, but apparently only the window closes and the program remains open, accordingly to Process Explorer.

 I contacted tech support from my mail server and they gave me some instructions (use port 993 or 995, SSL, etc) but the same problem.

Notable programs running: WIndows 2000 with latest updates, AVG antivirus, ZoneAlarm firewall. All my other email programs run well even Pegasus can download POP3 from another account without problems.

 Any thoughts?

Here's a few

1.  There is a really big message on the Exchange host and you are timing out.  Use File | Selective mail download to see what's on the server.  

2.  If you are using AVG between the Exchange host and PMail turn it off.

3.  Check to make sure the firewall is not blocking PMail.

[/quote][/quote]

 Thank you for your response Thomas, here are my direct answers:

1. I have normal access to the Exchange server from the web and also from Outlook Express (as a temporary measure). Thus no big message clogging things up.
2. AVG is not supossed to mess up with any email for that purpose. I also tried de-activating AVG while trying to connect and the same results.
3. The firewall is not blocking PMail.

I used to access the server using POP3, and it was working but it stopped last week (precisely Jan 30th). I tried to create IMAP folders with PMail and it didn't work either, thus beginning my plight on the matter.

I keep contact with the customer support, but so far no answer. I am trying to find what changed in that date. It is possible they tried to enforce SSL on their servers and that is creating a conflict, but I need to get an answer from them. However, I do not experience problems while using Outlook Express and IMAP folders accessing the server. I also tried reinstalling PMail and didn't work too. So I believe it is something in between.

Is it possible some file or folder is corrupted in my email directory that is causing the problem? How I can fix that?

 Thank you for your response Thomas, here are my direct answers:

1.  I have normal access to the Exchange server from the web and also

from Outlook Express (as a temporary measure). Thus no big message

clogging things up.
2.  AVG is not supossed to mess up with any email for that purpose. I

also tried de-activating AVG while trying to connect and the same

results.

3,  The firewall is not blocking PMail.

I used to access the server using POP3, and it was working but it

stopped last week (precisely Jan 30th). I tried to create IMAP folders

with PMail and it didn't work either, thus beginning my plight on the

matter.

I worked a Exchange host for years via IMAP4 and I has to user the server/username for the username to ensure I accessed the Exchange host with my mailboxes.   POP3 did not require this but IMAP4 did.

I keep contact with the customer support, but so far no answer. I am

trying to find what changed in that date. It is possible they tried to

enforce SSL on their servers and that is creating a conflict, but I

need to get an answer from them. However, I do not experience problems

while using Outlook Express and IMAP folders accessing the server. I

also tried reinstalling PMail and didn't work too. So I believe it is

something in between.

Is it possible some file or folder is corrupted in my email directory that is causing the problem? How I can fix that?

I can't see why anything in the PMail mailbox could affect anything but if you are trying to access a device that is not available (printer, disk drive like a CDROM or USB device that is offline) you could have delays.

[quote user="Thomas R. Stephenson"]

If you are using AVG between PMail and the sercer you need to re-configure the PMail POP3 setup to bypass AVG.

[/quote]

 And how do I do tell PMail to bypass AVG?

As a side note, all the action with the 100% CPU seems to occur at "msvcrt.dll+0x8532", according to Process Explorer.

[quote user="alexD"][quote user="Thomas R. Stephenson"]

If you are using AVG between PMail and the server you need to re-configure the PMail POP3 setup to bypass AVG.

[/quote]

 And how do I do tell PMail to bypass AVG?

 You go to the POP3 and SMTP setups in Tools | Internet options and ensure you are pointing directly at the POP3 and SMTP host not some internal IP address and/or port.

As a side note, all the action with the 100% CPU seems to occur at "msvcrt.dll+0x8532", according to Process Explorer.

That's one of the Visual C/C++ run time libraries and I'm not sure what it does.

[/quote]

Thomas,

Thanks for your reply. I do have the server names correct.

Regarding my problem, I come to think that it is something PMail uses or does that causes the problem. I replicated my account with Outlook Express, and it doesn't have any problems connecting to either the POP3 or the IMAP folders of my exchange server.

Only when PMail connects to the server using SSL is when the trouble begins. And I have no more clues what the problem might be.

At least I do have access to my emails from a client program, but not PMail. 

Alejandro