Unfortunately, you have to work around Microsoft's VERY flawed Outlook rules implementation. Microsoft thinks... Ohhh, if we just send several hundred of those appspot.com emails to the Junk folder, we've done our job. But they forget, they also mistakenly
send valid emails to the Junk folder as well. So you (as their captive user) have to wade through hundreds of Junk emails each day before you delete all of your Junk emails so you don't accidentally delete that one email they mistakenly sent to your Junk folder
(which you needed).
The way I have gotten around this is that you have to create a "Junk" folder rule that makes
something.appspot.com a trusted email/safe. This is because Microsoft's lame rules for the Junk folder won't allow using just "appspot.com" when creating a rule. It doesn't recognize that
form as valid. What a bunch of ****...
So that "something" I use is the last letter in the email address just prior to ".appspot.com". For example, if you're getting emails from something like "nnv$#cv*7qa.wrtvu.appspot.com"
create a trusted/safe rule for your Junk folder with a "Sender's address containing" "u.appspot.com". By just using the last letter "u" preceding ".appspot.com" it gets around Microsoft's email address validation **** rules;
and it ignores any characters before the last letter (which appspot frequently changes). This causes Outlook to send the email to your Inbox. By the way, right now, the **** coming from appspot.com is preceded by the letter "r". So I've created a trusted/safe
Junk rule that looks like "r.appspot.com".
Now, once the email heads to your Inbox rather than the LAME Junk folder, you can use the more powerful Inbox rules to
delete those **** emails with a "Senders address contains" Rule that has "r.appspot.com". Every appspot.com email that contains the letters "r.appspot.com" characters in it, regardless of what precedes those characters, will then be deleted
by Outlook. So far I have about 7 Junk trusted/safe rules with matching Inbox rules that are deleting the appspot.com emails. Before I did this, I was getting around 400 - 600 emails per day from appspot.com. Also, by the way, for some reason, it sometimes
takes these rules a day or so to take effect.
Too bad we have to do all this for a really poor rule implementation in Outlook. Hey, Microsoft, WAKE UP AND SMELL THE COFFEE! This is a real problem and your implementation of Outlook rules is really, really, really LAME! I strongly recommend Microsoft
get some real Product Managers to fix Outlooks rules problem. It's making Outlook more and more useless. And I'm certain this isn't an engineering problem; but more of a leadership issue.