[quote user="BMS"]Is there a solution, work-around or fix for this.
Also, any news on a long-awaited updated release?[/quote]
No news and some workarounds: The most reliable attempt of forwarding without anything getting lost at all is forwarding messages attached to a new message (allowing you to add your comments) as offered by the forwarding dialog. Aside from this, the actual formatting in outgoing messages is not properly shown in the reader when inserting you comments: To see how it will arrive at the recipient's side you need to queue your message, open the queue manager and create a copy of the outgoing message to some other folder (I usually use Deleted Messages if I don't want to keep a copy). If you open such a copy you will see how it actually looks when opened by your recipients.
That is IT, exactly. Thank you. I didn't realise I had the folders window in Preview mode because I had made it narrow to hide the preview pane, so the button to change to LIST mode was not visible.
I found it, switched it and now I can have those other options selected and the New Mail folder opens as it should.
Hi guys, thanks for your help. No, not using IMAP but POP3. It did work eventually, and all I did was to move the rule at the top of the rule list. But that's weird, for other rules I have there should not interfere with it. Anyways, I will test this with multiple rules and folders (for that is the whole point of going thru this trouble) and let you know if any more problems. Thanks again.
I'm not a fan of Win10 either. Much preferred Win7. Give Win10 a chance though. It' not terrible; it just takes getting used to and a lot of time researching how best to make it work like you think it should work rather than the way MS thinks we should want it to work.
I've now tried C:\PROGRA~2\MICROS~1\OFFICE14\WINWORD.EXE, C:\PROGRA~2\MICROS~2\OFFICE14\WINWORD.EXE, C:\PROGRA~1\MICROS~1\OFFICE14\WINWORD.EXE and C:\PROGRA~1\MICROS~2\OFFICE14\WINWORD.EXE with no success. I'll stick with what I've got - it's just I don't like mystery problems!
When just talking about wishes: I would like to have the oppotunity to delete also folders which contain subfolders with mails therein. In Germany we have to keep all business e-mail conversations of the last 10 years. That's why we maintain single mailfolders for each single year. But our users additionally create different subfolders for each year folder. And every new year I have to tidy up my user's Pmail accounts deleting those year folders which are older than 10 years. And this is a high time consumption process when you imagine about 18 users with about 10 to 20 subfolders per year folder.
I think I've solved this issue with another message resulting in similar crashes when forwarding or replying to HTML messages with inserting the HTML into the respective TER window. Since Pegasus Mail provides any HTML it processes to the active HTML renderer for correcting issues which might crash TER I found out supported by Martin Ireland what he was doing differently with BearHtml. After modifying my processing accordingly I don't see these crashes anymore. Expect to see an IER update (providing filxes for other issues as well) soon.
For the moment I have cancelled the printer distribution by Windows Group Policy Object. Guys in different Windows forums do not recommend this approach because it doesn't work sufficiently. Now I have installed the network printer manually again. Will see what happen.
Using the printers as local TCP/IP printers would be my very last attempt, if nothing else works for all.
The only messages I'm concerned with trying to get into someones hands are the ones unread from the last time the President left the office to the time I enabled forwarding. That's why the newmail filter rule came to mind. If filtering to a directory was an option I would do away with the forwarding and just keep an instance of his Pegasus Mail running minimized somewhere. Placing messages in a directory would keep it out of other users mailboxes and I could control access with permissions. Olaf's idea of adding a mailbox just for these messages is valid but requires more effort than the issue is worth.
I've written the directory idea off as wishful thinking and am fine with closing this inquiry.
I did it this morning. Now I will see whether it has solved it.
But since we have upgraded our old Windows Server 2003 to Windows Server 2016 we experience also other oddities, where e.g. printer go offline - but only at one workstation while other users have no problem with the network printers.
I take another cup of coffee and will wait ... [C]