Unfortunately there is no easy way. As you know, in Outlook each user has their own Id and password. The only simple way you could achieve this is to collect a file of all your users Ids and passwords, as the process requires a login. Not a good idea at all. At present this individual login is achieved by the Pm2msm.ini values, but with a little work I could force a login dialog. But that would require user participation. [:(] Hmmm...
You are not using Norman perhaps? This is similar to my problem http://community.pmail.com/forums/thread/942.aspx , just the invalid errorcode is different, a 6 instead of 2, but both invalid according to David.
Someone suggested that I swap in another NIC to see how it affected this hanging problem. I didn't have one handy so instead I updated the drivers for my existing one (an old Netgear FA311) and that seems to have done the trick! I can now forward those particular HTML-formatted emails without killing my network connection and hanging the computer. I guess the old drivers were either defective or corrupt.
So, perhaps my blaming Pegasus was misplaced. It still seems odd to me that Pegasus is the only network program of the many on this computer that would trigger the symptom.
Personally I setup addressbooks and dist. list using a full SMTP address in the form "FirstName Lastname"<firstname.lastname@example.org> This way the username is part of the email address and the address is fully definitive no matter how it's delivered. In addition I use the Mercury/32 PH server pointing at the system addressbook so that the POP3 users of Pegasus Mail can also access this addresbook. One of these days there will be a LDAP server as well so that will add a lot more capability for a number of other email clients.
[quote user="Correlator"]If you don't get such messages too often, save it into a file with extension *.b64 and then use, for example, WinZip to "open" it. WinZip will show its contents as a couple of text files. One of them will be your message in plain text format, which you can extract and read in Notepad etc.[/quote]
Thanks! Your suggestion works.
It is an adequate workaround because I only receive these problem emails occasionally.
Just on this last point. Why would anyone want to read/capture a file that was in read/write mode by some other process? This indicates that the file has a strong possibility of being updated. The Read-only version (yes Word/Excel are guilty) is then only an approximation to the current version of a file. This kind of thing is most common in my work when two or more people on a network are sharing and updating data.
You're right Martin but sometimes users need to do some things we didn't think they could have to do. For example, it happens to me quite often to be happy to have the feature "open a file in read-only mode because it's already opened by word or excel" (I made a lot of changes and suddently realize that I want to keep a copy of the original).
A good solution could be to warn the user that the file is in use and ask him/her to confirm he wants to attach the current version to his/her mail.
> This strange behavior is occurring on a brand new IBM Thinkpad with really nothing unusual added.
There's indeed a strange glitch according to Pegasus MDI when used with IBM Trackpoints:
Thinkpad Trackpoints can (and are by default) be configured to use for scrolling through the page. To scroll that way one has to press the middle "UltraNav"-Key and simultaneously press the trackpoint into any direction. Other than "normal" Windows behaviour this scrolling always triggers on the window beneath the current trackpoint position, even it's not the active window. Furthermore the Trackpoint pressure will be recalculated to control both the horizontal and the vertical scrollbar at the same time which means that one may scroll diagonally, too.
So far for the technical background, what I wanted to say is that it's not a "normal" scrolling technique which therefore cannot be compared with "normal" scrollwheel-mice.
The glitch now seems (only) to happen when this scrolling is invoked inside the window of PMail MDI on an empty window position where no child window is placed. Then the main area will be resized, the child windows will "scroll away" and scrollbars will appear even if they were not available before. It looks like that instead of any MDI child window (because at the scroll position there's none) the whole main area with all the other child windows will be scrolled (away).
Since I use Pegasus in full screen mode and have arranged a couple of used windows (mail folders) to fill all available space that Trackpoint-Phenomenon does not happen anymore, at least not unintentionally.
Finally, if it ever happens that folder windows became out of sight in PMail, there are two ways to repair:
1. The hard way: Kill the application task hard using the "Tasks" tab in the Task Manager to
prevent it from saving its configuration files with the
"wrongly-scrolled" window coordinates. Keep in mind that all other
configuration changes done in this session might be lost, too.
2. The soft way: If the wrong coordinates are already saved by any reason, you must select each open folder window in PMail itself under menu item "Windows" and first close it by pressing ESC before reopening later after all windows have been closed. After closing the last out-of-sight-window the (unusable) scrollbar will go away automatically. To "repair" the global folder window you can also directly edit the file pmail.ini - Close PMail before! - and adapt the coordinates stored in "[Pegasus Mail for Windows] / Folder manager window rectangle" to some small values (left upper corner). But always save a backup of at least this file or at best the whole mailbox directory before editing this file, since mistakes in that file might make things worse. Anyway I do not recommend to manipulate this file manually if you can not oversee the consequences...
Something similiar happens to us from time to time. Pegasus looses its internet settings. You have to write your e-mail adress again and add back pop and smtp definitions. At our site this happens roughly 1 time per year and per pc. All are running pegasus 4.4.1 in german with f-prot as antivirus scanner. By the way as this happened to me in some cases I googled this problem and did find some others but never found a solution.
I do not think that it is a right problem here. Users have appropriate rights. If a needed file was locked by f-prot, would pegasus not notice it as it does with open files you try to attach?
This may be just a wild guess! This all has to do with pmail.ini. Pegasus seems to read internet settings from it and stores them into memory at start. When it is closed these settings are written back. Could it be that the memory locations of these informations get deleted by some other nasty program. So when it comes to writing back there is nothing to write back.
As a kludge I decided today to give my users a script to copy back an faultless pmail.ini over the corrupted one.
What do you think of this?
As this is the first time I post to this forum I would like to thank David Harris for his work. I am glad to see that the work goes on and wish David and the team a lot of success.
"Blackcat and other Frisk developers, I am still wondering, assuming that emails are most likely the main entry point for viruses (?) do AV software developers have an exchange policy with email developers to find the best way to handle certain issues such as the one mentioned above in this thread. A few lines would be great."
Reply of one of the developers today (2007-11-27, 08:35:37)
"Sorry for the late reply. Nope, I am not aware of such an exchange, yet."
Export the mailbax from Netscape, must have a .mbx (lowercase). Copy the exported mailbox to the Pegasus maildir, must be done one at a time Open Pegasus, the folders will be added to the folder list. Create a new folder, using Pegasus 2.x format Select all emails from the Thunderbird folder and move to the newly created Pegasus folder.
Must be repeated as required for the balance of the mail folders. I was able to move just under 100 .mbx files this way.
Note: Pegasus will only see the new files (mailbox.mbx) on startup.
Welcome to the Community Support forum for Pegasus Mail.
What this forum IS: a place where you can ask questions and give answers, where Pegasus Mail users can share their expertise and experience with each other for the benefit of all.
What this forum IS NOT: an official technical support forum. Whilst I and my test teams will participate here as much as time permits, the fact that you post a question does not create any formal obligation on us to answer it. We will do our best to assist you as time and circumstance permits.
Rules for using this forum: This forum is provided as a community service: as such, certain rules apply.
No flames, outbursts, bad manners, slurs, abuse or rudeness. Discourteous behaviour will not be tolerated. Forum moderators will delete posts that breach this rule without notice or apology. Don't get me wrong: you're welcome to complain here - but if you do so, do it courteously and respectfully and we'll all get along fine.
No spam or advertising. Don't post irrelevant messages or advertise products unless they are directly relevant to Pegasus Mail.
No large attachments, please.
No wishlists please - not because we don't want them, but because there is another forum specifically intended for them.
No WareZ, no links to illegal download sites, no porn, no material that breaches copyright.
To participate in this forum, you must be a registered user of the site.
These rules notwithstanding, this forum is provided so that we can all help each other. Enjoy!
Perhaps you can use to obtain more detailed information about where exactly it's having problems? Right clicking on winpm-32.exe in Process Explorer and opening properties should give you a tabbed window with a lot of information. The "Threads" tab may be able to isolate a particular thread that is hogging the CPU - I generally see about five threads that are related to Pegasus Mail.