KSQR,

I'm happy to report your help did the trick, so thank you so much !

Thank you for the very quick reply

Yes I have version 4.72.572. build 5.72 I have used your message reader options and the message seem to open

but I will keep your crash post for future use.

Thank you and the other helpful Pegasus  support team it is AND has been most helpful

Yes, did that. Thank you.

So I now know, having belatedly had a look. Thanks.

Pegasus Mail will run fine on a 64-bit machine.  I have an office full of them (Win7) and a laptop at home (Win10 Home).

Many thanks. I've been using PM for about 20 years but never knew mbxmaint_ui.exe existed! It works fine on the samples I've tried.

[quote user="Ralph B."]AS PGP is apparently not readily available?[/quote]

No idea what you're trying to say here, but aside from the link provided by Martin: PGP can either be used as kind of a "proxy" if you pay for it (called messaging in the screenshot below) or as a free version with my extension after downloading a trial version of its (down that page). See below for the feature the free version provides.

Thank you so much. That thread helped me fix the problem.

Solved after a new installation in a new folder.

[quote user="Niall Martin"]I find this a persistent problem. [/quote]

IMAP overhaul is still one of the major tasks for PM v5 since there are lots of "construction sites" like yours to deal with.

Use AutoHotKey to send an email via commandline will work. Have used this method to send a generated file from a database export three times daily without a problem.

The scripting is fairly simple to learn.

 https://www.autohotkey.com/

[quote user="ddmartin"]I want help you, but I do not want send my password....[/quote]

You can use PGP for encrypting attachments for ensuring privacy, my key ID can be found below in my signature. There's even a helping with encrypting messages.

[quote user="PaulW"]Do you mean being altered when they forward/reply to it?  I can't quite imagine why your mesage should be changed in that instance. [/quote]

The wrapping of cell content is the major issue but I will copy table content out a message for pasting into Excel so picture that being done by my message recipients as well.

[quote user="PaulW"]Is creating your own table using Pegasus' html capability too long-winded to be of use?[/quote]

Yes.  Six columns, often +30 rows. 

Perfect. Thanks, Brian.

My antivirus no longer actively scans the C:\PMail\Mail folder, but the crashes and restarts persist. I gather from Michael in der Wiesche that Pegasus version 4 has various problems with IMAP. Nothing to do but avoid IMAP, start using DavMail again, or wait for Pegasus vsn 5. I'm too busy at the moment to start playing with DavMail again, so I'll struggle along with this annoyance and hope that PMail 5 comes along before too many months or years.

David 

WORKING!, in a workaround sort of way.

There were two problems:

1.  As you said, there was a problem with the username.  It was in the format "user", but in PM it wanted "user@domain.com".  The fastmail people checked this on a screenshot, and didn't catch it.

2.  There also seems to be an SSL problem:  They told me to try "insecuressl.messagingengine.com" instead of one of their normal servers, such as "imap.fastmail.com".  "insecuressl" uses an older version of SSL.

With the two changes together it started working, though neither alone worked.

Thanks a lot, everyone!

Please make sure you are using Mapipm.dll version 1.9.3 dated Mar 26, 2014, as this appears to fix your problem. I discovered a previous user had this problem, which has now gone away. You should be seeing a Pegasus Mail compose message screen with no recipients in the To: field, which you can now add.

You can download version 1.9.3 from;
http://community.pmail.com/files/folders/pegadd/entry40687.aspx

Martin

[quote user="DesGordon"]I've sent a mail as requested[/quote]

Thanks, I'll take a look as time permits.

Looking back at your original thread I noticed that you are using several anti-virus and malware utilities. Any one of these may probably be the problem, as the error condition suggests that this is a nearly random occurence. I would suggest you check these products to disable scanning by them of the Pegasus Mail directories, especially the NewMail directory. You should also add the directory defined as the TEMP directory in the system, usually c:\temp or a directory under your userid (see Pegasus Mail menu Help, About Pegasus Mail then click Info).

Martin

[quote user="tomdriver"]The dmp file is not inside Pegasus.  Never was.  It is a file on my desktop, namely 2016-10-31#19-02-13.dmp              200 KB[/quote]

Of course not, but there should be an auto-saved message in the draft manager with the CAB-compressed DMP file as attachment. And even if the file type would be accepted by the forum it wouldn't accept a file larger than 64 KB which even compressed DMP files usually exceed.

[quote user="tomdriver"]Thanks for help.  Pegasus continues to generate the "Access violation" errors every few minutes, and I have to restart the program to cure it for a short while.[/quote]

Now with knowing that the DMP file was stored on your desktop I start to feel that your system appears to have a weird setup which might also explain the Pegasus Mail issue you have: The DMP files should be stored in you system's TEMP folder and compressed to a CAB file. Pegasus Mail's (menu entry) Help => About Pegasus Mail => Info screen shoud show where this folder is, and this info should be sent along with the DMP file (if not posted here) as well.