If you cannot sort out the SMTP you could try using DavMail if your company has Exchange Web Services running.

Well just doing a new install does work fine.

Both the server and the client machines installs of Pegasus Mail should be accessing the same home mailbox directory when signing in as the same user so both should display the lock warning.  The fact that the client doesn't is of concern.  Trust us when we recommend not accessing the same mailbox directory simultaneously.  If you do, keep backups handy.

I get the impression that when you began this endeavor you where trying to figure out your options and understand how things worked.  That is commendable but now that you have played with it I recommend the same as has SaliesBuzz.  In instances where there is a server and a client(s), the best option is to run the server install of Pegasus Mail from the client. 

Thanks Brian.

[quote user="jonm"]As I said at 5906 characters the line becomes invisible so I find your statement of 16kb doesn't match my reality.[/quote]

Becoming invisible doesn't necessarily mean you can't enter more. I just pasted in more than 6000 characters which made Pegasus Mail throw a (software) exception which didn't crash it, though. And if copying all of it back to my text editor it still contains all of them while I even can type in more (without the line end getting blank) ... But I can duplicate the error message when trying to send a message with such a long line. This might be an internal processing error (truncation for not exceeding buffer size), though, since the editor field seems to accept more characters.

Restarting did not solve the problem. I did a restore point from a from last week which seems to have solved the problem. Reinstalling the software updates which included one of the Visual C++ packs did not seem to break the Message Editor. Perhaps I had some malware keystroke monitor or something that slipped by the firewall and virus scanners. A full virus scan hasn't turned up anything.

Thank you very much...now it works...I used all of the suggestions except disable cram-md5 which I already knew needed to be enabled...thank you so very much

Tools | Internet options | Sending. Select your Verizon definition, then Edit.

Compare whats there with the settings provided to you by Verizon and take into account the info already provided to you through this forum.

Try unchecking the option to preserve deleted emails - Tools | Options | Basic settings.

[quote user="Bill@VT"]I have work-arounds, but wondered if all of you are interested in this potential problem and would want me to forward the e-mails (redirect them) for you to look at?[/quote]

 Sure, please do as advised in my previous replies.

Oh dear.  Please send me a copy of the entire email, so it can be reviewed for structure and syntax. The easiest way to do this is to open the message then click the Forward button, and enter my email address (irelam@telus.net). In the Forwarding method,  click the button that states "Forward the message without editing".  Then click the Forward button at the bottom of the screen.

Martin 

[quote user="KSQR"]

When I activated SpamHalter I ran into a major problem, namely a 250KB file attached to a message got trimmed to under 10KB  Got the file by having the sender resend it and using web mail to retrieve it.  Also noticed that my mail filter to move files with ***SPAM*** prepended to Subject to a separate folder also moved some messages without the ***SPAM*** prefix.

    POP3 serverside filtering rules (if any)
    Global whitelist (if any)

[/quote]

After rerunning the PM install file (v4,70), the problem went away.  :-)

After many years of using PM, I finally edited my global whitelist file, white.pm.  To make editing easier. started by sorting.  The file went from over 500 entries to 383.

KSQR

The only additional suggestion I have is to play around with deletion settings in your Gmail profile in Pmail, i.e. delete immediately etc, to see if that solves the problem.

Thanks Michael ... but the problem is resolved.

The guy with our central IT who installed the new  certificates on central mailhost went to a conference ... and forgot to enable a nightly reboot of our mailhost. His colleague didn't know about and said, there are no problems at all. I tested with Outlook and Thunderbird and they didn't have any problems. Than I wrote this message to the forum thinking Pegasus was the problem.

The problem was not Pegasus ... it was the not rebootet mailhost. It holds around 40.000 IMAP-Sessions and some of them (which haven't died in iterim) did have the old certificate, the others the new one. So depending on the IMAP-prozess answering on Pegasus requsts, Pegasus got the old or the new certificate. Because we enabled fingerprint tracking, everytime when certificate changed randomly Pegasus asked if it should refresh. Didn't recognize this.

Pegasus handles SHA-2 certificates correctly.

Sorry for hastily writing the message!

    Olaf

Brian,

Many thanks for your advice. Your third suggestion did the trick. There was a rogue (very large) .CNM causing the freeze.

I'm using Pmail 4.7 under Windows-XP.

Ron Hulme. 

Bingo!

Thank you again! 

You may also wish to consider running Pegasus Mail from the server hosting the mail data. That way you have just one installation of Pegasus Mail to administer. After the installation has been configured and tested you simply create a shortcut to \\servername\share\winpm-32.exe on each person's desktop.

At the moment, I can (i) use PMail in combination with Zonealarm, but then WinApps do not update, or (ii) use Windows Firewall, which allows WinApps update, but Pmail can't get through (this is the apps in Win 8.1 desktop, not Windows update itself, which is fine)

In Windows Firewall, I've added Pegasus Mail to Allowed Applications. Is there something else I need to alter/add? 

Thanks for the support .The solution was found on the other thread.

I have not received a copy of a bad message yet.  Have you given up?

Martin