For BizTalk 2010, I am using the sample POP3 Pipeline to debatch the attachments from an email that was posted on the wiki.

http://social.technet.microsoft.com/wiki/contents/articles/21001.biztalk-server-how-to-extract-email-attachments-by-pipeline.aspx

In this example everything is working fine and I can set the values for the filename perfectly, BUT when the send port picks this up we are getting duplicate names for all the attachments.

So as example the send port file name format is the following "POP3Msg_%MessageID%.%SourceFileName%"; so for each message it should be the messagid prefix with the original source file name from the message. I attach CSV, JPG and other files together in the same email message. It always outputs each file but with the same SourceFileName portion. In the code I write to the event log and I can see that the values for the filename are being set and I can write them to the event log but it is not being used when outputting to the file system on BizTalk. Does anyone else see a problem here or why it would take the "first" name and not change per message?

The result looks like this. The highlighted one is a PNG and the other is a CSV. Notice that the CSV name is the one used for both.

In the event log here is what I see for each file:

Custom POP3 Attachment Processing

=======================================

Initial discovered File Name: image001.png

Resulting File Name: image001.png

Current MIME Content Type: image/png

Current Charset:

Outbound Message

=======================================

outMsg Filename: image001.png

outMsg Body Part Filename: image001.png

outMsg Content Type: image/png

outMsg Charset:

----------------------------------------------------------------------------------

Second File:

Custom POP3 Attachment Processing

=======================================

Initial discovered File Name: Duplicate Order Test 7-1.csv

Resulting File Name: Duplicate Order Test 7-1.csv

Current MIME Content Type: application/octet-stream

Current Charset:

Outbound Message

=======================================

outMsg Filename: Duplicate Order Test 7-1.csv

outMsg Body Part Filename: Duplicate Order Test 7-1.csv

outMsg Content Type: application/octet-stream

outMsg Charset:

• Edited by Jazzy Wednesday, July 01, 2015 9:17 PM Attaching the image

Ok, I was curious if anyone else was seeing the same of if my code differed from what people were using. Before going through the details of getting support involved I hoped to confirm what I experienced with someone else.

If the POP3 message has multiple parts, then there is a bug maybe in the Pipeline processing that is setting the FILE.ReceivedFileName property to probably the first file name.

FILE.ReceivedFileName, as ready by %SourceFileName% is a MessageContext Property so there can be only one.

You would need to look at each Part Context which is where the MIME disassembler should be writing the MIME part file name to.

So, what you are seeing is correct for BizTalk, but not for your process.

• Edited by Johns-305 [boatseller]MVP, Moderator 7 hours 56 minutes ago