Tom—when Apple says "rich text", they mean that in the generic sense, not rtf.
I don't think Mail has ever sent message in rtf.
On Feb 25, 2012, at 11:22 AM, Tom Wiltshire wrote:
> Here's an example of a basic RTF document:
>
> {\rtf1\ansi\ansicpg1252\cocoartf1038\cocoasubrtf360
> {\fonttbl\f0\fswiss\fcharset0 Helvetica;}
> {\colortbl;\red255\green255\blue255;}
>
> \paperw11900\paperh16840\margl1440\margr1440\vieww9000\viewh8400\viewkind0
>
> \pard\tx566\tx1133\tx1700\tx2267\tx2834\tx3401\tx3968\tx4535\tx5102\tx5669\tx6236\tx6803\ql\qnatural\pardirnatural
>
> \f0\fs24 \cf0 This is a basic rtf document\
> }
>
> I don't know what headers Apple's Mail.app sends out with this, but I can see
> why you wouldn't want to read that as plain text. Even if it got through (eg
> if the headers were ok) we'd still struggle to read it.
>
> (The file was saved from Apple's TextEdit.app, in case anyone wants to know
> where the example came from)
>
> T.
>
>
> On 25 Feb 2012, at 19:07, douglas repetto wrote:
>
>>
>> It may be that Apple is adding something to the header indicating rich
>> text/html even though you don't end up with offending characters in the
>> email. The list software rejects email based on the headers, not on the
>> actual content.
>>
>> There's no fundamental reason why the list can't accept html mail, btw. So
>> if people really want it we can make a change. In the past it's been about
>> spam control and saving bandwidth, but those issues aren't such big concerns
>> anymore, I think. Although I personally find that reading a list like this
>> in different fonts/colors/styles can be unpleasant.
>>
>> douglas
>>
>> On 2/25/12 2:02 PM, Nigel Redmon wrote:
>>> I've had problems in the past when html-style font tags make their
>>> way into the email. For instance, this happens in Apple's Mail.app.
>>> Even though it's not an html email, per se, they sometimes get
>>> rejected (but not always). If I do Make Plain Text from the Format
>>> menu before sedning, then they always get through—there is no visible
>>> change to the email either (because they are just some default font
>>> tags—I'm not really formatting the text).
>>>
>>>
>>> On Feb 25, 2012, at 10:38 AM, Brad Garton wrote:
>>>> Hey music-dsp-ers --
>>>>
>>>> Has anyone else experienced troubles getting posts to show up on
>>>> our list? I've sent (and re-sent) several this morning and they
>>>> just vanished. I've checked with douglas about it, but was
>>>> wondering if anyone else has had problems.
>>>>
>>>> brad http://music.columbia.edu/~brad
>>>
>>> -- dupswapdrop -- the music-dsp mailing list and website:
>>> subscription info, FAQ, source code archive, list archive, book
>>> reviews, dsp links http://music.columbia.edu/cmc/music-dsp
>>> http://music.columbia.edu/mailman/listinfo/music-dsp
>>>
>>
>> --
>> ............................................... http://artbots.org
>> .....douglas.....irving........................ http://dorkbot.org
>> .......................... http://music.columbia.edu/cmc/music-dsp
>> ...........repetto............. http://music.columbia.edu/organism
>> ............................... http://music.columbia.edu/~douglas
>>
>> --
>> dupswapdrop -- the music-dsp mailing list and website:
>> subscription info, FAQ, source code archive, list archive, book reviews, dsp
>> links
>> http://music.columbia.edu/cmc/music-dsp
>> http://music.columbia.edu/mailman/listinfo/music-dsp
>
> --
> dupswapdrop -- the music-dsp mailing list and website:
> subscription info, FAQ, source code archive, list archive, book reviews, dsp
> links
> http://music.columbia.edu/cmc/music-dsp
> http://music.columbia.edu/mailman/listinfo/music-dsp
--
dupswapdrop -- the music-dsp mailing list and website:
subscription info, FAQ, source code archive, list archive, book reviews, dsp
links
http://music.columbia.edu/cmc/music-dsp
http://music.columbia.edu/mailman/listinfo/music-dsp
