Re(5): Fwd: Really need a way to forward HTML messages

[Winston Weinmann]

Thank you for letting me know that. It appears that Redirect will not allow 
changing the title of the email (such as by adding Fwd:) and that you can't add 
anything to the text of the message. This is a disadvantage in a lot of 
circumstances.

For example, I am trying to forward and invitation to a fundraising event, and 
would like to add an introductory note explaining my involvement. I can't do 
this with Redirect. So in this particular case it's not a solution.

Are there any other differences between Forward and Redirect?

Do I need to download images before I use Redirect?

Thank you.

- Winston


CTM info wrote:

>Winston,
>
>Use Redirect instead of Forward. Redirect will leave the message content
>as it was.
>
>Kind regards,
>
>Chantal Favre
>CTM Development SA
>ctm-i...@ctmdev.com
>
>-
>  "In my first minutes with PowerMail 6, I've already been able
>   to archive a vast amount of my e-mail database and everything
>   is running brilliantly... Many thanks to CTM !"
>
>   Ricardo Pinto, PowerMail version 6 owner (unsolicited commment)
>
>   Download demo versions of PowerMail and FoxTrot Search products:
>  
>-
>
>On Tue, 13 Sep 2011 13:24:22 -0400, Winston Weinmann
> wrote:
>
>>OK, found out what the problem is with posting RTF messages to the
>>PowerMail Discussions list. It was at the bottom of the response from
>>the PowerMail Discussions list:
>>
>>>Your message could not be posted to the PowerMail discussions list because
>>>the message contained HTML and the list does not accept HTML messages.
>>>
>>>For more information, you can contact the list administrator at:
>>>
>>>CTM listmaster 
>>
>>So the PowerMail Discussions list considers RTF as HTML?
>>
>>
>>This has obscured what I tried to post initially, that I /really/ need
>>PowerMail to be able to forward HTML messages.
>>
>>- Winston
>>
>>
>>Winston Weinmann wrote:
>>
>>>The PowerMail Discussions list did it again. When I forwarded my
>>>original Rich Text Format message to myself, PowerMail 6 displayed it
>>>correctly. But below is what the PowerMail Discussions turned it into.
>>>It should read as:
>>>
>>>"OK, I've finally run into a situation where I really need to forward an
>>>HTML email. It is about a local arts organization that will close down
>>>in less than two weeks unless it gets immediate help. The message is a
>>>mess when read as text (lots of long ugly links).
>>>
>>>I have saved it as a web archive, and will send that. But it loses some
>>>of its impact sent as an attachment.
>>>
>>>I really hope PowerMail will be able to forward HTML mail as HTML soon."
>>>
>>>
>>>- Winston
>>>
>>>PowerMail discussions wrote:
>
>

Re(4): Fwd: Really need a way to forward HTML messages

[CTM info]

Winston,

Use Redirect instead of Forward. Redirect will leave the message content as it 
was.

Kind regards,

Chantal Favre
CTM Development SA
ctm-i...@ctmdev.com

-
  "In my first minutes with PowerMail 6, I've already been able
   to archive a vast amount of my e-mail database and everything
   is running brilliantly... Many thanks to CTM !"

   Ricardo Pinto, PowerMail version 6 owner (unsolicited commment)

   Download demo versions of PowerMail and FoxTrot Search products:
  
-

On Tue, 13 Sep 2011 13:24:22 -0400, Winston Weinmann  
wrote:

>OK, found out what the problem is with posting RTF messages to the
>PowerMail Discussions list. It was at the bottom of the response from
>the PowerMail Discussions list:
>
>>Your message could not be posted to the PowerMail discussions list because
>>the message contained HTML and the list does not accept HTML messages.
>>
>>For more information, you can contact the list administrator at:
>>
>>CTM listmaster 
>
>So the PowerMail Discussions list considers RTF as HTML?
>
>
>This has obscured what I tried to post initially, that I /really/ need
>PowerMail to be able to forward HTML messages.
>
>- Winston
>
>
>Winston Weinmann wrote:
>
>>The PowerMail Discussions list did it again. When I forwarded my
>>original Rich Text Format message to myself, PowerMail 6 displayed it
>>correctly. But below is what the PowerMail Discussions turned it into.
>>It should read as:
>>
>>"OK, I've finally run into a situation where I really need to forward an
>>HTML email. It is about a local arts organization that will close down
>>in less than two weeks unless it gets immediate help. The message is a
>>mess when read as text (lots of long ugly links).
>>
>>I have saved it as a web archive, and will send that. But it loses some
>>of its impact sent as an attachment.
>>
>>I really hope PowerMail will be able to forward HTML mail as HTML soon."
>>
>>
>>- Winston
>>
>>PowerMail discussions wrote:

Re: Fwd: Really need a way to forward HTML messages

[Tobias Jung]

Winston Weinmann wrote (Tue, 13 Sep 2011 13:24:22 -0400):

> OK, found out what the problem is with posting RTF messages to the
> PowerMail Discussions list. It was at the bottom of the response from
> the PowerMail Discussions list:
>
>> Your message could not be posted to the PowerMail discussions list because
>> the message contained HTML and the list does not accept HTML messages.
>>
>> For more information, you can contact the list administrator at:
>>
>>CTM listmaster 
>
> So the PowerMail Discussions list considers RTF as HTML?

Rich Text Messages _are_ HTML messages. Despite their name, they have
nothing to do with the Rich Text Format which is known from word
processors: Try sending a "rich text" message from PowerMail and view it
with an email client which can show the message source (e.g. Apple Mail)
and you'll see...

(Of course this doesn't help you with your forwarding problem, but since
you asked...)

Kind regards,
Tobias Jung

powermail-discuss Digest #2946 - 09/13/11

[PowerMail discussions]

powermail-discuss Digest #2946 - Tuesday, September 13, 2011

  Re(2): Fwd: Really need a way to forward HTML messages
  by "Winston Weinmann" 
  Re(3): Fwd: Really need a way to forward HTML messages
  by "Winston Weinmann" 


--

Subject: Re(2): Fwd: Really need a way to forward HTML messages
From: "Winston Weinmann" 
Date: Tue, 13 Sep 2011 13:05:22 -0400

The PowerMail Discussions list did it again. When I forwarded my original Rich 
Text Format message to myself, PowerMail 6 displayed it correctly. But below is 
what the PowerMail Discussions turned it into. It should read as:

"OK, I've finally run into a situation where I really need to forward an HTML 
email. It is about a local arts organization that will close down in less than 
two weeks unless it gets immediate help. The message is a mess when read as 
text (lots of long ugly links).

I have saved it as a web archive, and will send that. But it loses some of its 
impact sent as an attachment.

I really hope PowerMail will be able to forward HTML mail as HTML soon."


- Winston

PowerMail discussions wrote:

>>--==_20110913170005.178923888-1_==
>>Content-Type: multipart/alternative;
>> boundary="==_20110913170005.178923888-2_=="
>>
>>--==_20110913170005.178923888-2_==
>>Content-Type: text/plain; charset=US-ASCII
>>Content-Transfer-Encoding: quoted-printable
>>
>>OK, I've finally run into a situation where I really need to forward an =
>>HTML email. It is about a local arts organization that will close down in
>less =
>>than two weeks unless it gets immediate help. The message is a mess when
>read =
>>as text (lots of long ugly links).
>>
>>I have saved it as a web archive, and will send that. But it loses some
>of =
>>its impact sent as an attachment.
>>
>>I really hope PowerMail will be able to forward HTML mail as HTML soon.
>>
>>
>>- Winston
>>
>>p.s. This is a resend as the first one came back to me in quoted format.
>I =
>>sent this in Rich Text Format. Does the PowerMail Discussions list have a
>=
>>problem with Rich Text Format=3F
>>
>>--==_20110913170005.178923888-2_==
>>Content-Type: text/html; charset=utf-8
>>Content-Transfer-Encoding: quoted-printable
>>
>>>"http://www.w3.org/TR/html4/strict.dtd";>
>>
>>
>>
>>
>>
>>
>>
>>
>>p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica}
>>p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica;
>min-height: =
>>14.0px}
>>
>>
>>
>>OK, I've finally run into a situation where I really =
>>need to forward an HTML email. It is about a local arts organization
>that =
>>will close down in less than two weeks unless it gets immediate help. The
>=
>>message is a mess when read as text (lots of long ugly links).
>>
>
>Your message could not be posted to the PowerMail discussions list because
>the message seemed to contain an enclosure.
>
>For more information, you can contact the list administrator at:
>
>CTM listmaster 
>



--

Subject: Re(3): Fwd: Really need a way to forward HTML messages
From: "Winston Weinmann" 
Date: Tue, 13 Sep 2011 13:24:22 -0400

OK, found out what the problem is with posting RTF messages to the PowerMail 
Discussions list. It was at the bottom of the response from the PowerMail 
Discussions list:

>Your message could not be posted to the PowerMail discussions list because
>the message contained HTML and the list does not accept HTML messages.
>
>For more information, you can contact the list administrator at:
>
>CTM listmaster 

So the PowerMail Discussions list considers RTF as HTML?


This has obscured what I tried to post initially, that I /really/ need 
PowerMail to be able to forward HTML messages.

- Winston


Winston Weinmann wrote:

>The PowerMail Discussions list did it again. When I forwarded my
>original Rich Text Format message to myself, PowerMail 6 displayed it
>correctly. But below is what the PowerMail Discussions turned it into.
>It should read as:
>
>"OK, I've finally run into a situation where I really need to forward an
>HTML email. It is about a local arts organization that will close down
>in less than two weeks unless it gets immediate help. The message is a
>mess when read as text (lots of long ugly links).
>
>I have saved it as a web archive, and will send that. But it loses some
>of its impact sent as an attachment.
>
>I really hope PowerMail will be able to forward HTML mail as HTML soon."
>
>
>- Winston
>
>PowerMail discussions wrote:
>
>>>--==_20110913170005.178923888-1_==
>>>Content-Type: multipart/alternative;
>>> boundary="==_20110913170005.178923888-2_=="
>>>
>>>--==_20110913170005.178923888-2_==
>>>Content-Type: text/plain; charset=US-ASCII
>>>Content-Transfer-Encoding: quoted-printable
>>>
>>>OK, I've finally run into a situation where I really need to forward an =
>>>HTML email. It is about a local arts organization that will close down in
>>less =
>>>than two weeks unle

Re(3): Fwd: Really need a way to forward HTML messages

[Winston Weinmann]

OK, found out what the problem is with posting RTF messages to the PowerMail 
Discussions list. It was at the bottom of the response from the PowerMail 
Discussions list:

>Your message could not be posted to the PowerMail discussions list because
>the message contained HTML and the list does not accept HTML messages.
>
>For more information, you can contact the list administrator at:
>
>CTM listmaster 

So the PowerMail Discussions list considers RTF as HTML?


This has obscured what I tried to post initially, that I /really/ need 
PowerMail to be able to forward HTML messages.

- Winston


Winston Weinmann wrote:

>The PowerMail Discussions list did it again. When I forwarded my
>original Rich Text Format message to myself, PowerMail 6 displayed it
>correctly. But below is what the PowerMail Discussions turned it into.
>It should read as:
>
>"OK, I've finally run into a situation where I really need to forward an
>HTML email. It is about a local arts organization that will close down
>in less than two weeks unless it gets immediate help. The message is a
>mess when read as text (lots of long ugly links).
>
>I have saved it as a web archive, and will send that. But it loses some
>of its impact sent as an attachment.
>
>I really hope PowerMail will be able to forward HTML mail as HTML soon."
>
>
>- Winston
>
>PowerMail discussions wrote:
>
>>>--==_20110913170005.178923888-1_==
>>>Content-Type: multipart/alternative;
>>> boundary="==_20110913170005.178923888-2_=="
>>>
>>>--==_20110913170005.178923888-2_==
>>>Content-Type: text/plain; charset=US-ASCII
>>>Content-Transfer-Encoding: quoted-printable
>>>
>>>OK, I've finally run into a situation where I really need to forward an =
>>>HTML email. It is about a local arts organization that will close down in
>>less =
>>>than two weeks unless it gets immediate help. The message is a mess when
>>read =
>>>as text (lots of long ugly links).
>>>
>>>I have saved it as a web archive, and will send that. But it loses some
>>of =
>>>its impact sent as an attachment.
>>>
>>>I really hope PowerMail will be able to forward HTML mail as HTML soon.
>>>
>>>
>>>- Winston
>>>
>>>p.s. This is a resend as the first one came back to me in quoted format.
>>I =
>>>sent this in Rich Text Format. Does the PowerMail Discussions list have a
>>=
>>>problem with Rich Text Format=3F
>>>
>>>--==_20110913170005.178923888-2_==
>>>Content-Type: text/html; charset=utf-8
>>>Content-Transfer-Encoding: quoted-printable
>>>
>"http://www.w3.org/TR/html4/strict.dtd";>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica}
>>>p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica;
>>min-height: =
>>>14.0px}
>>>
>>>
>>>
>>>OK, I've finally run into a situation where I really =
>>>need to forward an HTML email. It is about a local arts organization
>>that =
>>>will close down in less than two weeks unless it gets immediate help. The
>>=
>>>message is a mess when read as text (lots of long ugly links).
>>>
>>
>>Your message could not be posted to the PowerMail discussions list because
>>the message seemed to contain an enclosure.
>>
>>For more information, you can contact the list administrator at:
>>
>>CTM listmaster 
>>
>
>
>

Re(2): Fwd: Really need a way to forward HTML messages

[Winston Weinmann]

The PowerMail Discussions list did it again. When I forwarded my original Rich 
Text Format message to myself, PowerMail 6 displayed it correctly. But below is 
what the PowerMail Discussions turned it into. It should read as:

"OK, I've finally run into a situation where I really need to forward an HTML 
email. It is about a local arts organization that will close down in less than 
two weeks unless it gets immediate help. The message is a mess when read as 
text (lots of long ugly links).

I have saved it as a web archive, and will send that. But it loses some of its 
impact sent as an attachment.

I really hope PowerMail will be able to forward HTML mail as HTML soon."


- Winston

PowerMail discussions wrote:

>>--==_20110913170005.178923888-1_==
>>Content-Type: multipart/alternative;
>> boundary="==_20110913170005.178923888-2_=="
>>
>>--==_20110913170005.178923888-2_==
>>Content-Type: text/plain; charset=US-ASCII
>>Content-Transfer-Encoding: quoted-printable
>>
>>OK, I've finally run into a situation where I really need to forward an =
>>HTML email. It is about a local arts organization that will close down in
>less =
>>than two weeks unless it gets immediate help. The message is a mess when
>read =
>>as text (lots of long ugly links).
>>
>>I have saved it as a web archive, and will send that. But it loses some
>of =
>>its impact sent as an attachment.
>>
>>I really hope PowerMail will be able to forward HTML mail as HTML soon.
>>
>>
>>- Winston
>>
>>p.s. This is a resend as the first one came back to me in quoted format.
>I =
>>sent this in Rich Text Format. Does the PowerMail Discussions list have a
>=
>>problem with Rich Text Format=3F
>>
>>--==_20110913170005.178923888-2_==
>>Content-Type: text/html; charset=utf-8
>>Content-Transfer-Encoding: quoted-printable
>>
>>>"http://www.w3.org/TR/html4/strict.dtd";>
>>
>>
>>
>>
>>
>>
>>
>>
>>p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica}
>>p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica;
>min-height: =
>>14.0px}
>>
>>
>>
>>OK, I've finally run into a situation where I really =
>>need to forward an HTML email. It is about a local arts organization
>that =
>>will close down in less than two weeks unless it gets immediate help. The
>=
>>message is a mess when read as text (lots of long ugly links).
>>
>
>Your message could not be posted to the PowerMail discussions list because
>the message seemed to contain an enclosure.
>
>For more information, you can contact the list administrator at:
>
>CTM listmaster 
>