Jump to content
docasar

EmailReadMessageValue wont give any messageID

Recommended Posts

Hello,

I have been already half a day trying to find out how the 360work email EmailReadMessageValue function works. I have been able to download only the latest 3 days emails, but if any new email will come the EmailGet NExtMessage would be set as 0 and therefore "Halt the script" Moreover no email that I download comes with the messageID or UID. The first does not create the $variable because it is empty and the second gives only value "0". Everything else can be obtained from the keys.

What could I be doing wrong so that the EmailReadMessageValue( "messageID" ) does not extract the messageID from the email??? 

I am desperate because I just cant figure out why this is not working, so any comment that would help see some light would be much appreciated, 

Thanks a lot in advance for any help you may provide.

Luis

Share this post


Link to post
Share on other sites

docaser,

I ran into the same issue using Version 3.06 of the plugin.  In looking at the header information,  the messageID is listed as message-ID.  So I tried using

EmailReadMessageValue( "message-ID" )

Adding the - into the value to read worked. 

This is a  change from version 2.X of the plug in.  In that version the documentation was correct.

Regards

Bruce

  • Like 1

Share this post


Link to post
Share on other sites

Hello Bruce,

I am sorry I am just getting back to you about your suggestion. Thanks a lot, it worked great! :)

I have encountre the same problem with replyTo, any suggestion for that?

Thanks a lot,

 

Share this post


Link to post
Share on other sites

docaser,

 

It looks like they updated the protocal to use the header label value.  I checked and my scripts had the same problem.  Try using:

EmailReadMessageValue( "return-path" )

Regards

Bruce

 

 

Share this post


Link to post
Share on other sites

Hi docasar,

Bruce emailed us and brought this to our attention. It looks like there is an inconsistency  between the documentation and what the plugin is expecting. The key values are actually case-sensitive and the documentation does not reflect that. I tested and changing "messageID" to "messageid" and "replyTo" to "replyto" resulted in the correct information being pulled from the email. Bruce's workaround works as well because the plugin has a fallback to where if the key value that is passed in doesn't exist in the list of values that is created when the message is read into memory then the plugin will search the actual headers and fetch the value if it finds a match. Using "return-path" actually returned the messageID in some cases for me so I would recommend trying "replyto". With that being said, we have changed the code so that the key values are not case sensitive. This change will be present in the next release of the Email plugin. 

 

Again, thanks Bruce for bringing this to our attention!

Share this post


Link to post
Share on other sites

Hi Ryan,

Many thanks for your comment.

Best regards,

 

On 16/01/2018 at 7:05 PM, Bruce Herbach said:

docaser,

 

It looks like they updated the protocal to use the header label value.  I checked and my scripts had the same problem.  Try using:

EmailReadMessageValue( "return-path" )

Regards

Bruce

 

 

HI Bruce,

Many thanks for your help! What I was doing was parsing that info from the headers directly. I will try what you and Ryan suggested.

Best regards,

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now


×

Important Information

By using this site, you agree to our Terms of Use.