6 ms·

At least a few reported that it was bouncing at the destination once they set up an appropriate handler. They are only "not being sent" when there is a url in t

by daveguy 11y ago

At least a few reported that it was bouncing at the destination once they set up an appropriate handler. They are only "not being sent" when there is a url in the message and that is a big red flag on the receiving side (not much text but a url). It doesn't look like an App Engine problem. It looks like messages being identified as spam problem.

markdown 11y ago
Not the case for me. No bounces being reported. In any case, gmail and outlook don't bounce messages for spam; They put them in the spam bin. Nothing whatsoever changed in my code. I haven't touched it in a year, and all of sudden email stopped on the 1st of April. There's nothing in the changelogs to indicate there was a change that should cause this behaviour. It's absolutely an App Engine problem. https://cloud.google.com/appengine/docs/python/release-notes https://cloud.google.com/appengine/docs/python/release-notes
- daveguy 11y ago
  Interesting. I have been somewhat weary of the "machine learning for everything!" approach that google has taken recently -- i just don't think it's there yet. I wonder if a learning algorithm on the google side just started deciding outgoing spam and not giving correct feedback. It is very curious that no url works and with url doesn't. That should give straightforward repeatability (if they can simulate as your account). Have you tried sending to different target e-mail addresses during the test? I saw once it just worked and a bunch of stuff flew through. Also saw there was some question as to quotas. Did you get it clarified? Are you maybe above usage quotas with the regular e-mails so test e-mails are being stopped/delayed? Are test and production separate? It seems like if it were a google side issue there would be an uproar from the users.
- djsumdog 11y ago
  No, gmail constantly drops messages without putting them in spam. That's actually a huge problem. Microsoft does the same. That's for e-mails that don't even contain any links!
jlees 11y ago
I ran into a similar problem a while back (using Heroku) --- after a brief foray into the world of spam filtering, it turned out to be caused by our domain being identified by SpamAssassin (IIRC) as a spam signal. We changed the wording of our emails and moved to a different subdomain and suddenly all the email got through. It was.. interesting to debug.

by daveguy 11y ago

markdown 11y ago

Not the case for me. No bounces being reported. In any case, gmail and outlook don't bounce messages for spam; They put them in the spam bin. Nothing whatsoever changed in my code. I haven't touched it in a year, and all of sudden email stopped on the 1st of April. There's nothing in the changelogs to indicate there was a change that should cause this behaviour. It's absolutely an App Engine problem. https://cloud.google.com/appengine/docs/python/release-notes https://cloud.google.com/appengine/docs/python/release-notes

daveguy 11y ago
Interesting. I have been somewhat weary of the "machine learning for everything!" approach that google has taken recently -- i just don't think it's there yet. I wonder if a learning algorithm on the google side just started deciding outgoing spam and not giving correct feedback. It is very curious that no url works and with url doesn't. That should give straightforward repeatability (if they can simulate as your account). Have you tried sending to different target e-mail addresses during the test? I saw once it just worked and a bunch of stuff flew through. Also saw there was some question as to quotas. Did you get it clarified? Are you maybe above usage quotas with the regular e-mails so test e-mails are being stopped/delayed? Are test and production separate? It seems like if it were a google side issue there would be an uproar from the users.
djsumdog 11y ago
No, gmail constantly drops messages without putting them in spam. That's actually a huge problem. Microsoft does the same. That's for e-mails that don't even contain any links!

jlees 11y ago

I ran into a similar problem a while back (using Heroku) --- after a brief foray into the world of spam filtering, it turned out to be caused by our domain being identified by SpamAssassin (IIRC) as a spam signal. We changed the wording of our emails and moved to a different subdomain and suddenly all the email got through. It was.. interesting to debug.