Nigel Metheringham wrote:
>On Thu, 2002-07-18 at 15:29, Alexander Sabourenkov wrote:
>> Hmm. Now let's see.
>> The type of the attachment is determined by its Content-Type header.
>> Now what's wrong with Mozilla sending a multipart/message-rfc822 attachment
>> having a C_ontent-Disposition: attachment; name="ForwardedMessage.eml" ?
>>
>> Extension can have some relevance to the actual content type for the MUA if
>> and only if the stated content-type is 'application/octet-stream' if I'm
>> not mistaken.
>
>You've not ventured into the world of windows have you?
>
>Extension is everything, bugger the MIME type.
Unfortunately this message (and the one it was a follow-up to) were
victims of the very thing they were talking about. The
C_ontent-Disposition line which I have mangled above triggered our
system filter and the messages were rejected as possible viruses.
Am I right in thinking there's absolutely no way to tell the quoted text
apart from an actual inline attachment, because $message_body has the
newlines replaced with spaces? I know Philip is thinking of doing
something about this for a future release, but does anyone have any
suggestions on what to do in the meantime?
We do catch an awful lot of viruses this way and I'd hate to just turn
it off, especially since this is the first false positive we've noticed.
--
Eleanor Blair (also postmaster@eng) ecb39@???
