Mercury Mail Server is rejecting emails of the form <<Sender> name@sender.com>
Appendix C of RFC822 (which defines email address formats in headers)
suggests that including the name in front of the email address (as
"Fred bloggs<fred@somewhere.com>") is perfectly acceptable, and
even encouraged.
This needs to be fixed since the Mercury server rejects the incoming emails as emails to unknown addressees.
[/quote]
<Sender> name@sender.com is an improper form. The forms are "Sender" <name@sender.com>, or Sender <name@sender.com> or name@sender.com (Sender) In addition, I'd check to make sure that you have matching <> where required.
[quote user="philip e j jones"]If I hilite a section of an incoming message in either preview or open mode, then try and past it into another application, the whole message is pasted. Is there a way to cut and paste part of a message. I know I can do this if I open reply then cut and paste - but its just one more fiddly annoyance that seems unnecessary.[/quote] I do this all the time so I'm not sure what to tell you. There might be something specific about the messages you are working with though that causes a problem with the copy/paste.
It sounds like your folder set-up is trashed. The .cnm files are the individual messages in the new mail folder. Try copying them using windows explorer to a safe place, and then do a complete new install of Pegasus Mail to a different folder. Copy the cnm files to your this second new mail folder and try again. Avoid duplicating names of folders.
I've read this post as I'm having the same problem with IMAP with my
Gmail account. I don't have IMAP setup with any other account so I
can't say if it is a Gmail problem or not, but from the above posts it
seems that it may not be limited to Gmail.
In GMail enable Setting | Labs | Advanced IMAP controls. Then in the IMAP4 settings try selecting "Do not automatically expunge messages" and see if this helps. IIRC, it's the moving to the trash folder and expunging the original message that is causing the problem. FWIW, this is the only IMAP4 server I have with this particular problem with deleting with an immediate purge. maybe that's why GMail added these "advanced" options.
[quote user="irelam"] Make sure you close Pegasus Mail by using its menu File/Close rather than the system 'X' button in the right corner of the Window. Martin[/quote]
What? Pegasus still has that bug?
I hope this is fixed in 5.0!
[/quote]
I am not sure whether this really has something to with the problem reported by the thread starter. I have several Pegasus Mail user; for testing purposes, I closed every of them by clicking on the X in the right corner of the Pegasus Mail main window. Each time I closed it that way, Pegasus Mail closed normally without any problems.
Thomas S.'s suggestion concerning the rights sounds useful to me.
There may be another reason for Pegasus Mail crashing when being closed. If you close Pegasus Mail while a POP3-check is being done, Pegasus Mail is likely to crash (at least, this is what I have experienced). Is Pegasus Mail checking for new messages while your are closing Pegasus Mail?
I can't duplicate your experience. In the message composition window, I can select an alternate identity, and for that particular email, the identity has been changed. I am not using sigs, but each of my identities has a different "sender name", and the resulting emails always carry the name associated with the identity selected while composing the message.
I would try disabling all the addons you have, one-by-one, until you go back to a stable system.[/quote]
In addition:
A bit of a wild guess ... , but check your Antivirus system and settings. It may as well have an Anti-Spam system integrated (so you would run two). Some systems actually place themselves in between your Pegasus Mail and your ISP and seamlessly takeover and control your email downloads and sending. This may actually explain why your PM is in 'offline' mode but you still receive those and other(?) messages. I would completely deactivate and check your AV program and do some tests.
I seem to remember Pegasus used to multi-task pretty well, both when downloading new messages and when sending messages. For a while I've noticed that I can still do other activities while I'm downloading, but if I upload a big message, Pegasus appears to be locked up solid. Often it doesn't even update its progress indicator message for most of the upload time. It does eventually finish uploading and unfreeze.
I originally starting seeing this in 4.41. Then I finally got sick of the long-lines-wrapping bug in 4.41 and went back to 4.31, and it's still doing it there. I just switched from XP to Vista and that didn't change anything either.
Nothing has changed in my ISP connection. Other utillities (e.g. ftp) can upload at full speed without hanging. I have no outgoing-mail virus scanner.
What might have caused this to change? How can I prevent Pegasus from hanging while uploading?
Is there any way to do this now? Also, how can I run a filter against an IMAP Inbox to move old messages to a local folder; I have created a rule set and also the local folder but so far have not found a way to run the filter against the Inbox. I've set the filter to run on 'open' rather than 'close', but upon opening the Inbox, the filter isn't run. Shouldn't autofilter folders work against incoming IMAP mail too?
EDIT: I am now waiting for the results of selecting Tools -> Mail Filtering Rules -> Apply General Rule Set to Folder to see if that runs the rule set against an IMAP Inbox...
EDIT: That works OK...
Still wondering about how to have this done automatically without needing to open and close the folder. Cygwin is running on this host - could I set up a cron job to do this?
i post here my question but my problem is not exactly the same.
after a major PC crash, i've restored the old pmail directory, but
my pmail account password don't work. (not my login/password email account)
I remember my password. There is a way to retrieve my email ?
thanks,
Eric
PS: i hope you've understand my bad english! [/quote]
Pegasus Mail does not use passwords. You probably need to enter your username. Those names are listed in a file called pmail.usr. You can open that file with notepad or such. Most likely when you enter admin it will work.
If there is an image in the forwarded message you wish to 'save', then bcc yourself. This will include any image/attachment that would be missing when a forward/send is done.
This is a design issue from when hard drive spoace was not as available/large as it is now.
Please do not hide information that could be important to helping you solve the problem. That IP address and the timeout setting is critical and no security risk at all.
That said, I would first increase the timeout and see if that fixes the problem. Also if you have AVG between Pegasus Mail and the POP3 server I would remove that as well. If neither of these fixes the problem then you probably have some sort of packet fragmentation problem. The POP3/SMTP transmissions may fail if the MTU packet size is so large that a packet is fragmented. In many cases the receiving system router blocks the receiving servers "packets fragmented" response to the sending system using "MTU Discovery". These oversize packets are not accepted and so are resent. This results in a timeout, generally at the end of the message transmission but it can be anywhere in the process. You need to reduce the MTU size. Windows defaults to a 1500 MTU and many routers and DSL connections need 1492. You might simply want to turn off the MTU Discovery operation.
You might want to get a copy of SG TCP Optimizer that I find quite handy. http://www.speedguide.net/downloads.php This little utility will allow you to test your MTU for maximum size without fragmentation against specific servers. If will also make it easy to adjust the MTU.
And finally, does this computer, by chance, happen to have an NVidia NForce 4 chipset on the motherboard? If so, many other have had this exact problem, and it turned out to be an optimization setting for the built in NIC which caused the problems with packet fragmentation. Disabling the advanced optimization capability called "checksum offload" made all the problems of sending SMTP mail via WinPMail disappear.
> I have been using Pegasus for many years over many computers. I > recently had my wife's computer checked and the "expert" at her > university backed up everything on the C drive before reinstalling > XP from the start. Yes, it seems to work faster now and I can find > all the documents and files/folders my wife uses for her university > job. Except, however, for pegasus. When I try to open it, using > the wimpm-32 application (largest) file, I get a box requesting the > "username" before it will load. I have no recollection of a > username in this position, and have tried all sorts of permutations > of her "identity", usernames for email, and racked my brains all > without success to gain entry into this beloved of all places. I am > at a total loss. If there is/was a username and it is lost, is > there some way I can get her Pmail to open. My wife cries a lot > these days, and I am hoping to sove this mystery for her and to be > her hero. Please help. Thank you.
I suspect the drive letter or path to the mailboxes has changed. Go to the directory containing the winpm-32.exe file and run the program pconfig.exe. Check the Standalone HOME and NEW mail directory drive and path to make sure they are pointing to the directory containing the pmail.ini file and folders. By default this should be in the form c:\pmail\mail\<username> or c:\pmail\mail\~8 depending on whether or not this a a older or newer installation.
> Yesterday, after working fine my Pegasus will no longer work. Seems > to hang at the start of loading the new mail folder and tries to > load forever. Can anyone recommend a program or service that might > help. I despartately need these emails.
Move all of the *.CNM files out of the new mail directory and try again. It should now open normally. You can then put the messages back one at a time until you find the problem message.
It's probaby going to be a really large message. If you are using content control then I'd recommend that you set a limit on the message size so you are not scanning these large files with encoded attachments.
1. Use Tools | Spam and content controls | Content control...
2. Select and edit the control definition
3. Select the "Message tests" tab.
4. Enter 8000 in "Check at most this many bytes in each message"
Thanks for the suggestion - sorry for not getting back for so long! The context menu worked fine in Pegasus 4.41, too, I just had never realized that there was one.
It must be an accidental omission in the dialog - buglet - all (?) the other rule types have checkboxes for disabling and negating the rule.