> I am getting a consistent POP3 error on one of my identities but only when I am checking mail for ALL identities. > If I become the problematic identity and check mail there is no error. Even when the error is generated, it still does in fact > download the mail from the server which proves the settings are correct. Even so, I tried deleting the POP3 configuration and > re-creating it, but the problem still persists. > Anyone have any further ideas I can try?
Become that identity and go into the POP3 setup using Tools | Internet options | (Receiving)POP3 and hit the add button. Go through all of the POP3 setups you see there and edit then to check their configuration. Delete all those that are no longer necessary.
[quote user="billmac"]Sorry Guys - I found the culprit after some further research. I moved a large CNM file out of the mail directory and all was well. can I now delete this large file? What exactly is it?[/quote]
CNM files contain single messages in the new mail folder.
Michael forwarded your report to me and I've had a look at it.
The core of the problem is that the message is not in a legal format - the end-of-line markers are carriage-return characters on their own, not carriage-return + line-feed as required by the Internet mail standard. Most likely, the customer is using a Macintosh (which uses bare carriage returns for text files) and sending them out using an unsophisticated mail program that doesn't understand that it has to normalize the line endings.
This is one of those areas where you might say "but the web based viewer displays it fine, why can't you?"... Well, all programs are mixtures of compromises, and one of the ones I've made is that I'll tolerate messages with no carriage-returns, but not messages with no line-feeds. It's one of those areas where I balanced performance and maintainability against the need to correct what is demonstrably a rarely-encountered third-party error, and the choice I made means that messages with solo carriage-returns as EOL markers cause problems. I'm sure you'll find that the web mailer has its own sets of compromises and that there are other things that it can't do that Pegasus Mail can - such is the nature of compromise.
Michael and I are working on a way of handling this better, but in all honesty, the more realistic approach would be to see if you can get the customer to lodge a bug report with the developer of their mail program and get it fixed there.
There's nothing garbled, it's just the HTML version of a message, and if it displays ok in Pegasus Mail I really wonder why it should not on other people's machines. Note that Pegasus Mail by default pastes in formatted text if available on the clipboard which enables the editor's Rich text option, you can avoid HTML parts from being created by unchecking the Rich text option or using paste special (Ctrl + Shift + V or context menu entry). There are also options for sending plain text messages (Tools => Options => Message formatting) or multipart/alternative (Tools => Options => Sending mail) which might help.
When I send email to myself as a test, Pegasus honors the formatting in the signature except the image which appears as a grey box.[/quote]
That's because Pegasus suppresses images by default. If you right-click in the body of the message, you'll see an option "Show pictures (HTML only)". If you select this option, you'll see the graphic. [/quote]
Provided the signature (or message) contains remote (linked) images this is true, otherwise there must be something else involved ... Make sure the image you select for your signature is displayed in the signature editor before saving and closing, you sometimes need to load images twice for succeeding.
I don't think it is the printers, cuz everyone in my office room is connected to the same printer, and they don't have the same problem. If I recalled correctly this started happening after I changed my default copies to self folder and it's name, is there a a way to change it back to default setting?
> Crash when sending attachment "solved"....or at least identified ! > PCTOOLS AV Free.........is the culprit....some recent update has resulted in a conflict.
So there was something between WinPMail and the server after all. :-)
We have the same issue here, and it seems to be occurring more each day. I've given my users tips on what to do for forwarding and printing, but they never remember and are starting to get a little annoyed. I understand David is working on a fix, that's great news! If some testing help is needed for the fix, I will gladly volunteer if it helps us arrive at a solution quicker!
You seem to refer to a previous post, which one? Did you get a session log for diagnosing (Tools => Internet options => General at the bottom, please read Pegasus Mail's help or search this forum for more details before posting any of the results, it'll contain your account credentials!).
The issue is not whether Ctl-J reformats the text, (it does), but, rather, what is causing the sudden loss of formatting in the beginning. It is not triggered by backspacing. It happens while I am typing (two finger, and not very accurately hitting keys, so you are correct that it probably has something to do with my typing). But it is unique to Pegasus - it does not happen in any other program - so my suspicion is that it is some key combination which does something particular in Pegasus. The really interesting aspect here is that apparently nobody else experiences this.
I just found that changing the Message font (start a new message and click on the "f" font icon) will change the font of the right pane (addresses) in the Distribution List window.
I had previously played with different settings. I just tried to send again and the emails went out. I re-typed my password on the "Login in to the SMTP server using....". Either before I had the wrong password or Comcast took me off the black list.
I go thru this every year with them. I'll need to figure something out for next year.