• Previous message: Stian B. Barmen: "RE: Problems with winmail.dat"
• In reply to: Stian B. Barmen: "RE: Problems with winmail.dat"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Mail actions: [ respond to this message ] [ mail a new topic ]

Looks like nobody can offer me a solution to my problem with .com files?

To recap: Inline images in HTML are given identifiers such as
"97924@xyz.molar.is" - they also have a separate file name
header field that gives the image a proper file name (ending in .gif or
whatever). If I have a rule to drop .com files in my Anomy
configuration files, it will nuke those images, even though their _file_
names don't end in .com, only their _id_ does...

Sample of an actual image header:

--MIMEStream=_2+76342_040116330413413_1055088934
Content-Type: image/gif; name="C___Program Files__mozilla.org__Carl Jensema.gif"
Content-Transfer-Encoding: base64
Content-Disposition: inline; filename="C___Program Files__mozilla.org__Carl Jensema.gif"
Content-ID: <97971@xyz.molar.is>

As you can see, the file name clearly ends in ".gif" - however this
inline image attachment is dropped because the content id ends in
.com... :-(

-- 
Marvin Herbold
97879@xyz.molar.is
http://www.herbold-family.com

• Next message: V. Weck: "problems with sanitizer blocking on mail scanning"
• Previous message: Stian B. Barmen: "RE: Problems with winmail.dat"
• In reply to: Stian B. Barmen: "RE: Problems with winmail.dat"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
• Mail actions: [ respond to this message ] [ mail a new topic ]