Skip to main content
June 26, 2008
Question

CFExchangemail GetAttachments - Empty AttachmentFileName

  • June 26, 2008
  • 2 replies
  • 512 views
Using the cfexchangemail tag with the getAttachments I am getting java.lang.NullPointerException for some attachments. It appears that for some attachments do not show "AttachmentFileName". For my example, when I submit an email from a PDF Form it will send either a PDF file or XML file as an attachment, but these do not show up.

A cfdump shows the following results from the code attached:
AttachmentFileName: [empty string]
AttachmentFilePath: [empty string] (This is expected with the attributes used in tag)
CID: [empty string]
IsMessage: NO
MimeType: [empty string]
Size: 113476

It knows the attachment is there and it knows the size, but it can not find the name or download it.

Any Ideas?
    This topic has been closed for replies.

    2 replies

    Participant
    May 15, 2009

    We have the same/similar issue on cf8 8,0,1,195765

    Have you had any luck in finding an solution?

    We are trying to retrieve e-mails with a form attachment from and exchange server.

    The form is an attached PDF form created in LiveCycle Designer ES 8.2.1.xxxx

    it has a button of type submit with the submit to url set to mailto:xxx@xxx.com

    and Submit as: pdf

    When the form is filled and the button is clicked the file is attached on the server and can be seen retrieved via an e-mail client

    however CF reports the information as when using the UID:

    ATTACHMENTFILENAMEATTACHMENTFILEPATHCIDISMESSAGEMIMETYPESIZE
    1[empty string][empty string][empty string]NO[empty string]417878

    And ColdFusion cannot retrieve the email's attachments via Exchange via this method. Getting a java.lang.NullPointerException when trying to retrieve it.

    If the PDF form is manually attached to an e-mail in Outlook the server can read/retrieve the attachment fine.

    This is a major roadblock in our project! If anyone has any insights it would be greatly appreciated.

    July 3, 2008
    I submitted this as a bug to Adobe.