Search

POP3 adapter - Failed to decode the S/MIME message by Axel Schulze

Active

3
1
Sign in
 to vote
Type: Bug
ID: 726723
Opened: 2/27/2012 2:18:46 AM
Access Restriction: Public
0
Workaround(s)
3
User(s) can reproduce this bug
On our BizTalk Server we have an error regarding received email messages with the POP3 adapter.

The error message is "There was an authentication failure. "Failed to decode the S/MIME message. The S/MIME message may not be valid."

BizTalk Server 2009, CU 2

Configuration:
- POP3 receive location
- custom receive pipeline
- apply MIME Decoding = true
- basic authentication

It seems it has something to do with the length of the header of the message. After installing CU2 for BizTalk 2009 I was able to receive messages with longer headers (more message receivers) but unfortunately we receive mails with even longer headers.

I'll attach samples for working/ not working messages to this item.

Thank you.
Details (expand)

Product Language

English

Version

BizTalk 2009

Category

Adapters

Repro Steps

- Create POP3 adapter
- apply MIME Decoding = true
- basic authentication
- send the sample messages attached to the configured mailbox
File Attachments
File Name Submitted By Submitted On File Size  
not_working.txt (restricted) Axel Schulze 2/27/2012 -
working.txt (restricted) Axel Schulze 2/27/2012 -
Sign in to post a comment.
Posted by VijenS on 10/23/2012 at 4:59 AM

We are seeing similar issue where some messages get stuck in BizTalk..

A message received by adapter "FILE" on receive location "RL_POP3_XXX" with URI "C:\BizTalk\drop\Mail\*.eml" is suspended.
Error details: There was a failure executing the receive pipeline: "CustomsplitIdentify," Source: "POP3 Split Attachment" Receive Port: "RP_POP3_XXX" URI: "C:\BizTalk\drop\Mail\*.eml" Reason: There was an authentication failure. "Failed to decode the S/MIME message. The S/MIME message may not be valid.".
Posted by NARESHK BANKER on 9/18/2012 at 2:12 AM
IN MY CASE MAIL.COM ALIAS WITH LIVE.COM BUT NOW POP3 NOT SUPPORTED IN MY DESKTOP.
Posted by Axel Schulze on 3/14/2012 at 2:43 PM
Applied CU3 recently and the problem is still there - could *please* someone from Microsoft have a look?
Sign in to post a workaround.
© 2013 Microsoft Corporation. All rights reserved. Microsoft Connect Terms of Use | Trademarks | Privacy Statement