Re: Munged attachment names (again?)

# Here is a sample message that shows the attachment naming problem.
# Hopefully, I've kept the essential bits after eliding the content.
# v2b27 named and tagged the file as:
#
# <LI>application/octet-stream attachment:
# <A HREF="att-0011/01-imeDxtr.doc_">imeDxtr.doc_</A>
#
# It looks like it might be as simple as recognizing/handling filenames
# whether or not they're quoted?!
# _____________
# Tom von Alten

>From the Changelog I just baselined:

• Corrected a parsing error in parsemail when dealing with attachments. If the filename was "quoted" things worked properly. If the filename was not quoted then the name of the attachment was dropping the first letter of the filename and adding '_' to the end.
• Corrected a conditional statement that was limiting storage of 'inline' types to only recording inline types that were of type image/.
• Changed strstr usage when searching MIME headers to use strcasestr instead as the case sensitivity was getting in the way.

Thanks Tom. Works much better now. :)

-- 
Kent Landfield                        Phone: 1-817-545-2502             
Email: kent_at_landfield.com             http://www.landfield.com/
Email: kent_at_nfr.net                   http://www.nfr.net/
Search the Usenet FAQ Archive at http://www.faqs.org/faqs/
Search the RFC/FYI/STD/BCP Archive at http://www.faqs.org/rfcs/