"Could not communicate with Pegasus Mail"

irelam

posted Nov 5 '18 at 10:40 pm

Some more info on DDE:

https://office-watch.com/2017/dde-finally-dead-took-microsoft-long/

Martin

Some more info on DDE:https://office-watch.com/2017/dde-finally-dead-took-microsoft-long/Martin

mikepe

posted Oct 28 '18 at 11:57 am

Hi, all

I'm running Pegasus Mail Version 4.73.639 under Windows 10 64-bit.

I have set PM as my default email app. In the list of such apps it is identified as "Pegasus Mail WSENDTO Utility". I presume that that is standard; I cannot see any way on the "Default apps" screen to change it to winpm-32.exe, for example.

However, when I attempt to open PM from another app (in this case, it is a new PIM in beta development called HandyPIM) -- for example, to attach and send a bug report -- I get the attached error message.

HandyPIM's developer has attempted to reproduce my problem, using Win10 and PM, but it worked fine for him.

Any suggestion to fix this would be most welcome!

Mike

Hi, allI'm running Pegasus Mail&nbsp;Version 4.73.639 under Windows 10 64-bit.I have set PM as my default email app. In the list of such apps it is identified as "Pegasus Mail&nbsp;WSENDTO Utility". I presume that that is standard; I cannot see any way on the "Default apps" screen to change it to&nbsp;winpm-32.exe, for example.However, when I attempt to open PM from another app (in this case, it is a new PIM in beta development called HandyPIM) --&nbsp;for example,&nbsp;to attach and send a bug report -- I get the attached error message.HandyPIM's developer has attempted to reproduce my problem, using Win10 and PM, but it worked fine for him.Any suggestion to fix this would be most welcome!Mike&nbsp;

Michael

posted Oct 28 '18 at 1:07 pm

[quote user="mikepe"]I'm running Pegasus Mail Version 4.73.639 under Windows 10 64-bit.[/quote]

Did you ever run Pegasus Mail's installer on this system (instead of just copying it from another machine or keeping it as is during a major Windows update)? If not this would be the first thing to do, after a major Windows update this might be helpful as well. Just run it as an update over the current version, even if you already have the most recent version installed.

[quote user="mikepe"]I'm running Pegasus Mail&nbsp;Version 4.73.639 under Windows 10 64-bit.[/quote]Did you ever run Pegasus Mail's installer on this system (instead of just copying it from another machine or keeping it as is during a major Windows update)? If not this would be the first thing to do, after a major Windows update this might be helpful as well. Just run it as an update over the current version, even if you already have the most recent version installed.

			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

mikepe

posted Oct 28 '18 at 1:31 pm

Thanks, Michael. I'll give that a try. I did install it fresh on to the current system; but inevitably there have been Windows updates since then.

Mike

Thanks, Michael. I'll give that a try. I did install it fresh on to the current system; but inevitably there have been Windows updates since then.Mike&nbsp;

David_himself

posted Oct 28 '18 at 1:55 pm

Is it possible that you have been affected by the October updates to Win10? I'm still OK with Pegasus, but when I updated Oxygen and Notepad++ last week I found I couldn't change the default app for .xsl files back to Notepad++. If you search the internet, you will find a ton of complaints that Windows no longer allows the changing of default apps. Presumably it's an accidental bug that MS will fix in November. One hopes that's November 2018.

best

David

Is it possible that you have been affected by the October updates to Win10? I'm still OK with Pegasus, but when I updated Oxygen and Notepad++ last week I found I couldn't change the default app for .xsl files back to Notepad++. If you search the internet, you will find a ton of complaints that Windows no longer allows the changing of default apps. Presumably it's an accidental bug that MS will fix in November. One hopes that's November 2018.best&nbsp;David&nbsp;

mikepe

posted Oct 28 '18 at 3:18 pm

Hi, David

It's quite possible. For better or for worse, I've left Windows 10 on automatic update...

Mike

Hi, DavidIt's quite possible. For better or for worse, I've left Windows 10 on automatic update...Mike&nbsp;

mikepe

posted Oct 28 '18 at 7:10 pm

[quote user="idw"]

[quote user="mikepe"]I'm running Pegasus Mail Version 4.73.639 under Windows 10 64-bit.[/quote]

Did you ever run Pegasus Mail's installer on this system (instead of just copying it from another machine or keeping it as is during a major Windows update)? If not this would be the first thing to do, after a major Windows update this might be helpful as well. Just run it as an update over the current version, even if you already have the most recent version installed.

[/quote]

Hi, Michael

I've just re-installed PM, but there's no change. Maybe I need to restart the computer?

Or maybe (as David suggested) it's a Windows bug...

Mike

[quote user="idw"][quote user="mikepe"]I'm running Pegasus Mail&nbsp;Version 4.73.639 under Windows 10 64-bit.[/quote]Did you ever run Pegasus Mail's installer on this system (instead of just copying it from another machine or keeping it as is during a major Windows update)? If not this would be the first thing to do, after a major Windows update this might be helpful as well. Just run it as an update over the current version, even if you already have the most recent version installed. [/quote]Hi, MichaelI've just re-installed PM, but there's no change. Maybe I need to restart the computer?Or maybe (as David suggested) it's a Windows bug...Mike&nbsp;

irelam

posted Oct 28 '18 at 11:24 pm

The error message suggests that WSendto cannot call Pegasus Mail using DDE protocol.Firstly please ensure that Pegasus Mail is up and running, then repeat the WSENDTO invocation.

Also try starting MS Word and with a document open go to the File menu and select Sendto. Below that menu select Send TO Pegasus Mail. You should see a Pegasus Mail editor screen that allows you to alter things like fonts etc. Press Send and it should work. You can also try running WPMMAPI.EXE in c:\pmail\programs that will setup the DDE protocol inside Pegasus Mail.

I have had numerous problems since the Windows Update. Nearly all have bee resolved after reinstalling software products

Martin

The error message suggests that WSendto cannot call Pegasus Mail using DDE protocol.Firstly please ensure that Pegasus Mail is up and running, then repeat the WSENDTO invocation.Also try starting MS Word and with a document open go to the File menu and select Sendto.&nbsp; Below that menu select Send TO Pegasus Mail.&nbsp; You should see a Pegasus Mail editor screen that allows you to alter things like fonts etc. Press Send and it should work.&nbsp; You can also try running WPMMAPI.EXE in c:\pmail\programs that will setup the DDE protocol inside Pegasus Mail.I have had numerous problems since the Windows Update. Nearly all have bee resolved after reinstalling software productsMartin &nbsp;&nbsp;&nbsp;

bfluet

posted Oct 29 '18 at 12:40 am

Steps that usually get Pegasus Mail fully functional on Win10 are to run the Pegasus Mail installer or the SETPMDEFAULT.EXE utility and then set the default email app and the MAILTO protocol to the Pegasus Mail WSENDTO utility.

Steps that usually get Pegasus Mail fully functional on Win10 are to run the Pegasus Mail installer or the SETPMDEFAULT.EXE utility and then set the default email app and the MAILTO protocol to the Pegasus Mail WSENDTO utility.&nbsp;

mikepe

posted Nov 2 '18 at 4:27 pm

Hi, thanks for the suggestions.

I retried the WSENDTO invocation, but with the same result.

My version of word (2007) doesn't have that set of menus. I tried using the 'Send' options, but Word only told me that I needed to log onto MS Exchange.

I tried running WPMMAPI.EXE, but the system said I couldn't run it on my device.

I have also tried running setpmdefault.exe, as suggested below, but again, nothing has changed. WSENDTO is still the default mail app (as I presume it should be), but the error message persists.

The struggle continues :-)

Mike

Hi, thanks for the suggestions.I retried the WSENDTO invocation, but with the same result.&nbsp;My version of word (2007) doesn't have that set of menus. I tried using the 'Send' options, but Word only told me that I needed to log onto MS Exchange.&nbsp;I tried running&nbsp;WPMMAPI.EXE, but the system said I couldn't run it on my device.&nbsp;&nbsp;&nbsp;I have also tried running&nbsp;setpmdefault.exe, as suggested below, but again, nothing has changed. WSENDTO is still the default mail app (as I presume it should be), but the error message persists.The struggle continues :-)Mike&nbsp;

Brian Fluet

posted Nov 2 '18 at 4:49 pm

Yup. MS Office is a different beast. There is a way to add a macro in NORMAL.DOT that you can then add to the Quick Toolbar which will allow you to send using Pegasus Mail. I haven't done it in a long time but I still have the notes about it. If you care to give it a try send me a PM with your email address and I'll be happy to copy you on my notes.

BTW, my apology to all for posting as two different users. Do to an email hosting issue I switched to an old profile and now feel stuck with one foot on either side of the tracks. I hope to get it sorted out soon.

Yup.&nbsp; MS Office is a different beast.&nbsp; There is a way to add a macro in NORMAL.DOT that you can then add to the Quick Toolbar which will allow you to send using Pegasus Mail.&nbsp; I haven't done it in a long time but I still have the notes about it.&nbsp; If you care to give it a try send me a PM with your email address and I'll be happy to copy you on my notes.BTW, my apology to all for posting as two different users.&nbsp; Do to an email hosting issue I switched to an old profile and now feel stuck with one foot on either side of the tracks.&nbsp; I hope to get it sorted out soon.

irelam

posted Nov 3 '18 at 3:49 am

Brian

Further to the thread on sendto\wsendto\ms-mapi etc etc I already posted a number of Urls from Microsoft Dev database. I checked on my own home system and get the same error message, which indicates that the DDE service is not active. A number of these articles on problems like this indicate that either MsExchange or Outlook should be active to supply the DDE. Well I did not install either of these products on my Windows 10 64-bit system right from the switch to Win 10. I have not seen this problem till very recently (post October maintenance release).

What scared me was that Microsoft in their articles promoted first a command then a registry update, to disable DDE. They followed up with an example on re-enabling DDE.. Several users complained that the re-enable did not work on their systems, and are demandng that DDE be re-enabled. Microsoft's response was to say "no" as it was a security risk, and further that users should convert to the OLE DB database system for exchanging data. Well I don't have OLE services installed on my system, and neither do I want to learn OLE coding techniques across applications that don''t have OLE functions built in already. Until Microsoft deals with this problem DDE, there is little hope of cross-application linking of data or commands.

The only temporary solution I can see, is to use email file transfers via export then import to a target machine. Or to use shared locked memory or disk dataset. Either way this is problematic.

More later.....

Martin

Brian&nbsp;&nbsp; Further to the thread on sendto\wsendto\ms-mapi etc etc I already posted a number of Urls from Microsoft Dev database. I checked on my own home system and get the same error message, which indicates that the DDE service is not active.&nbsp; A number of these articles on problems like this indicate that either MsExchange or Outlook should be active to supply the DDE. Well I did not install either of these products on my Windows 10 64-bit system&nbsp; right from the switch to Win 10. I have not seen this problem till very recently (post October maintenance release).What scared me was that Microsoft in their articles promoted first a command then a registry update, to disable DDE. They followed up with an example on re-enabling DDE.. Several users complained that the re-enable did not work on their systems, and are demandng that DDE be re-enabled.&nbsp; Microsoft's response was to say "no" as it was a security risk, and further that users should convert to the OLE DB database system for exchanging data.&nbsp; Well I don't have OLE services installed on my system, and neither do I want to learn OLE coding techniques across&nbsp; applications that don''t have OLE functions built in already.&nbsp; Until Microsoft deals with this problem DDE, there is little hope of cross-application linking of data or commands.The only temporary solution I can see, is to use email file transfers via export then import to a target machine.&nbsp; Or to use shared locked memory or disk dataset. Either way this is problematic.More later.....Martin &nbsp;

Brian Fluet

posted Nov 4 '18 at 1:38 am

Martin, do I understand that what you are saying is that the Word macro you created for Word 2007 (which I then used as the basis for creating one for Excel) will not work when running on Win10?

irelam

posted Nov 4 '18 at 6:27 pm

You are right. I just tested again on my Win 10 64-bit. No connection message still. DDE is dead or disabled. :-( I also checked my MAPI inteface utility, which uses DDE and it too failed to connect.

Martin

You are right. I just tested again on my Win 10 64-bit.&nbsp; No connection message still.&nbsp; DDE is dead or disabled.&nbsp; :-( &nbsp;&nbsp; I also checked my MAPI inteface utility, which uses DDE and it too failed to connect. Martin

irelam

posted Nov 5 '18 at 10:36 pm

Just some more info on the DDE problem, see:

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV170021

It seems likely that you need to be running wither Microsoft Office or Microsoft Exchange Server, to get DDE

See the following link for a non-Microsoft view on DDE

https://blogs.sas.com/content/sasdummy/2014/10/14/dde-is-doa/

Martin

Just some more info on the DDE problem, see:https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV170021 &nbsp;It seems likely that you need to be running wither Microsoft Office or Microsoft Exchange Server, to get DDE &nbsp;&nbsp;&nbsp;&nbsp; See the following link for a non-Microsoft view on DDEhttps://blogs.sas.com/content/sasdummy/2014/10/14/dde-is-doa/ Martin

Related Topics

Pending draft

Confirm move posts

Insufficient permissions

Select a different topic

Edit history