Hi Michael,

  Just to let you know I have downloaded this document set already.  The format is extremely complex, and I really don't think I can cope with fathoming out what Microsoft is trying to achieve. I have obtained the pointers to the various sections of a DOCX file and I know the headers for PDF and ZIP files, as well as standard *.doc files. So I will try an experimental version of Mapipm to extract these files programatically.

I have located the blocks that contain the email message header lines and body content as well, so I may be able to re-constitute the original email message, or close to it.

That being said this will likely take some time.

 Martin

If that works to satisfactions I will then work on other filetypes like *.XLS etc

Hi Guys,

I could not imagine that this was never be asked until now, but the search didn't return any results in this regard.

How I could make "mailto:" links working with Pmail? We are mainly using the current version of Firefox and I'm aware that I have to go to the firefox settings to assign Pegasus for "mailto:" links. But it doesn't work. BTW, our Pmail installation is on a server where different users are starting their own Pmail session from the same location. Means, when starting Pmail, the option -i <local_username> has to be added to the path. But I'm not able to add the user name as an additional option within the firefox settings. Also in case Pmail is already started and I click a mailto: link (where Pmail is added within firefox settings but without local user option) - nothing happens. Has anybody a clue or is it impossible?

Cheers

Joerg

Greetings Joerg,

In the OS, the Pegasus Mail WSENDTO Utility needs to be set as the default for the mailto: protocol.  It won't be available as an option to the OS if the appropriate registry entries don't exist.  If that's the case, run WSSETUP.EXE one each workstation (if you didn't already), followed by SETPMDEFAULT.EXE.  You should then be able to select Pegasus Mail WSENDTO Utility as the default for mailto:.

Hi Brian,

Thanks for the hint. Now I remember the wsendto utility. Great. I will test it tomorrow.

It seems I have to create my own Pmail Wiki here, where I save such important things. Otherwise they are getting lost in my mind. ;-)

Greetings

Joerg 

[quote user="Joerg"]It seems I have to create my own Pmail Wiki here, where I save such important things. Otherwise they are getting lost in my mind. ;-)[/quote]

I know exactly what you mean.  I now have two different Pmail "Wikis".  One at the office maintained on an app called Treepad Lite.  The other is on the flash drive from which my support instance of PMail runs.  It's made up of a bunch of .txt files.  Treepad Lite is an awesome tool for freeform note making.  OTOH, the .txt file approach needs some work. :-)

Hi Brian,

Standard internet "mailto:" links are working again. Fine so far. Thanks again. I have directly made a new entry into our DokuWiki to rescue this information from fading out [:S]. The DokuWiki which we are using is a simple to use and highly versatile Open Source wiki software that doesn't require a database. But of course, all users have to be familiar with the syntax, which differs from html (https://dokuwiki.org)

But one issue remains in connection with mailto: links:  We often have to login into an online document management system of one of our customers. Therein you can select different files. When all needed things are collected you can click on a button "Send by E-mail". This causes that Outlook is being started and the selected files will be handed over and directly attached to a new e-mail. As far as I can see, a ".msg" file will be handed over to Outlook. I have changed Windows preselections in that manner that also msg files are assigned to Pegasus, but unfortunately it doesn't work. Pegasus doesn't start. Now we are thinking about to install Outlook (additionally to Pmail) with a separate E-mail address. But this is not my favorite way.

Cheers

Joerg

[quote user="Joerg"]But one issue remains in connection with mailto: links:  We often have to login into an online document management system of one of our customers. Therein you can select different files. When all needed things are collected you can click on a button "Send by E-mail". This causes that Outlook is being started and the selected files will be handed over and directly attached to a new e-mail. As far as I can see, a ".msg" file will be handed over to Outlook. I have changed Windows preselections in that manner that also msg files are assigned to Pegasus, but unfortunately it doesn't work. Pegasus doesn't start. Now we are thinking about to install Outlook (additionally to Pmail) with a separate E-mail address. But this is not my favorite way.[/quote]

I don't exactly remember whether MAPIPM is installed by default with Pegasus Mail, but it's very likely the missing link. You can download it from Martin's tools page, it should provide further instructions and you may need to run SetPMDefault again after putting the DLL file into its proper place.

Moin Martin,

Thanks for the link. Sounds good. I will test it and come through with the result.

Gruss aus Rostock

Joerg

Hallo Martin,

Just downloaded and replaced the existing mapipm.dll with the newer one from Martin's tool page. The dll has been placed at the server drive where our multi-user Pmail installation resides (\\server\Pmail$\Programs\). Further I have checked that the registry key for Pmail is in place at my workstation. Nevertheless I have also executed the SetPMdefault.exe again.

But finally any file handing-over to Pmail fails. When trying to use the Windows Explorer right click "send to:" functionality as recommended for testing by Martin, the Windows Explorer returns the error: "The file or folder "wsendto.exe", where the link relates to, could not be find. Sound like a link problem, but standard "mailto:" links are working.

Jeorg,

Check the sendto link on the PC...

C:\Users\{YourUsername}\AppData\Roaming\Microsoft\Windows\SendTo

For the Pegasus Mail option I have:

Pegasus Mail.LNK with a target of H:\PMAIL\WSENDTO.EXE

There is also a Mail Recipient.MAPIMail entry.  You can specify the "opens with" app in it's properties.  I haven't encountered a need to mess with this so mine is not specified.  I assume it should point to wsendto but don't know for certain. 

Hi Michael and Brian,

It becomes better more and more...  [:)]

And although the Mailto standard in Windows has been set by SetPMdefault, the link at C:\Users\{YourUsername}\AppData\Roaming\Microsoft\Windows\SendTo was still wrong. After setting it to the server share where Pmail resides, the "Sendto:" function in Windows (e.g. from Windows Explorer context menu) works and hands over the selected file as an attachment to Pmail. Good so far. Thanks Brian for the link.

But back to the Customer's Online Document Management System: When trying to send the selected files by mail, the system still creates a msg file (e.g. data.msg) which will be handed over to Pmail right now. Pmail starts, creates a new mail where this msg file is attached. Fine so far, but nobody is able to read this "msg" file.

It seems this Customer Document Management System is only programmed for collaboration with Outlook. That's why it doesn't hand over the original files but creates a msg file which contains all single files.

[quote user="Joerg"]But back to the Customer's Online Document Management System: When trying to send the selected files by mail, the system still creates a msg file (e.g. data.msg) which will be handed over to Pmail right now. Pmail starts, creates a new mail where this msg file is attached. Fine so far, but nobody is able to read this "msg" file.

It seems this Customer Document Management System is only programmed for collaboration with Outlook. That's why it doesn't hand over the original files but creates a msg file which contains all single files.[/quote]

Gotta love software that requires specific third party apps.  I have a contract job billing app that requires Outlook to email documents and an accounting app that requires Adobe Reader to view documents as pdf.   Luckily I can save the documents as pdf files and work with them from there.  That's probably not an option or not practical in the online system you're dealing with.

I don't know how your system is set up, but if Wsendto.exe cannot be found, that seems to indicate that Wsendto.exe is not in c:\pmail\programs directory.  You could put it in a directory that is listed in your PATH environmental variable (control panel/system/advanced settings/environmental variables).

As to what MSG files contain, I cannot comment without an example being sent to me (irelam17@telus.net). I no longer have an Microsoft Outlook client to use to test these links.

 Martin.

From what I can gather, a .msg file contains the entire message content (headers,body, & attachments).  I suspect the .msg extension gets associated with Outlook during installation.

I wonder whether a .msg file could be converted to a .101 file that Mercury could send.  Unfortunately that's way above my level of knowledge.

[quote user="irelam"]I don't know how your system is set up, but if Wsendto.exe cannot be found, that seems to indicate that Wsendto.exe is not in c:\pmail\programs directory.[/quote]

In the meantime, as stated above, Window's sendto: path has been adjusted to the server share where wsendto.exe resides. And it works now.

[quote user="irelam"]As to what MSG files contain, I cannot comment without an example being sent to me (irelam17@telus.net).[/quote]

I try to provide you with such an example msg file tomorrow.

contains the entire message content (headers,body, & attachments).  I

suspect the .msg extension gets associated with Outlook during

installation.

I wonder whether a .msg file could be converted to a

.101 file that Mercury could send.  Unfortunately that's way above my

level of knowledge.[/quote]

I think so, Brian. We have send a query to the creator of that document management system (called DocMap). But I'm afraid their system could only provide such msg files.

In Germany (and Europe) we have changed the clock to summer time last week. And today there is the first day of about 17°C. [H] Should be about 62.6 °F, if I calculate correctly. Could think about a first little barbecue. Nice after office hours and until tomorrow.

Cheers

Joerg

Just a short note about SetPMDefault: It only sets proper Registry entries based on a local Pegasus Mail installation, and you need to run it with elevated access rights (Admin). I don't know whether this handles client/server environments properly.

[quote user="idw"]Just a short note about SetPMDefault: It only sets proper Registry entries based on a local Pegasus Mail installation, and you need to run it with elevated access rights (Admin). I don't know whether this handles client/server environments properly.[/quote]

I believe it does.  I recall determining that running wssetup followed by running setpmdefault was the most certain to setup a workstation with pmail as the default mailer.  On recent installs I noticed that wssetup prompts to set up pmail as the default mailer.  This has worked so haven't needed the setpmdefault step.  I'm now wondering why it was needed.  A new version of wssetup came with v4.61 so perhaps that is when things changed.  If so, that was 7 years ago (it feels like 2).  Regardless, I'm pretty certain that I have run setpmdefault to resolve default mailer issues on workstations.  I don't remember when last did it though.  It could be that running wssetup again would accomplish the same thing.

I assumed wssetup was invoking setpmdefault when setting pmail as the default mailer but we all know about that word "assume".

When preparing a new user workstation I normally manually create a desktop shortcut for Pmail only and that's it. All other things will be adjusted at the server. To change Windows standard mailto link, yesterday I've made both, wssetup and setpmdefault. This works so far and set the necessary registry keys as well as the necessary "mailto:" settings in Firefox (wsento utility chosen). But Window's "send to" link (C:\Users\{YourUsername}\AppData\Roaming\Microsoft\Windows\SendTo) remains unchanged and has to be adapted manually.

@Martin: now I've got such an Outlook msg file for you which contains an image and a Word file I think. I will send this template by mail to you in a few seconds.

Received the file, thank you. I discovered that the MSG file is a compound file structure call DOCX. Owner of Microsoft Office can create/read/delete these files easily. That being said those of us who don't use Microsoft Office, especially MS WORD, are pretty much out-of-luck. Solution is to get the originator to send out the components of the DOCX separately as standard attachments.

PS the Microsoft utility WordViewer which could read MSG files, is being withdrawn this month :-(  The existing Wordviewer (2003-2008 vintage) will not read the latest Microsoft Outlook MSG attachments, and OpenOffice and LibreOffice, have poor support for the latest MSG files.

Martin

[quote user="irelam"]I discovered that the MSG file is a compound file structure call DOCX. Owner of Microsoft Office can create/read/delete these files easily. That being said those of us who don't use Microsoft Office, especially MS WORD, are pretty much out-of-luck. Solution is to get the originator to send out the components of the DOCX separately as standard attachments.

PS the Microsoft utility WordViewer which could read MSG files, is being withdrawn this month :-(  The existing Wordviewer (2003-2008 vintage) will not read the latest Microsoft Outlook MSG attachments, and OpenOffice and LibreOffice, have poor support for the latest MSG files[/quote]

Hi Martin,

I agree, the msg file, I've sent you, is of a compound structure - but didn't contain only a MS Word docx file. This docx MS Word file was only one of the files therein. Other files within this msg file were a pdf and two jpg files. When opening this msg file with Outlook, it will be directly converted back into single attachments (1 pdf, 1 docx, 2 jpg). But I don't want to use this bloody Outlook (or other software) for getting back the original attachments from the msg file. This would be a big effort since we have to regularly send messages from out of the DocMap system. An every time this system creates a msg file which we, of course, could open with Outlook, followed by saving of the restored single attachments, followed by opening of Pmail and attach the restored files to a new mail.

That's why I had hoped the MAPIPM could be adapted that it is able to convert Outlook msg files back to its original files which will be attached to a new Pmail message. If this is not possible, I have to setup an additional Outlook (for that user) for processing of these msg files directly.[:(]