I want to make it simple, by using the surrounding services gae team
is proud of,
although many of the surrounding services are lame, I am willing to
believing gae team will make them better soon.
On Sep 11, 9:26 am, Robert Kluin wrote:
> Yeah this is pretty silly; as Jamie mentioned, you're almo
Yeah this is pretty silly; as Jamie mentioned, you're almost certainly
better off using Amazon's service for sending emails. I've never
spoke with anyone who regrets switching. As I recall, various
Googlers have suggested you might be better off using SES, or other
similar services, as well.
R
Yes, I always use a task to send email for exactly this reason. Easily solved,
but really kind of silly.
On Sep 10, 2011, at 5:16 PM, JH wrote:
> This error was happening a year ago when I used to send gae email. I
> get far less urlfetch timeouts when sending via Amazon... If you are
> going
This error was happening a year ago when I used to send gae email. I
get far less urlfetch timeouts when sending via Amazon... If you are
going to email with gae you need to do it via tasks so they will
retry. You will continue to see this mail.send timeout.
On Sep 10, 2:46 pm, Joshua Smith wro
Google's mail api is rather limited and in my experience subject to
being flagged as spam. You may want to try out Amazon's SES. I have
used it with great success. They have methods to inform you if an
email you sent is returned as undeliverable. They also have a high
rate of deliverability.
T
