Better Email Q&A

[petematheson]

Sent, no worries! Thanks very much

[FlyingDiver]

I just looked at the raw message. It's mickeysoft crazy email content. It's doing multipart with png and gif and HTML and plain text. I think the problem is the HTML and plain text parts are encoded base-64 for some bizarre reason. I'll need to look at the code to see what I need to do to decode it properly.


Sent from my iPad using Tapatalk

[FlyingDiver]

Try this (pre-release) version: https://github.com/FlyingDiver/Indigo-B ... tag/v7.1.1

[shrxman]

Hey Joe,

Got another question for you. How can I send an HTML formatted email from the command line? I currently use this command:

bePlugin.executeAction("sendEmail", deviceId=outboundEmailDeviceId,props={'emailTo':emailTo, 'emailSubject':emailSubject, 'emailMessage': report})

However, since the file is HTML formatted, it all gets translated and the tags show up in the message. When I cut and past the message into an Action Group and select the 'HTML' format from your dropdown list, the messages render perfectly. Is html another prop I can add to that previous command, perhaps, or is it not exposed to the commandline?

thanx!
~ken

[FlyingDiver]

This should work:

Code: Select all

bePlugin.executeAction("sendEmail", deviceId=outboundEmailDeviceId,props={'emailTo':emailTo, 'emailSubject':emailSubject, 'emailMessage': report, 'emailFormat': "html"})

[shrxman]

HAH.. Nevermind. I answered my own question. This works perfectly:

Code: Select all

bePlugin.executeAction("sendEmail",deviceId=outboundEmailDeviceId,props={'emailFormat':'html', 'emailTo':emailTo, 'emailSubject':emailSubject, 'emailMessage': body})

Thanx, as always, for the plugin!

~ken

[kennybroh]

I'm getting a slew of these errors. I've cut off a bunch of the ascii. Indigo and the plugijn are up to date, and the gmail pop server shows a "success" state. Any ideas?

Code: Select all

Jun 22, 2017, 3:33:37 PM

   Better Email Error              Error fetching Message 1: line too long

   Better Email Error              Error fetching Message 2: line too long

   Better Email Error              Error fetching Message 3: line too long

   Better Email Error              Error fetching Message 4: line too long

   Better Email Error              Error fetching Message 5: line too long

   Better Email Error              Error fetching Message 6: line too long

   Better Email Error              Error fetching Message 7: line too long

   Better Email Error              Error fetching Message 8: line too long

   Better Email Error              Error fetching Message 9: line too long

   Better Email Error              Error fetching Message 10: line too long

   Better Email Error              Error fetching Message 11: line too long

   Better Email Error              Error fetching Message 12: line too long

   Better Email Error              Error fetching Message 13: line too long

   Better Email Error              Error fetching Message 14: line too long

   Better Email Error              Error fetching Message 15: line too long

   Better Email Error              Error fetching Message 16: line too long

   Better Email Error              Error fetching Message 17: line too long

   Better Email Error              Error fetching Message 18: line too long

   Better Email Error              Error fetching Message 19: line too long

   Better Email Error              Error fetching Message 20: line too long

   Better Email Error              Error fetching Message 21: line too long

   Better Email Error              Error fetching Message 22: /9j/4AAQSkZJRgABAgAAAQABAAD/2wBDAAYEBQYFBAYGBQYHBwYIChAKCgkJChQODwwQFxQYGBcUFhYaHSUfGhsjHBYWICwgIyYnKSopGR8tMC0oMCUoKSj/2wBDAQcHBwoIChMKChMoGhYaKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCj/wAARCAD0AbMDASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWGh4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREAAgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYkNOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOEhYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwDgY+lWEOTxVWI5FTxnBrYxLakZFWYyMiqac81aj6igC9D1FXoBuKjtVCLtV+z5cD0pNgasKhVIFW0OBVOI1OHx1qQLCMNwq5GeKzomDOBVuN9uaq4M9B+HwHlXUn0FdaZo1PzFV+pFeR6deT2yMYZJI1k4JU1dWYykl5HY98moauVc9TSQcbWBHsa53xlIz2cCxuP9Zkgc9q5ZJWA4dvzpTKT3JPuc0JCuFpvS4ibGMHOa3PtIJ35JY9M1iIxJwTxVmN8j6UwReab5lJOSTVa8G4gjvVZpv3wweBVhmzF8w4HTnmlbUZArlSEYjk0kjYk2kjI7UXGDDvAwfvKT3qGVz5ivuDBu9MQZBYirEXy4xVGRwJjVpHOVwAaYjXtpvKuEkUbm7+laS6o7NtfAUf3hxWfZy2iwLv8A9YTUN1PAUO1uW4xQwL8V1CLiRGbarY6dDVO82w3J+zD5D09xisvc4OU5qTzpQY3YH5eODSHcvPLhvKhGCeuaz7qQLKpHIzTpbsvODsIJ7ZxSTGGSHLfJKDnBoHcikn8w5cn2FV3OQelRs2elNJwO+aBjWYZxSHgH3qNzk5ppOce1ADv8ail4BYdaczEDpmo3Y8HH4UrhYe5wox6YqCQnKk5I9K

Thanks

[FlyingDiver]

I'm getting a slew of these errors. I've cut off a bunch of the ascii. Indigo and the plugijn are up to date, and the gmail pop server shows a "success" state. Any ideas?

Turn on debug logging for the plugin and try it again. Also, zip up the full email message (including headers) from your email client and attach it here or PM it to me.

[kennybroh]

Turned debugging on but it really doesn't add anything. Same messages with the only debug message "Retrieving Message #n" under the error "Error fetching Message n: line too long".

So I disabled all of the triggers which use the plugin and it is still giving me the error. Why is the plugin trying to retrieve every message in the inbox if nothing is asking for anything within indigo?

Also it is going through 250 messages, reporting the same error for all of them.

[kennybroh]

This particular mailbox is just used to communicate with indigo. I deleted all the messages, and here's what the log now shows:

Jun 22, 2017, 5:44:30 PM
Better Email Debug Connecting to POP Server: KBF Indigo email
Better Email Debug Retrieving Message # 1
Better Email Error Error fetching Message 1: line too long
Better Email Debug Retrieving Message # 2
Better Email Error Error fetching Message 2: line too long
Better Email Debug Logged out from POP server


But there are no emails there.

[FlyingDiver]

So I disabled all of the triggers which use the plugin and it is still giving me the error. Why is the plugin trying to retrieve every message in the inbox if nothing is asking for anything within indigo?

Triggers have nothing to do with fetching messages. The plugin always attempts to fetch all messages in the POP mailbox. It (tries to) ignore messages it's seen before. Then, for each message it fetches, it checks to see if any of the messages match the trigger conditions.

In general, it's good practice to have the plugin delete messages from the server when it processes them. Or have some other mechanism to clear them out on a regular basis. Otherwise it spends a lot of time fetching old messages that have already been processed.

In your case, I'm a little stumped on why it's fetching 2 messages when you say the POP mailbox is empty. The server should have replied with a count of 0, which would cause the plugin to just close the connection.

Who's the POP service provider?

Also, check the preferences file for the plugin. What's in the readMessages line?

[kennybroh]

OK, now I completely cleaned out the mailbox, and the plugin is not reporting any messages:

Better Email Debug Connecting to POP Server: KBF Indigo email
Better Email Debug No messages to process
Better Email Debug Logged out from POP server

So I sent a test email to it to see what happened, I have a trigger set up to respond to an email that has "outside lights" in the subject, and I sent an email with that in the subject, but it did not activate the trigger:

Better Email Debug Connecting to POP Server: KBF Indigo email
Better Email Debug Retrieving Message # 1
Better Email Debug Parsing message GmailId15cd20bafbd6689a
Better Email Debug Received Message Subject: outside lights
Better Email Debug Received Message From: Kenneth Frank <[email protected]>
Better Email Debug Received Message To: [email protected]
Better Email Threaddebug checkMsgs: Updating states on server: [{'value': 'Kenneth Frank <[email protected]>', 'key': 'messageFrom'}, {'value': 'outside lights ', 'key': 'messageSubject'}, {'value': '', 'key': 'messageText'}, {'value': 'GmailId15cd20bafbd6689a', 'key': 'lastMessage'}]
Better Email Debug Checking Triggers for Device KBF Indigo email (1441975309)
Better Email Debug Checking Trigger turn on outside lights (534339360), stringMatch
Better Email Debug Checking Device State messageSubject for string: outside lights
Better Email Debug No Match for Trigger turn on outside lights (534339360)
Better Email Debug Deleting Message # 1
Better Email Debug Logged out from POP server

Another question. It says it is deleting the message, and the next time it doesn't process that message. But when I go into my mailbox on gmail or in the mail app, it is physically still in the inbox.

[FlyingDiver]

I've never had any reports that it's not deleting POP messages properly. It might be some sort of race condition within Gmail that it's not showing the updated status right away. If you run the plugin again, does it still think the message is there? Or if you re-open the web interface page, is it still there?

The error you were originally getting might have been caused by the number of messages in the inbox. I never tested the way I store the record of seen messages with that many messages.

[FlyingDiver]

Also, should that trigger have fired? The log is saying no match. Is that correct?

[kennybroh]

There was a match. It should have fired.