You are probably using multiple accounts. The new version only allows this if you set it up that way when it is installed (according to the manual) and the default installation is single user only and cannot be changed after installation.
[/quote]
Isn't this a rather old thread? See my reply, and others, in the thread you created 2011-01-26:
The help files are very clear:
You have one identity and its POP and SMTP settings. You then create a new, second, identity (it can be based on an old identity, you select, so that you have some settings already arranged as you like). Everything can now be changed in the second identity and stay like that. Obviously it must have its own POP & SMTP settings, e-mail address etc.
Change from the default identity to the second identity, i.e. become it; select Internet Options... Add the address; on POP3 tab click Add then New, and remember to save the definition as something that can be recognised as related to identity B. Repeat for SMTP if necessary.
I have a single user setup, with several identities; it works very well.
Another solution to be able to redefine mailbox path is to delete (or rename) the file pmail.cfg in the program folder. Next time you open Pegasus, it will ask you for your mailbox.
I think that maintaining a blacklist is a waste of time. Blacklisting services are well known to be inaccurate and problematic for entry removal.
You should trust your Spam detection engine (SpamHalter?). If your Spam detection engine causes false positives, it needs to be trained some more. If the sender is coming from an IP address as apposed to a domain name, it is most likely to be a home PC or random IP address (Mail-bot). In either of these cases the spammer does not need or want a reply, and he/she will change sending address frequently.
I suggest you focus on a content detection scheme and possible use of whitelisting friendly domains.
I agree. Viruses are basically dormant in email messages until they are opened or saved, when the AV will hopefully detect them. There is no scripting language support in Pegasus Mail. So don't worry.
Just a quick note to let the forum know that my problem of not receiving certain attachments has been corrected. Everything seems to be working quite nicely.
Thanks to all. I solved my problem essentially along the lines that you recommended. I can confirm that a normal installation in Vista is not the way to go. See my other post.
I have corrected this problem by (1) uninstalling PMAIL from Vista (This included removal though Programs and Features (Control Panel) which removed it from my user subdirectories, and manually deleting the PMAIL folder in Program Files) and (2) following the instructions in Moving your mailbox to another PC from the PMail Knowledge Base. In retrospect I think my mistake was to allow the new version of PMAIL to install into \Program Files and then try to add the folder structures, etc. I could have copied the old version from my previous PC into a data directory on the new computer, as instructed in Moving your mailbox and then updated to 4.41 in place.
The critical piece of missing info was that PMAIL does not install into the registry. When Peter S supplied that bit of info I was able to figure out the rest of it. Thanks, Peter
Just want to close the loop on this issue. First things first: Thanks to Martin and Thomas for their assistance. Martin led me to the solution via PM. Here is what he told me:
Looking at the raw view, I see that it was defined as multipart/alternative which is a
pretty good sign that there is/was a Text and an Html part. The boundary
statements also suggest the same. But there is no html part.
Also the end of message is marked by a "-- End" line. The "--" is part of a signal for
mime multipart boundary markers.
So basically it is broken. How, I cannot begin to guess, sorry.
Which was indeed the case. Some changes to the application and all is well. Thanks again for the help!
I assume that the Win95 systems can talk to the WinXP systems at least via TCP/IP. If this assumption is true install Mercury/32 on the XP system and have the Win95 system point to this host rather than the ISP. Mercury/32 can receive the the mail either via the queue if networked of via MercuryS. Mercury/32 can send all the mail via MercuryC using SSL.