Author |
Message
|
mikav |
Posted: Tue Mar 26, 2013 8:10 am Post subject: EmailInput Node - Access to message header fields? |
|
|
Newbie
Joined: 08 Jan 2013 Posts: 8
|
WMB v7.0.0.3
We are using EmailInput Node to read messages from an email server over POP3.
We can access the message's header fields To, From, ReplyTo, Subject, Size and SentDate and they contain the correct data.
We can also access the message's body through the MIME parts and it seems to contain the correct data.
However, we're also trying to access other message header fields than the ones listed above, such as Message-ID. The field exists in the header of the email in question when viewing it on the server, but we can't seem to find it anywhere in the data received from the EmailInput Node.
Does anybody know if other header fields than the ones listed above are accessible somehow, or if we should just accept that they are not accessible? |
|
Back to top |
|
 |
lancelotlinc |
Posted: Tue Mar 26, 2013 8:15 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
What does your Trace node tell you?
Code: |
Root:
${Root}
===
LocalEnvironment:
${LocalEnvironment}
===
Environment:
${Environment}
===
ExceptionList:
${ExceptionList}
===
${CURRENT_TIMESTAMP}
======================= |
_________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
mikav |
Posted: Tue Mar 26, 2013 11:48 am Post subject: |
|
|
Newbie
Joined: 08 Jan 2013 Posts: 8
|
lancelotlinc wrote: |
What does your Trace node tell you?
|
Code: |
2013-03-26 15:01:18.061994 2380 UserTrace BIP4060I: Data ''Root:
( ['GENERICROOT' : 0x1c221908]
(0x01000000:Name):Properties = ( ['GENERICPROPERTYPARSER' : 0x1dca9708]
(0x03000000:NameValue):MessageSet = '' (CHARACTER)
(0x03000000:NameValue):MessageType = '' (CHARACTER)
(0x03000000:NameValue):MessageFormat = '' (CHARACTER)
(0x03000000:NameValue):Encoding = 546 (INTEGER)
(0x03000000:NameValue):CodedCharSetId = 437 (INTEGER)
(0x03000000:NameValue):Transactional = FALSE (BOOLEAN)
(0x03000000:NameValue):Persistence = FALSE (BOOLEAN)
(0x03000000:NameValue):CreationTime = GMTTIMESTAMP '2013-03-26 19:01:18.057' (GMTTIMESTAMP)
(0x03000000:NameValue):ExpirationTime = -1 (INTEGER)
(0x03000000:NameValue):Priority = 0 (INTEGER)
(0x03000000:NameValue):ReplyIdentifier = X'' (BLOB)
(0x03000000:NameValue):ReplyProtocol = 'UNKNOWN' (CHARACTER)
(0x03000000:NameValue):Topic = NULL
(0x03000000:NameValue):ContentType = 'text/plain; charset=ISO-8859-1' (CHARACTER)
(0x03000000:NameValue):IdentitySourceType = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceToken = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourcePassword = '' (CHARACTER)
(0x03000000:NameValue):IdentitySourceIssuedBy = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedType = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedToken = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedPassword = '' (CHARACTER)
(0x03000000:NameValue):IdentityMappedIssuedBy = '' (CHARACTER)
)
(0x01000000:Name):EmailInputHeader = ( ['EMAILIHD' : 0x1c221b90]
(0x03000000:NameValue):To = 'to.test@somewhere.com' (CHARACTER)
(0x03000000:NameValue):From = 'from.test@somewhere.com' (CHARACTER)
(0x03000000:NameValue):ReplyTo = 'from.test@somewhere.com' (CHARACTER)
(0x03000000:NameValue):Subject = 'Some email subject' (CHARACTER)
(0x03000000:NameValue):Size = 2582 (INTEGER)
(0x03000000:NameValue):SentDate = TIMESTAMP '2013-03-26 15:01:18' (TIMESTAMP)
)
(0x01000000:Name):MIME = ( ['MIME' : 0x1c220ee8]
(0x03000000:NameValue):Content-Type = 'text/plain; charset=ISO-8859-1' (CHARACTER)
(0x01000000:Name ):Data = (
(0x01000000:Name):BLOB = ( ['none' : 0x1dad5940]
(0x03000000:NameValue):BLOB = X'0d0a0d0a0d0a0d0a54 <SNIP> 52e0d0a0d0a' (BLOB)
)
)
)
)
===
LocalEnvironment:
===
Environment:
===
ExceptionList:
===
2013-03-26 15:01:18.061541
=======================
|
|
|
Back to top |
|
 |
lancelotlinc |
Posted: Wed Mar 27, 2013 4:52 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
Doesn't look like the Id you are looking for is available based on the information you see in the Trace node. You might try to configure your POP server to provide additional data details, if possible. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Mar 27, 2013 5:19 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
lancelotlinc wrote: |
Doesn't look like the Id you are looking for is available based on the information you see in the Trace node. You might try to configure your POP server to provide additional data details, if possible. |
I'm not sure how the POP server configuration will change how the EmailInput node processes the MIME document it receives or the email headers that are outside of the MIME document it receives.... |
|
Back to top |
|
 |
lancelotlinc |
Posted: Wed Mar 27, 2013 5:25 am Post subject: |
|
|
 Jedi Knight
Joined: 22 Mar 2010 Posts: 4941 Location: Bloomington, IL USA
|
mqjeff wrote: |
lancelotlinc wrote: |
Doesn't look like the Id you are looking for is available based on the information you see in the Trace node. You might try to configure your POP server to provide additional data details, if possible. |
I'm not sure how the POP server configuration will change how the EmailInput node processes the MIME document it receives or the email headers that are outside of the MIME document it receives.... |
I'm not an expert on email, but it seems plausible that a Message Id could be passed down in EmailInputHeader or MIME.OptionalPreamble if the server were to provide the info. I could be wrong. _________________ http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
Back to top |
|
 |
Vitor |
Posted: Wed Mar 27, 2013 5:35 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
lancelotlinc wrote: |
I'm not an expert on email, but it seems plausible that a Message Id could be passed down in EmailInputHeader or MIME.OptionalPreamble if the server were to provide the info. I could be wrong. |
It does seem plausible, but that trace only shows the documented headers in EmailInputHeader & doesn't show MIME.OptionalPreamble at all. Now my experience in MIME is fairly limited (like my email reading by WMB experience) but I'd have expected the OptionalPreamble to show in the trace like Content-Type (as implied here); does it need to be parsed out? Is there a DOMAIN for that?
@mikav - to be clear, are you talking about the additional identification headers described in Section 3.6.4 of RFC 2822? _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
mqjeff |
Posted: Wed Mar 27, 2013 5:37 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
lancelotlinc wrote: |
mqjeff wrote: |
lancelotlinc wrote: |
Doesn't look like the Id you are looking for is available based on the information you see in the Trace node. You might try to configure your POP server to provide additional data details, if possible. |
I'm not sure how the POP server configuration will change how the EmailInput node processes the MIME document it receives or the email headers that are outside of the MIME document it receives.... |
I'm not an expert on email, but it seems plausible that a Message Id could be passed down in EmailInputHeader or MIME.OptionalPreamble if the server were to provide the info. I could be wrong. |
It does seem plausible.
But the documentation doesn't say that the EmailInputHeader will be populated with anything other than a specific set of fields... So it's not clear that any changes to the configuration of the server will do any good.
The email server logs should indicate the contents of the messages passed across the POp3 connection to the Broker email client. If the data is in there, and it appears that mikav has checked this... - and it's clearly not in the EmailInputHeader... |
|
Back to top |
|
 |
mikav |
Posted: Wed Mar 27, 2013 6:00 am Post subject: |
|
|
Newbie
Joined: 08 Jan 2013 Posts: 8
|
Vitor wrote: |
@mikav - to be clear, are you talking about the additional identification headers described in Section 3.6.4 of RFC 2822? |
That is correct.
There are a number of other header fields available in the email as seen from the client, that we don't see in the trace.
And as for header fields in the MIME parts, I believe they should only show up there if they are not ASCII-7, which they are in this case. And if we trace out the BLOBs from the MIME parts, we can't find the fields in there either.
I don't believe the problem lies in configuration of the POP3 server, but I guess we could also experiment with setting up a different POP3 client to see if the number of header fields exposed differ. |
|
Back to top |
|
 |
|