Reprocessed emails, take 2

Posted on
Fri Apr 26, 2019 12:09 pm
jtburgess offline
User avatar
Posts: 77
Joined: Jan 17, 2018
Location: NJ

Reprocessed emails, take 2

(My first post got lost, evidently due to UTF-8 characters that indigo/mysql/??? wasn't able to handle...)

A few days ago Better Email reprocessed several emails that were not in my inbox and had arrived several days-to-hours earlier.
I haven't seen this behavior since I "fixed" the configuration to move processed emails to the "Archive" folder, so this seems to be a very rare occurrence.

As you'll see below, this accesses a comcast.net IMAP email server, and this is the only client accessing that account, for what its worth.

I am still running Indigo 7.1.1, and Better Email 7.2.4.

$ grep 'Pittstown IMAP: Received Message' 2019-04-21\ Events.txt
2019-04-21 08:58:43.256 Better Email Pittstown IMAP: Received Message Subject: Motion detected on wyzecam1
2019-04-21 08:58:43.256 Better Email Pittstown IMAP: Received Message From: Wyze via IFTTT <action@ifttt.com>
2019-04-21 08:58:43.257 Better Email Pittstown IMAP: Received Message To: pittstown@comcast.net
2019-04-21 08:58:43.257 Better Email Pittstown IMAP: Received Message Date: Sat, 13 Apr 2019 04:13:10 +0000 (UTC)
2019-04-21 08:58:44.280 Better Email Pittstown IMAP: Received Message Subject: For a limited time: switch to solar + get a $1,000 Prepaid Card!
2019-04-21 08:58:44.281 Better Email Pittstown IMAP: Received Message From: Xfinity
2019-04-21 08:58:44.282 Better Email Pittstown IMAP: Received Message To: pittstown@comcast.net
2019-04-21 08:58:44.282 Better Email Pittstown IMAP: Received Message Date: Wed, 17 Apr 2019 11:38:20 -0700
2019-04-21 08:58:45.181 Better Email Pittstown IMAP: Received Message Subject: Motion detected on wyzecam1
2019-04-21 08:58:45.181 Better Email Pittstown IMAP: Received Message From: Wyze via IFTTT <action@ifttt.com>
2019-04-21 08:58:45.182 Better Email Pittstown IMAP: Received Message To: pittstown@comcast.net
2019-04-21 08:58:45.182 Better Email Pittstown IMAP: Received Message Date: Thu, 18 Apr 2019 03:47:43 +0000 (UTC)
2019-04-21 08:58:46.075 Better Email Pittstown IMAP: Received Message Subject: Motion detected on wyzecam1
2019-04-21 08:58:46.076 Better Email Pittstown IMAP: Received Message From: Wyze via IFTTT <action@ifttt.com>
2019-04-21 08:58:46.077 Better Email Pittstown IMAP: Received Message To: pittstown@comcast.net
2019-04-21 08:58:46.078 Better Email Pittstown IMAP: Received Message Date: Fri, 19 Apr 2019 03:45:33 +0000 (UTC)
2019-04-21 08:58:47.078 Better Email Pittstown IMAP: Received Message Subject: Full tank but NEVER full price. Learn how.
2019-04-21 08:58:47.079 Better Email Pittstown IMAP: Received Message From: "GasBuddy" <et-reply@GasBuddyEmail.com>
2019-04-21 08:58:47.079 Better Email Pittstown IMAP: Received Message To: <pittstown@comcast.net>
2019-04-21 08:58:47.080 Better Email Pittstown IMAP: Received Message Date: Fri, 19 Apr 2019 11:35:03 -0600
2019-04-21 08:58:47.963 Better Email Pittstown IMAP: Received Message Subject: Motion detected on wyzecam1
2019-04-21 08:58:47.964 Better Email Pittstown IMAP: Received Message From: Wyze via IFTTT <action@ifttt.com>
2019-04-21 08:58:47.965 Better Email Pittstown IMAP: Received Message To: pittstown@comcast.net
2019-04-21 08:58:47.965 Better Email Pittstown IMAP: Received Message Date: Sat, 20 Apr 2019 03:49:27 +0000 (UTC)
2019-04-21 08:58:49.060 Better Email Pittstown IMAP: Received Message Subject: Why our monthly prices are changing
2019-04-21 08:58:49.061 Better Email Pittstown IMAP: Received Message From: Netflix <info@mailer.netflix.com>
2019-04-21 08:58:49.061 Better Email Pittstown IMAP: Received Message To: pittstown@comcast.net
2019-04-21 08:58:49.062 Better Email Pittstown IMAP: Received Message Date: Sat, 20 Apr 2019 09:52:13 +0000
2019-04-21 08:58:49.973 Better Email Pittstown IMAP: Received Message Subject: Add MLB Extra Innings today
2019-04-21 08:58:49.974 Better Email Pittstown IMAP: Received Message From: Xfinity
2019-04-21 08:58:49.974 Better Email Pittstown IMAP: Received Message To: pittstown@comcast.net
2019-04-21 08:58:49.975 Better Email Pittstown IMAP: Received Message Date: Sat, 20 Apr 2019 12:00:08 -0700
2019-04-21 08:58:50.948 Better Email Pittstown IMAP: Received Message Subject: Motion detected on wyzecam1
2019-04-21 08:58:50.949 Better Email Pittstown IMAP: Received Message From: Wyze via IFTTT <action@ifttt.com>
2019-04-21 08:58:50.949 Better Email Pittstown IMAP: Received Message To: pittstown@comcast.net
2019-04-21 08:58:50.950 Better Email Pittstown IMAP: Received Message Date: Sun, 21 Apr 2019 03:45:39 +0000 (UTC)


Questions:
  1. Any idea what caused this, and what I can do to prevent it from happening again?
  2. I only need Better Email to process the Wyze alerts. I have Mail.app rules to deal with Xfinity, Netflix, etc. but they aren't working.
    Can I get Better Email to ignore messages that don't match the Trigger condition so the Mail.app rule will work? Or here's another idea. Can I trigger a Better Email Trigger from a Mail.app Rule?

Posted on
Fri Apr 26, 2019 12:39 pm
FlyingDiver offline
User avatar
Posts: 7189
Joined: Jun 07, 2014
Location: Southwest Florida, USA

Re: Reprocessed emails, take 2

I'm confused. You say that BetterEmail is the only client accessing this account (pittstown@comcast.net), but then you talk about Mail.app rules. Is this account also set up in Mail.app or not? Because BetterEmail doesn't know anything about Mail.app rules.

You're using the "Move messages after processing option", right? Try turning on the "process all messages" option. I know it says testing only, but that's really only necessary if you're leaving messages in the INBOX. Processing all is no big deal if you keep the INBOX empty.

I'm not sure how to answer your other question because of the contradiction above. I would recommend NOT trying to use the same email address/INBOX for both BetterEmail and Mail.app rules. If the email address is dedicated to Indigo, there should be no reason to do so. Having two different clients attempt to process the same INBOX is going to be tricky, because you really don't have any control of which gets there first.

I think what you're really asking for is to make the post-processing options (leave, move, delete) dependent on trigger processing. That's possible to implement, I think, but can't be done with the current plugin. If that's what you need, please file an enhancement request on GitHub with specific scenarios that you're trying to handle.

joe (aka FlyingDiver)
my plugins: http://forums.indigodomo.com/viewforum.php?f=177

Page 1 of 1

Who is online

Users browsing this forum: No registered users and 2 guests

cron