CFPOP Attachment Error (apparent bug)

[steverobison]

Using CFPOP to retreive mail, if a Content-Disposition Header isn't
formed a certain way, CFPOP appears to ignore the attachment.

A standard jpg attachment header appears to be as follows

------_=_Part_UNIQUEIDENTIFICATION
Content-Type: image/jpeg;
name="SOMEFILENAME"
Content-Transfer-Encoding: base64
Content-Description: SOMEFILENAME
Content-Disposition: attachment;
filename="SOMEFILENAME"

Note the line below Content-Type is a tab, then name="SOMEFILENAME"

While using a Cingular cell phone (Motorola V551) to send an email
with a photo attachment, the following attachment header is sent.

------=_Part_UNIQUEIDENTIFICATION
Content-Type: image/jpeg
Content-Transfer-Encoding: base64
Content-Location: SOMEFILENAME
Content-ID: <SOMEFILENAME>
Content-Disposition: inline

Note that the 2nd line name="SOMEFILENAME" doesn't exist.

When I use CFPOP to download this message, CFPOP doesn't process the
attachment.

If I go into the mail server and manually edit the message and add the
2nd line, as follows.

------=_Part_UNIQUEIDENTIFICATION
Content-Type: image/jpeg
name="SOMEFILENAME"
Content-Transfer-Encoding: base64
Content-Location: SOMEFILENAME
Content-ID: <SOMEFILENAME>
Content-Disposition: inline

Now, if I attempt to process this message using CFPOP, it will
successfully process the attachment inside of the message.

When I look at RFC 2183 ([url]http://www.faqs.org/rfcs/rfc2183.html[/url]), it
appears that the content header as sent by Cingular is valid.

Let me know if anyone needs further detail or clarification.

[serat]

I suspect that this is due to a lack of support for the Content-Location
header, which is part of the Cingular headers but not part of the standard jpg
attachment example.

I found a couple cfpop bugs/enhancements for CFMX 7, one for support for
Content-Location, bug report 53799. This will provide support for that header
according to RFC 2557.

[PaulH]

going at that message via javamail (both thru cf and java) i can see that the
message contains an attachment but can't return it unless handled as a special
case (ie the code modifications i used to get this attachment blows up
w/"normal" mail w/attachments). is it really just w/cf?