I passed this comment on to a cc:Mail knowledgable person and got this reply:
-Joe
> >From list-managers-owner@greatcircle.com Tue Mar 5 16:58:46 1996
> From: Kjetil Torgrim Homme <kjetilho@ifi.uio.no>
> Date: Wed, 6 Mar 1996 00:25:37 +0100
> To: List-Managers@GreatCircle.COM
> Subject: CC:Mail attachments
>
> While we're on the subject of broken mailers... One of the members on
> a list I run is using some CC:Mail stuff, and he's emitting messages
> that look like this:
>
> <<<exaple deleted>>
>
> If you uudecode it, you get the headers of the message s/he replied
> to. Discussions with the user indicates that he's able to remove the
> included text, but not the uuencoded headers.
On replying to a message the user needs to deselect the "Retain the
original item" / "All" radio button. There is is also a configuration
option that controls the default behaviour.
Since the cc:Mail message format is not RFC-822, it needs to store
the RFC-822 headers of inbound messages. So it makes them a file attachment.
Most users ignore them to the point of sending them right back out
when they reply or forward a message.
> Does anyone know if it can be configured to behave? I would prefer to
> find a solution so that I don't have to revoke the member's posting
> access. (I really hate to read messages from people who use mail
> agents where you can't edit the quoted material, anyway.)
cc:Mail allows you to edit quoted material.
It can seperate new material from quoted, but it uses a "Reply Seperator"
rather then the internet style of indenting with a character, such as the
common '>'.
----- End Included Message -----
|
|
