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
"email@example.com" - 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:
Content-Type: image/gif; name="C___Program Files__mozilla.org__Carl Jensema.gif"
Content-Disposition: inline; filename="C___Program Files__mozilla.org__Carl Jensema.gif"
As you can see, the file name clearly ends in ".gif" - however this
inline image attachment is dropped because the content id ends in
-- Marvin Herbold firstname.lastname@example.org http://www.herbold-family.com