Could not parse Outlook Rich Text attachment
rlopezcnm at gmail.com
Tue Oct 15 18:50:26 IST 2013
On Tue, Oct 15, 2013 at 3:49 AM, Martin Hepworth <maxsec at gmail.com> wrote:
> about time people dropped rtf emails from outlook and went to html....
> security aside nothing else other than outleek can parse the email properly.
> Martin Hepworth, CISSP
> Oxford, UK
> On 15 October 2013 10:01, Kai Schaetzl <maillists at conactive.com> wrote:
>> Robert Lopez wrote on Mon, 14 Oct 2013 15:16:12 -0600:
>> > I have been looking through the source of MailScanner-4.84.5-3 and I do
>> > recognize any answers to my questions.
>> There is a 4.84.6 that specifically lists a TNEF patch.
>> Get your web at Conactive Internet Services: http://www.conactive.com
>> MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> Before posting, read http://wiki.mailscanner.info/posting
>> Support MailScanner development - buy the book off the website!
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> Before posting, read http://wiki.mailscanner.info/posting
> Support MailScanner development - buy the book off the website!
Thanks for that. In the archives there is also email saying some patch did
not fix the problem. I need to see if the one you point to is newer.
I agree with your statement and the sentiment. It may not be that easy. Ie,
the choice may not be a personal one and the choice may not be honoured
even when made.
I am becoming convinced there might be bugs in Exchange and/or Outlook.
We have done some experiments and email composed in HTML when forwarded by
a person who is set up to default to HTML end up forwarding "HTML" email
with winmail.dat attached.
It is not clear to me if it is our implementation of Exchange that is
messed up or if it is all Exchange because suddenly the problem is growing
very fast on incoming email from outside our college.
We are also struggling with our phone system that is running on a UNIX box
which sends voice messages to employees who are on Exchange. When Exchange
forwards that message it has a winmail.dat attached.
Right now many persons are complaining about the sender.error.report.txt
My thinking is until I get things fixed as per Kai's suggestion I need to
stop the sending of the report, which I think means stop the scanning of
the winmail.dat file by discarding it instead of scanning it.
I just do not know if that means a loss of information.
Unix Systems Administrator
Central New Mexico Community College (CNM)
525 Buena Vista SE
Albuquerque, New Mexico 87106
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MailScanner