Content-Transfer-Encoding: |
quoted-printable |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Wed, 6 Aug 2003 14:24:13 -0400 |
Content-Type: |
text/plain; charset="iso-8859-1" |
MIME-Version: |
1.0 |
Reply-To: |
|
Parts/Attachments: |
|
|
Yes, it is possible to have Outlook send in fully plain text. You need to set up an alias for the listname in a personal address book, then set up the alias to send only plain text, and uncheck any mime features. I set up my discussion list aliases with Send options as Mime unchecked and Plain text/UUencode checked. It seems to work.
(i sure hope this message does work, sending from outlook, with the above options)
Dan Robinson
[log in to unmask]
> -----Original Message-----
> From: Andrew Bosch [mailto:[log in to unmask]]
> Sent: Wednesday, August 06, 2003 1:57 PM
> To: [log in to unmask]
> Subject: Re: characters added to the end of lines
>
>
> The codes are MIME codes for soft returns in the text.
> Microsoft Outlook and
> Novell Groupwise clients both do this. Listserv is strictly
> RFC-compliant and
> so does not convert these codes to actual hard returns
> (CR-LF). This can
> cause weird formatting problems for mail readers that
> interpret these codes,
> but then encounter the hard returns that Listserv inserts at
> the end of every
> 80-character line.
>
> To solve this problem, you could configure your mail server
> strip out the
> MIME codes. I'm not sure if it is possible to get Outlook to
> send in plain
> text, but Groupwise clients can be made to send through a
> non-MIME gateway.
>
>
>
> >>> [log in to unmask] 8/6/2003 10:52:47 AM >>>
> Several users seem to encounter an issue where their e-mails
> are having
> extra characters added to the ends of each line. I'm not
> certain, but it
>
>
|
|
|