V-com, made by Avanquest.  Current versions include Fix-it Utilities and System Suite (versions 7 are most recent).   I have used this for over 6 years, even though I did try AVG, Nortons, CA, PCillin, MacAffee, to name a few.  In my opion, Fix-it contains the absolute best AV program (other than not being able to use the auto-email scan with Pegasus.  The updates are prompt, fast/easy to install,  and have in the past detected virus that Norton and others did not. The other utilities included in Fix-it are also superb and have saved me many times from giving up on my o/s, formatting, and reinstalling.

Hello all,

Friends of mine are having the following error message come up:

>> 0038 +OK Hello there. [ISafe POP3 Proxy]
<< 0027 USER programs@domain.com
>> 0024 +OK Password required.
<< 0020 PASS XXXXXXXXXXXXX
>> 0016 +OK logged in.
<< 0006 STAT
>> 0015 +OK 2 7917811
<< 0006 LIST
>> 0055 +OK POP3 clients that break here, they violate STD53.
<< 0008 RETR 1
>> 0028 +OK 7908022 octets follow.

They are running a single copy of Pegasus mail on a network machine with separate mailboxes/users. The others are not having this problem. 

What does this mean and how can it be fixed please?

Thanks

Ellie 

Nothing wrong so far.  Have them use  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 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.

[quote user="Thomas R. Stephenson"]Nothing wrong so far.  Have them use  File | Network configuration | General and turn on "Create Internet session logs (advanced diagnostic use only)" 

You can now try again to 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.[/quote]

Thanks Thomas

I have sent the instructions to her and we will see what she finds.

Regards to you,

Ellie
 

It seems that re-starting sorted the problem out, but she forgot to let me know.

Thanks for the suggestions, Thomas,

All the best, 

Ellie

 

BTW,  Ellie the line

>> 0055 +OK POP3 clients that break here, they violate STD53.

is not an error message, it's just providing you information.

I tried this, but can find no .wpm file anywhere.  My problem with Pegasus is that it suddenly stopped receiving mail.  It displays the message at bottom, "Identifying unread messages," then , "Downloading message 1 of xx," then displays this error:

>> 0018 +OK Hello there.
<< 0011 USER kiss
>> 0024 +OK Password required.
<< 0017 PASS XXXXXXXXXX
>> 0016 +OK logged in.
<< 0006 STAT
>> 0013 +OK 1 73007
<< 0006 LIST
>> 0055 +OK POP3 clients that break here, they violate STD53.
<< 0008 RETR 1
>> 0026 +OK 73007 octets follow.

This is driving me crazy.  I've used Pegasus for years, but now cannot receive mail.  I've searched the knowledge base, forum, internet, etc., but can't find how to fix this.  I have the same Pegasus on my laptop computer, and it still works fine.

I have opened and closed Pegasus 3 times.  The second time it did actually create .wpm files which are not really any help as they make no sense to me.

00:51:57.241 >> 0016 +OK logged in.\0D\0A
00:51:57.241 << 0006 STAT\0D\0A
00:51:57.331 >> 0013 +OK 1 17100\0D\0A
00:51:57.331 << 0006 LIST\0D\0A
00:51:57.421 >> 0055 +OK POP3 clients that break here, they violate STD53.\0D\0A
00:51:57.421 >> 0009 1 17100\0D\0A
00:51:57.421 >> 0003 .\0D\0A
00:51:57.421 << 0008 RETR 1\0D\0A
00:51:58.333 >> 0026 +OK 17100 octets follow.\0D\0A
00:51:58.333 >> 0076 Return-path: <20070630MAR026T0000D7B@bouncedreports.discoverfinancial.com>\0D\0A

and so on...................

00:51:58.333 >> 0082 \09by naxp41l1.ihs.discoverfinancial.com (AIX5.3/8.13.4/8.13.4) id l626cDZr508206;\0D\0A
00:51:58.333 >> 0033 \09Mon, 2 Jul 2007 02:38:13 -0400\0D\0A
00:51:58.333 >> 0038 Date: Mon, 2 Jul 2007 02:38:13 -0400\0D\0A
00:51:58.333 >> 0078 Message-Id: <200707020638.l626cDZr508206@naxp41l1.ihs.discoverfinancial.com>\0D\0A
00:52:28.336 8: Socket read timeout.
00:52:48.345 << 0006 QUIT\0D\0A
00:52:48.435 >> 0041 Discover_eReport@discoverfinancial.com>\0D\0A
00:52:48.435 --- Connection closed normally at Mon, 02 Jul 2007 00:52:48. ---\0A\0A

I still can't receive mail.  Can anyone help?

[quote user="azwolfman"]

I have opened and closed Pegasus 3 times.  The second time it did actually create .wpm files which are not really any help as they make no sense to me.

00:51:57.241 >> 0016 +OK logged in.\0D\0A
00:51:57.241 << 0006 STAT\0D\0A
00:51:57.331 >> 0013 +OK 1 17100\0D\0A
00:51:57.331 << 0006 LIST\0D\0A
00:51:57.421 >> 0055 +OK POP3 clients that break here, they violate STD53.\0D\0A
00:51:57.421 >> 0009 1 17100\0D\0A
00:51:57.421 >> 0003 .\0D\0A
00:51:57.421 << 0008 RETR 1\0D\0A
00:51:58.333 >> 0026 +OK 17100 octets follow.\0D\0A
00:51:58.333 >> 0076 Return-path: <20070630MAR026T0000D7B@bouncedreports.discoverfinancial.com>\0D\0A

and so on...................

00:51:58.333 >> 0082 \09by naxp41l1.ihs.discoverfinancial.com (AIX5.3/8.13.4/8.13.4) id l626cDZr508206;\0D\0A
00:51:58.333 >> 0033 \09Mon, 2 Jul 2007 02:38:13 -0400\0D\0A
00:51:58.333 >> 0038 Date: Mon, 2 Jul 2007 02:38:13 -0400\0D\0A
00:51:58.333 >> 0078 Message-Id: <200707020638.l626cDZr508206@naxp41l1.ihs.discoverfinancial.com>\0D\0A
00:52:28.336 8: Socket read timeout.
00:52:48.345 << 0006 QUIT\0D\0A
00:52:48.435 >> 0041 Discover_eReport@discoverfinancial.com>\0D\0A
00:52:48.435 --- Connection closed normally at Mon, 02 Jul 2007 00:52:48. ---\0A\0A

I still can't receive mail.  Can anyone help?

[/quote]

The system timed out at 30 seconds.  What have you set the TCP/IP timeout to in the POP3 setup?  If this is 30 seconds, and the server is a busy server,  try increasing this to about 90-120 seconds and see if this fixes the problem.  If it does not then I suspect there is a TCP/IP level Winsock problem.  A POP3/SMTP transmission may fail if the MTU packet size is so large that a packet is fragmented.  In many cases the receiving system router blocks the receiving servers "packets fragmented" response to the sending system using "MTU Discovery".  These oversize packets are not accepted and so are resent.  This results in a timeout, generally at the end of the message transmission but it can be anywhere in the process.  You need to reduce the MTU size. Windows defaults to a 1500 MTU and many routers and DSL connections need 1492.  You might simply want to turn off the MTU Discovery operation.

You might want to get a copy of SG TCP Optimizer that I find quite handy.  http://www.speedguide.net/downloads.php  This little utility will allow you to test your MTU for maximum size without fragmentation against specific servers.  If will also make it easy to adjust the MTU. 

And finally, does this computer, by chance, happen to have an NVidia NForce 4 chipset on the motherboard?  If so, many other have had this exact problem, and it turned out to be an optimization setting for the built in NIC which caused the problems with packet fragmentation. Disabling the advanced optimization capability called "checksum offload" made all the problems of sending SMTP mail via WinPMail disappear.

Thank you for the reply.  I had the timeout set at 300 seconds.  I thought that might be a problem, so I increased it to 500 seconds - still could not receive mail.  I thought maybe I had inadvertently entered something wrong in the spam rules file (winrules), so I deleted all the rules and started fresh.  Still have same problem, except I keep getting one same email over and over (from a trusted source that I have been receiving daily mails from for over a year).  Otherwise no mail.  Just message at bottom of Pegasus, "Downloading message 1 of 40. 0%".  

A couple days ago, I uninstalled Pegasus and cleaned the registry, then installed version 4.41.  Still same problem.  [:@] No, computer does not have NVidia chipset.  Keep in mind Pegasus had been running on this same computer for years, and for several weeks with no changes to the pc, router, modem, etc.  The NIC is in a PCI slot and is hard-wired to the router.  Suddenly, just one day Pegasus stopped working.  I have a copy of Pegasus on my laptop which still works fine.  The only way I can get mail onto my pc is to let the laptop get the mail, then copy the PMI and PMM files over onto the desktop.

I will go to the http://www.speedguide.net/downloads.php  page and check it out.

Does your PC run a virus checker that is set up to filter incoming POP3 emails?

My anti-virus program does have that option, but I turned that off over a year ago because I discovered that it prevented Pegasus from downloading the mail.

Hot Da---!  I just checked and discovered that my email anti-virus auto scan is turned on again!  Somehow this pc turned it on by itself, or some program turned it on.  This has to be the problem.  I'll just turn it off again and monitor it periodically to make sure it doesn't turn itself back on.

For the record, which virus checker is it that causes this problem?