Dear Tbilisi,

You can seamless upgrade from version 4.12a to 4.51

Ah Hah!

You are a scholar and a gentleman, kind sir. When I selected "Edit," there it was - as if by magic!  It was well hidden, but you are correct that it is there. It also does not exist in the Help or database files by any key word that I could think up.

I thank you so much and wish you a wonderful evening and weekend.[:)]

Yes, I understood that as it also displays OK for me.  As I said, it is the mail message format that is wrong, not the HTML web display.

At the risk of getting slightly off-topic (!), what "total window"? Oh, you see? Now I've gone and given you some more points, too! This is a never-ending whirlpool of paying points to people who paid you points for getting points...     :D

OK, enough. This is meant to be a serious forum you know. E-mail isn't about fun. Now back to work. Chop-chop!

The charset which is claimed to be "ISO-8859-1" is actually UTF-8. Why? Because the character "ü" is encoded as "=C3=BC" which is a 2-byte encoding.

Has the message in question been created by Pegasus Mail (which I doubt) or did you receive this message from another person? If so, what email client did they use?

 

Sven

 

Thank you for your response.

I have seen that the firewall blocks traffic ICMP-Typ 3 and 4 when I send a mail in this account. Then I have enabled traffic ICMP-Typ 3 and 4 in the firewall.

The problem:

> 00:43:34.828 7: Socket read error 2746.
> 00:43:43.906 << 0006 QUIT\0D\0A
> 00:43:43.906 9: Socket write error 2746.

was solved. I had not changed anything other (MPU, ...)

As well large mails can now be send in this account without any problems.

Peggy

Thanks Thomas

your suggestion fixed my problem

Thanks once again.

kalu

> Whenever the user sends his queued messages, a small red exclamation
> point button appears on the status bar. Clicking the button gives
> this error: "Pegasus Mail has encountered an unidentified error on
> your TCP/IP network. The error code returned to Pegasus Mail was 0H.

The Zero Hex error says Pegasus Mail can't connect to the server and there was not error code provided.  You should have the user 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.

> Further information on this problem is unavailable - please check
> that your TCP/IP software is correctly installed and configured and
> there are no problems with your TCP/IP network at present." We are
> on an extremely large university network, so changes to the network
> are out of the question. Also, no other users of Pegasus are
> reporting any problems.

Two things come to mind, the timeout is set too low or there is a packet fragmentation problem.  He first should go to Tools | Internet options | (Sending) SMTP, edit the SMTP setup and set the timeout to something like 180 seconds,  

If this does not help then I suspect packet fragmentation.  The POP3/SMTP transmissions 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.


> Occasionally, when sending messages, he receives a "Mail Delivery
> Failure" message saying "Delivery has failed..." due to a
> nondescript "TCP/IP error while processing job." Oddly enough, if
> you check, the e-mail actually WAS sent out. The Mail delivery
> failure is obviously coming from Pegasus, and not our Exchange
> servers.

Another sign of packed fragmentation.  The SMTP process fails when the .<CR><LF> end of message is sent via a timeout but in fact the message is processed by the receiving server.   Pegasus Mail gets a failure and the mail is delivered by the host.  It should not deliver since there was a failure in the sending process but since it has the entire message it's not necessarily a bad thing.

Does it really? I'm only asking this because from an email from Martin

Ireland (concerning my post about images that sometimes show and

sometimes don't) I gathered that Pegasus extracts the html part

of a message and hands it over to bearhtml to display it. Depending on

exactly what this extracting involves, could it be that the html part

of the message is affected by Pegasus in some way?

In this case yes.  The raw view of the message was also truncated, and both BearHTML and the browser saw the same thing.  If so then the CNM file did not contain the missing part.  If the part was missing when received in the system then it was bad on the server as well.  There may have been some control codes in the message that caused the host to drop the end of the string.

Finally,  Yahoo does not even pay lip service to the e-mail HTML standards, as a web mail client it's too much of a bother I guess.  It appears that Yahoo thinks that if the HTML displays well in a browser it's good enough.

Thanks Thomas.

I will try the things that you mentioned.

Thankyou verymuch

kalu

We have been using Pegasus for almost 2 decades now.

Our hair is getting greyer by the day; not because of any intrinsic

problems with Pegasus ( which we sponsor) but because there appears to

be no thought given to file corruption, re-indexing or file

administration.

There is the utility MBXMAINT.exe that comes with v4.5 that will allow you to repair, reindex and compress users folders.  This must be done when the user is not running the program nor accessing the folders in any way.

FWIW, I do not know how to import mail from "Mailbag Assistant", does it have any sort of export capability??

You're absolutely right I had T(to) move to ?????? in Mail Filtering Rulles.

Thank you very much.

 I deleted that Now everything is fine.

 Don Cole

[quote user="irelam"]

Try opening an app like Microsoft Word and in a new document do a "Paste Special"  which should list all the data stored in the clipboard and its format.

A reboot should clear the Clipboard.   As for the problem it is likely bad Html not following the protocol for paste'ing Html.

Martin

[/quote]

It's all a lot easier to do: Just open the clipboard application (used to be in the Accessories folder of the Start menu, the excutable is [Drive]:\WINDOWS\system32\clipbrd.exe which you may start via Run command or in a console window if no shortcut is available): It has a menu (View?) listing all available formats of the clipboard contents and also provides an Edit menu for clearing etc. - no need to reboot anything or use non-default applications ...

I did not know that Gmail allowed that. I'll try changing my account settings when I have the time.

 

I'm using the address that my provider (NTT OCN) supplied to me when I signed my first contract with them. I never used it before because of the clunky interface, but it's nice to know that it came in handy now.

Too easy!! Thx

corrected. deleted file state.pmj and all good.

We nornally only see this problem if the drive, in our case x: is not mapped.  You need to check each system which is trying to access email to ensure your I drive is mapped to the right place or edit to use the URL instead and Thomas suggested.  I do  not think we have seen this specific message as a result or incorrect permissions but that is certainly worth a check too.

Bump

Still looking for some help with this. I would like to make sure i have the install done correctly before proceeding.

 

Hi.<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

We are running Netware 6.5 (OES2) servers, but using Pegasus only for POP/SMTP mail through our webmail client. When the user tries to run Pegasus, the splash screen appears, then go away without ever opening. We found one way to fix it was to re-install Windows, but that is not a great fix.

Today, I had another user call about their Pegasus not working. It’s doing the same thing that the other users were reporting. On this particular machine, I had just installed Microsoft networking in order to share out printers. When I uninstalled Microsoft networking, Pegasus worked. When I re-installed Microsoft networking, Pegasus didn’t work again. Is there some problem between Netware and Microsoft networking that would not allow this to run correctly?

 Thanks!

I had a similar problem on windows XP with Pegasus 4.61, eating up most of the CPU power. Now the fan comes to rest again.

In the german version it is: Extras -> Einstellungen -> Erweiterte Einstellungen -> Windows Internet Services laden -> immer.

 

Thanks for the help

 

Edmund