v4.52

I'll do the search and read.

Thanks.

Good morning,

 We have a number of PM users and all configurations are identical! However, when I have a reply from one of our users, the format is significantly affected.

The following is a typical example of a reply from one of our users.

From:    &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;<b>&quot;Gail XXXX&quot; &lt;XXXX@XXXX.org.au&gt;</b></span></font>
To:    &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;<b>&quot;'Vicki'&quot; &lt;Vicki@mXXXX.org.au&gt;</b></span></font>
Subject:    &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;<b>RE: MM</b></span></font>
From:    &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;</span></font>
To:    &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;</span></font>
From:    Vicki Cavalieros [Vicki@XXXX.org.au]</span></font>
To:    Gail Conlon</span></font>
Subject:    Re: MM</span></font>
From:    &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&quot;Gail &quot; &lt;gconlon@XXXXX.org.au&gt;</span></font>
To:    &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&quot;'Vicki'&quot; &lt;Vicki@XXXX.org.au&gt;</span></font>
Subject:    &#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#160;&#

Any suggestions on why this happens??

Looking forward to your advice and hopefully a solution.

Boris

&#160; is the code for a non-breaking space. I don't know why that is appearing in the headers at all, let alone so many times.

Are you seeing this only in the headers or in the body of the messages themselves? Are you able to confirm that this person is using Pegasus to reply to you (and not some other program or even webmail)? I assume that if they were writing a plain text message you wouldn't see this - have you tested that?

This appears in he header only!

And as already stated "We have a number of PM users and all configurations are identical!

However, when I have a reply from one of our users, the format is

significantly affected."

All emails are set to HTML format, we dont use plain text.

I can see that you are experiencing the Microsoft effect. Your user is mailing to you from Microsoft Outlook. Outlook uses these crazy blanks to space out the header line content from its line tags (ie From: ).  I can only suggest you ask him/her to stop sending you html email messages and just use plain text.

Martin

[quote user="irelam"]

I can see that you are experiencing the Microsoft effect. Your user is mailing to you from Microsoft Outlook.

Martin

[/quote]

No!. Please do read the post.

"We have a number of PM users and all

configurations are identical!

However, when I have a reply from one of our users, the format is

significantly affected."

We don't use LookOut we use PM exclusively. And ALL configs are the same. That's why I'm stumped on this one and am seeking a solution.

Thanks..

We have read your post but some things just don't fit. Remember, the people on this forum have seen every error Pegasus has thrown over the years and several are beta testers. However, we will continue in good faith. We do want to fix your problem one way or another.

Can you post the entire raw version of one of the affected messages please? Perhaps with the whole message available we may spot something vital.

Thanks.

Following further investigation I can report the following.

I generated an email which was sent internally (to a PM user), this was in turn forwarded off-site and replied to the forwarder who in turn sent it to me.

The external person does use LookOut, so the supposition is that the original cause may be correct.

Is there a work-around or "cure" for this? The process described above is a regular one and lines of   &#160 will therefore continue without such remedy.

Thanks again for the assistance.

[quote user="BMS"]

Thanks.

Following further investigation I can report the following.

I generated an email which was sent internally (to a PM user), this was in turn forwarded off-site and replied to the forwarder who in turn sent it to me.

The external person does use LookOut, so the supposition is that the original cause may be correct.

[/quote]

See? Irelam knows his stuff.

You mention the messages being forwarded. You remember that I asked you originally whether these extra codes were in the headers or the message body? You said the headers, and in fact, I suspected you meant the body. Now, I'm sure you meant the body.

You're seeing these codes in the informational 'headers' which are placed in the body of a forwarded message, aren't you? The bit that says something like 'forwarded message follows' and then includes the To, From, etc. of the original message. Although this information is taken from the headers of the original message, at that point it's just text in the body - an important distinction.

When you forward (or reply) to a message, Pegasus offers you the option of including the original headers or not. You could get around your problem by choosing to omit all headers. Alternatively, when forwarding a message, you can either send the original as an attachment or you can 'bounce' it. The latter is just redirecting the message to the new recipient as if it had been sent to them in the first place. Either option should avoid the non-breaking spaces.

Perhaps the best long-term solution would be to convince the external contact to amend their address book so that Outlook sends messages to your user in plain text.

Thanks for the feedback.

 All taken on board. I'll have a "play" with some options and see the best fit for us. Unfortunately it's not just one external contact to re-educate it would be quite a few.

I'd be better off setting up a marketing campaign to convince these people to use PM instead:-)

What version of Pegasus Mail are you using?

Previously, users seem to have avoided this problem by using v4.5x (search for #160 in the forum to see earlier threads).