Error with Sender Email Channel & MS Exchange Parameter

[azharshaikh]

Hello All,

Our scenario is Email (POP) to File scenario. We are using Email Package and ASMA properties to pick the SHeader CC field value in our Message Mapping.

Everything is working fine except for few Emails that is sent by some users to our Message Server Exchange ID. We are getting error for these few Email with Error message in PIMON as: (screenshot attached)

MappingException: Mapping failed, IllegalArgumentException: Name is too long (59/50): SHeaderSHEADERX-MS-EXCHANGE-CROSSTENANT-ORIGINALARRIVALTIME

We do not have control over this Ms Exchange Server Header Name length that is sent from Sender / User Mailbox in PI and its causing this issue. If we do not use/ Enable Variable Transport Binding in Channel, this Length error is not coming. However we need to use SHeader parameter in Channel to check for CC email ID value.

We have also tried to add parameters as suggest in SAP note # 940462 - xi mail adapter sends message attributes that are too long

dc.nameLength

Module name: AF_Modules/DynamicConfigurationBean 

Parameter Name: dc.valueLength

Parameter Value: 200

But still same error persists. Please suggest if you have encountered this error before and steps/ideas to resolve it.

Regards,
Azhar

[azharshaikh · Accepted solution]

Hi All,

We were able to resolve this issue by tweaking the parameter value as provided in SAP Note # 940462.

We have added the Dynamic Configuration Module Parameter (prior to Std Adapter Module) in our Sender Mail Channel (Module Tab) in order to trim the DC Header Parameter Name length to 50 (as PI accepts max 50 length) as follows: (screenshot is attached for reference)

Processing Sequence:

1. AF_Modules/DynamicConfigurationBean     Local Enterprise Bean     1

Module Configuration value:

1     dc.nameLength     50

Regards,

Azhar

[dipen_pandya]

Hi Azhar,

http://service.sap.com/sap/support/notes/1805037

I am not sure if this note is relevant with your issue or not.

Best Regards,

Dipen.

[azharshaikh]

Hi Dipen,

Thanks for your inputs. However this is not applicable to our scenario.

Hi All,

Any other inputs on resolving this?

Regards,

Azhar