Alerts Using Gmail as SMTP Server?
I'm trying to set up Alerts to use Gmail as the SMTP server. I have tried using valid Gmail recipient and sender email addresses (though I don't think this matters), a valid Gmail user name and password (with and without the @gmail.com on the end, though I am pretty sure you would need it), with Mail Server Address - smtp.gmail.com and ssl://smtp.gmail.com and Port - 587 (though I have tried them all). None of these configurations have worked. The error in the Log is:
error sending mail: {error,retries_exceeded, {network_failure,"ssl://smtp.gmail.com", {error,nxdomain}}} (repeated 5 times)
or
error sending mail: {error,retries_exceeded, {network_failure,"smtp.gmail.com",{error,timeout}}}
Has anyone been able to successfully configure Alerts to use Gmail for the SMTP server, if so what am I doing wrong? There is a lot of material available indicating that Gmail can be used as a free SMTP server (for example [url]http://geekswithblogs.net/TakeNote/archive/2007/07/16/113974.aspx[/url]), but maybe this just isn't supported by Gmail, or is there an issue with Alerts?
One unfortunate thing I noticed is that regardless of the sender's address, it uses the address associated with my Gmail username.
Thanks Perry. smtp.gmail.com resolves fine. I think the issue is that Amazon is blocking these messages (my NS deployment is on EC2 instances). I am going to get them to raise my message limit and try again.
I am getting the following errors in the logs with my reconfiguration to match what you described above:
error sending mail: {error,retries_exceeded, {network_failure,"smtp.gmail.com",{error,closed}}} (repeated 1 times) ns_mail001 10:40:41 - Mon Aug 16, 2010
error sending mail: {error,retries_exceeded, {network_failure,"smtp.gmail.com",{error,closed}}} ns_mail001 10:35:01 - Mon Aug 16, 2010
Hmm, I'll try to reproduce inside of Amazon (I first tested within my own lab). Let me know if you make any progress.
Perry
I've had Amazon remove my email sending limit, but I am still getting the same error. I've also tried a few different gmail accounts.
"error sending mail: {error,retries_exceeded, {network_failure,"smtp.gmail.com",{error,closed}}} (repeated 3 times)"
Let me know if you have any luck or advise regarding what I might try next. Thanks.
That's pretty weird darryl, I haven't had any trouble. It actually looks like maybe gmail is returning the "retries_exceeded" error. I wonder if it's possible that they blocked access from a particular IP because they saw too much traffic? I don't know if you could get a response out of Google, but perhaps trying it from a completely different system?
I too am seeing this on our various servers. Some more info for you, Perry: we can send using the Gmail account in question via .NET without a problem on these exact servers, so it doesn't seem to be a localized/IP-specific issue. The account in question is a Google Apps account (so, not @gmail.com.) I've tried both ports 25 & 587, as well as with the @ourdomain.com and without to no avail. I also tried with my plain-Jane @gmail.com account to see if it was an issue with Google Apps accounts; it wasn't. I've also tinkered with the firewall rules with no luck.
That's very strange. I've definitely had it working with my own gmail account. Are you receiving the same errors as above?
Darryl, I was able to set this up with my own Gmail account and verified that it worked. As a note, I didn't put the "@gmail.com" on the end of my username and I was able to use ports 25, 587 (but not 2525). I used 'smtp.gmail.com for the mail server address.
I believe the "nxdomain" error is a DNS resolution issue...are you sure the machine that Memcached is running on is able to resolve 'smtp.gmail.com'?
Let me know what else I can do to help.
Perry
Forum support is great for free but sometimes you need a guaranteed response time and dedicated resources for your questions or issues.
Consider purchasing enterprise-level support from Membase: http://www.membase.com/products-and-services/overview
Call or email "sales -at- membase -dot- com" today!