Jon00 Email V4

[jon00]

If it does not exist, add the line immediately below the [Settings] line

Copy mine and you will not have any issues in the future:

[Settings]
ScriptingReferences=system.XML;System.XML.dll,System.Data;System.Data.dll,System.Web;System.web.dll,System.Drawing;System.Drawing.dll,System.Management;System.Management.dll 

Settings.ini can be found in the config directory

[johnnybwis]

That was it... thanks

[michaeldecharon]

John,

Can I also have the link to the new version?

[jon00]

Check your Homeseer email address.

[michaeldecharon]

Check your Homeseer email address.

Thank you John, but i'm not able to check my messages, I've send you a pm.

[jon00]

I've now sent details to your direct email address.

[GreenAcres]

Jon,


Looking forward to HS Version 3.0 support


Thanks For All The Hard Work!!!


Thom

[johnnybwis]

I've been finding some minor issue's with my Homeseer events, I think a power outage corrupted it but not sure how far back to go for a backup so I've just been correcting as I go. Anyway the email script is showing the following...any ideal? I'm thinking my email set-up page may have changed?


7/1/2013 6:13:11 PM - Jon00_Email - Error in main subroutine: Invalid operation at current state
7/1/2013 6:13:10 PM - Jon00_Email - John has 0 emails in this mailbox
7/1/2013 6:13:10 PM - Jon00_Email - John has 0 new email messages
7/1/2013 6:13:10 PM - Jon00_Email - Error in Pops subroutine Block T: Invalid operation at current state
7/1/2013 6:13:10 PM - Jon00_Email - Error in Pops subroutine Block F: Invalid operation at current state
7/1/2013 6:13:10 PM - Jon00_Email - Error in Pops subroutine Block E: Invalid operation at current state
7/1/2013 6:13:10 PM - Jon00_Email - There are no changes at the mail server for John
7/1/2013 6:13:10 PM - Jon00_Email - Error in Pops subroutine Block D: Invalid operation at current state
7/1/2013 6:13:10 PM - Jon00_Email - Error in Pops subroutine Block C: Invalid operation at current state
7/1/2013 6:13:10 PM - Jon00_Email - Error in Pops subroutine Block B: Invalid operation at current state

[jon00]

The problem is Winsock related. You may need to do a repair.

In Windows 7, you could try the following from the command prompt:

netsh winsock reset catalog

(reset winsock entries) and

netsh int ip reset reset.log hit

(reset TCP/IP stack)

[GreenAcres]

Jon,

Does this support HS3 if so I would like the beta as well

[jon00]

Jon,

Does this support HS3 if so I would like the beta as well

No only HS2.

[Wadenut]

I suppose it's time to report this. These errors have been occurring quite frequently since installing V4. Since I've been focusing on tracking down and fixing errors, this is one of the few problems remaining, This seems to only occur on periodic checks (10 mins), perhaps once or twice per day:

12/8/2013 11:33:13 PM Jon00_Email Error in main subroutine: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:12 PM Jon00_Email Error in main subroutine: Invalid operation at current state
12/8/2013 11:33:11 PM Jon00_Email Cannot retrieve message 2 from POP3 server
12/8/2013 11:33:10 PM Jon00_Email Error in Pops subroutine Block S: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:10 PM Jon00_Email Error in Pops subroutine Block R: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:10 PM Jon00_Email Problem with POP3 server - will need to download all mail on next run
12/8/2013 11:33:10 PM Jon00_Email Error in Pops subroutine Block Q: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:10 PM Jon00_Email Error in Pops subroutine Block P: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:09 PM Jon00_Email Error in Pops subroutine Block I: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:09 PM Jon00_Email Error in Pops subroutine Block T: Invalid operation at current state
12/8/2013 11:33:09 PM Jon00_Email Error in Pops subroutine Block F: Invalid operation at current state
12/8/2013 11:33:08 PM Jon00_Email Error in Pops subroutine Block E: Invalid operation at current state
12/8/2013 11:33:07 PM Jon00_Email Error in Pops subroutine Block D: Invalid operation at current state
12/8/2013 11:33:07 PM Jon00_Email Error in Pops subroutine Block C: Invalid operation at current state
12/8/2013 11:33:07 PM Jon00_Email Error in Pops subroutine Block B: Invalid operation at current state
12/8/2013 11:33:07 PM Jon00_Email Homeseer Pop error : Cannot set message number when disconnected
12/8/2013 11:33:07 PM Jon00_Email Cannot retrieve message 1 from POP3 server
12/8/2013 11:33:07 PM Jon00_Email Error in Pops subroutine Block F: Invalid procedure call or argument
12/8/2013 11:33:06 PM Jon00_Email Error in Pops subroutine Block E: Invalid procedure call or argument
12/8/2013 11:33:06 PM Jon00_Email Error in Pops subroutine Block D: Invalid procedure call or argument
12/8/2013 11:33:06 PM Jon00_Email Error in Pops subroutine Block T: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:06 PM Jon00_Email Error in Pops subroutine Block F: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:05 PM Jon00_Email Error in Pops subroutine Block E: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:05 PM Jon00_Email Error in Pops subroutine Block D: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:05 PM Jon00_Email Error in Pops subroutine Block C: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:05 PM Jon00_Email Error in Pops subroutine Block B: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:04 PM Jon00_Email GCMTech Pop error : Cannot set message number when disconnected
12/8/2013 11:33:04 PM Jon00_Email Cannot retrieve message 1 from POP3 server
12/8/2013 11:33:04 PM Jon00_Email Error in Pops subroutine Block F: Invalid procedure call or argument
12/8/2013 11:33:04 PM Jon00_Email Error in Pops subroutine Block E: Invalid procedure call or argument
12/8/2013 11:33:03 PM Jon00_Email Error in Pops subroutine Block D: Invalid procedure call or argument
12/8/2013 11:33:03 PM Jon00_Email Error in Pops subroutine Block T: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:03 PM Jon00_Email Error in Pops subroutine Block F: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:02 PM Jon00_Email Error in Pops subroutine Block E: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:02 PM Jon00_Email Error in Pops subroutine Block D: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:02 PM Jon00_Email Error in Pops subroutine Block C: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:02 PM Jon00_Email Error in Pops subroutine Block B: Wrong protocol or connection state for the requested transaction or request
12/8/2013 11:33:01 PM Jon00_Email Error in Pops subroutine Block T: Invalid operation at current state
12/8/2013 11:33:01 PM Jon00_Email Error in Pops subroutine Block F: Invalid operation at current state
12/8/2013 11:33:01 PM Jon00_Email Error in Pops subroutine Block E: Invalid operation at current state
12/8/2013 11:33:01 PM Jon00_Email Error in Pops subroutine Block D: Invalid operation at current state
12/8/2013 11:33:01 PM Jon00_Email Error in Pops subroutine Block C: Invalid operation at current state
12/8/2013 11:33:01 PM Jon00_Email Error in Pops subroutine Block B: Invalid operation at current state

[jon00]

The email checking routine has not changed from V3 to V4. These messages all relate to POP3 server communication issues.

[langenet]

Jon00,

Would you mind sending me a link to v4?

Thanks,

Robert

[langenet]

Jon,

Just wondering why I see these message in the log... They show when the app gets the e-mail.

18/12/2013 7:53:25 AM  Jon00_Email  Info - Base64 string detected and decoded in 62 milliseconds 
18/12/2013 7:53:26 AM  Jon00_Email  Info - Base64 string detected and decoded in 78 milliseconds 
18/12/2013 7:53:26 AM  Jon00_Email  Info - Base64 string detected and decoded in 78 milliseconds 
18/12/2013 7:53:26 AM  Jon00_Email  Info - Base64 string detected and decoded in 62 milliseconds 
18/12/2013 7:53:26 AM  Jon00_Email  Info - Base64 string detected and decoded in 78 milliseconds 
18/12/2013 7:53:27 AM  Jon00_Email  Info - Base64 string detected and decoded in 78 milliseconds 
18/12/2013 7:53:27 AM  Jon00_Email  Info - Base64 string detected and decoded in 93 milliseconds 
18/12/2013 7:53:27 AM  Jon00_Email  Info - Base64 string detected and decoded in 62 milliseconds 
18/12/2013 7:53:27 AM  Jon00_Email  Info - Base64 string detected and decoded in 62 milliseconds 
18/12/2013 7:53:28 AM  Jon00_Email  Info - Base64 string detected and decoded in 78 milliseconds 
18/12/2013 7:53:28 AM  Jon00_Email  Info - Base64 string detected and decoded in 78 milliseconds 
18/12/2013 7:53:28 AM  Jon00_Email  Info - Base64 string detected and decoded in 78 milliseconds 
18/12/2013 7:53:28 AM  Jon00_Email  Info - Base64 string detected and decoded in 62 milliseconds 
18/12/2013 7:53:29 AM  Jon00_Email  Info - Base64 string detected and decoded in 109 milliseconds 

Other than that, it seems to work fine.