ANNOUNCE: Beta 4.25-7 released

Fri Nov 14 20:47:08 GMT 2003

I think that's broken behavior on the part of the mail client and not
something that I would want MS to modify.  If I send a plain text message in
which I want to discuss the <iframe> tag, I expect the client on the other
end to interpret it as plain text.  If I send a message that doesn't include
a content-type tag, then I also expect the receiving MUA to interpret the
message as having a default content-type of text/plain.

Denis Beauchemin wrote:

>Well,
>
>My Evolution is interpreting them and presenting me with a nice "recalc
>this page" button...  so other email clients may also be at risk here...
>
>Denis
>Le ven 14/11/2003 à 15:13, Trever Furnish a écrit :
>
>>Thanks, Denis.  As I suspected, a mail client will not interpret this as 
>>html because the content type is set to text/plain, so I think 
>>MailScanner is doing the sane thing by not disarming these "tags" - 
>>they're not really tags unless they're in a text/html message body.
>>
>>-t.
>>
>>
>>Denis Beauchemin wrote:
>>
>>><html> 
>>><head>
>>><title>Bulletin PROFETIC</title>
>>></head>
>>><body leftmargin="0" topmargin="0" marginwidth="0" marginheight="0">
>>><form method='GET' action='nouveautes.php3'>
>>><input type="hidden" name="recalcul" value="oui">
>>><input type='submit' class='spip_bouton' name='submit' value='Recalc
>>>this page'></form>
>>></body>
>>></html>
>>>
>>>
>>> 
>>>> 