hs.mailsubject(index) returns blank...

[pyspilf]

Has anyone managed to get hs.mailsubject(index) to actually return the subject string from an email in a script...? For me it returns a blank, so it effectively cannot be used to parse incoming email subjects and invoke script actions accordingly...

Bugzilla #1500 has also been raised in relation to this.

It would be (very) nice if someone on HS3 (I am on v3.0.0.152) could write a simple script to try this and let me know if it works for them.

Thanks

Sandro

[sparkman]

Hi Sandro,

That's the same issue I have. Rich said it works for him and so nothing has been done on it since. I have a test script posted in the bugzilla report.

Thanks
Al

[Rupp]

If memory serves me correctly this will only work when an email trigger is activated. Is this how you guys are testing this?

[pyspilf]

Yes, using an event, triggered by an email received, to run the script.

[sparkman]

Yes, using an event, triggered by an email received, to run the script.

Exactly. Initially the index was not returned, that was fixed, but now supplying that index to the other functions just returns a blank.

Cheers
Al

[hjk]

I have just tried this today for the first time. I can get an index, but everything else seems broken. For hs.MailText(), intended to return the message body, I see this pop up in the log:

Getting email body: Please select folder first. Use SelectInbox(), ExamineInbox() or Select(String), Examine(String) method.

I can't seem to find any references for this.

Any ideas? Mail processing is broken, as far as I can tell.

hjk
---

[sparkman]

I have just tried this today for the first time. I can get an index, but everything else seems broken. For hs.MailText(), intended to return the message body, I see this pop up in the log:

Getting email body: Please select folder first. Use SelectInbox(), ExamineInbox() or Select(String), Examine(String) method.

I can't seem to find any references for this.

Any ideas? Mail processing is broken, as far as I can tell.

hjk
---

I haven't seen that specific error. Do you get the same error with hs.MailSubject, or does it just return a blank? Please add your name to the Bugzilla report as well so that it's more likely to get addressed.

Thanks
Al

[MiG1408]

Same issues

I'm having the same issues... Mail subject returns blank regardless of whether I use mail trigger or a specific index. Any help would be much appreciated!

[sparkman]

I'm having the same issues... Mail subject returns blank regardless of whether I use mail trigger or a specific index. Any help would be much appreciated!

Please add your name to the Bugzilla report mentioned in the previous posts. The more people report that this is broken on Bugzilla, the more likely it is to get fixed.

Cheers
Al

[travisdh]

I also added myself to the issue as well and asked again on Bugzilla, hoping it makes it into the next release as I have now migrated to Linux and the inbuilt email handling is the only way I can receive emails.

[hjk]

I haven't seen that specific error. Do you get the same error with hs.MailSubject, or does it just return a blank? Please add your name to the Bugzilla report as well so that it's more likely to get addressed.

Thanks
Al

Added my name to the Bugzilla report. Thanks for sending the link to it! That made it easy. I would love to get mail functions working.

[sparkman]

I would love to get mail functions working.

Me too, but HST doesn't appear interested in getting it working.

[travisdh]

I agree, I know HST are flat out but email should be a basic functionality, especially in other platforms (e.g. linux) where there are no other third party email solutions.

What is more frustrating is that it is half working, in that it will report the index and detect when mail has been received, but that is as far as it goes, its like the old school pager systems that beep to tell you there is a message, then you have to find it out yourself by calling a number.

Hopefully this is fixed in the next version, so that as well as the index being returned the actual email functions return the subject, body and so on but I have to be honest I am not holding my breath given the bug has been around for a while.

[sparkman]

As an FYI, this bug is resolved as of version 311!