Closed rknLA closed 12 years ago
Hmm, OK but we have to deal with this anyway. Can't we use any of the older servers as an SMTP relay? Can't we use something directly in rails, say https://github.com/collectiveidea/action_mailer_optional_tls ? We can register api-mailer@safecast.org and then use gmail servers (SMTP or IMAP). Since we don't require a full blown SMTP, if it needs to be, directly writing to a tcp/53 can be coded.
Actually I need my password reset right now, can anybody help? :-|
Kevin,
Do we have keys for Amazon SES?
The best thing here would be to enable SES, enable @safecast.org as a sender, and then never worry about sending email again.
—P
On Tue, Aug 14, 2012 at 4:32 PM, Kalin KOZHUHAROV notifications@github.comwrote:
Hmm, OK but we have to deal with this anyway. Can't we use any of the older servers as an SMTP relay? Can't we use something directly in rails, say https://github.com/collectiveidea/action_mailer_optional_tls ? We can register api-mailer@safecast.org and then use gmail servers (SMTP or IMAP). Since we don't require a full blown SMTP, if it needs to be, directly writing to a tcp/53 can be coded.
Actually I need my password reset right now, can anybody help? :-|
— Reply to this email directly or view it on GitHubhttps://github.com/Safecast/teamdata/issues/3#issuecomment-7729593.
Paul Campbell paul@hypertiny.ie
web http://hypertiny.ie blog http://www.pabcas.com twitter http://www.twitter.com/paulca github http://www.github.com/paulca phone +353 87 914 8162
I don't have AWS permissions to enable Production SES, so Sean, you might have to take care of that.
https://console.aws.amazon.com/ses/home
I tried hooking devise up through our Google Apps account, but haven't gotten it working with that either =\
On Tue, Aug 14, 2012 at 8:58 AM, Paul Campbell notifications@github.comwrote:
Kevin,
Do we have keys for Amazon SES?
The best thing here would be to enable SES, enable @safecast.org as a sender, and then never worry about sending email again.
—P
On Tue, Aug 14, 2012 at 4:32 PM, Kalin KOZHUHAROV notifications@github.comwrote:
Hmm, OK but we have to deal with this anyway. Can't we use any of the older servers as an SMTP relay? Can't we use something directly in rails, say https://github.com/collectiveidea/action_mailer_optional_tls ? We can register api-mailer@safecast.org and then use gmail servers (SMTP or IMAP). Since we don't require a full blown SMTP, if it needs to be, directly writing to a tcp/53 can be coded.
Actually I need my password reset right now, can anybody help? :-|
— Reply to this email directly or view it on GitHub< https://github.com/Safecast/teamdata/issues/3#issuecomment-7729593>.
Paul Campbell paul@hypertiny.ie
web http://hypertiny.ie blog http://www.pabcas.com twitter http://www.twitter.com/paulca github http://www.github.com/paulca phone +353 87 914 8162
— Reply to this email directly or view it on GitHubhttps://github.com/Safecast/teamdata/issues/3#issuecomment-7730451.
Just requested an upgrade, apparently we only had "sandbox" access before. Should take 24 hours to confirm and then I can validate emails from @ safecast.org to any where. -s
On Tue, Aug 14, 2012 at 12:36 PM, kevin nelson notifications@github.comwrote:
I don't have AWS permissions to enable Production SES, so Sean, you might have to take care of that.
https://console.aws.amazon.com/ses/home
I tried hooking devise up through our Google Apps account, but haven't gotten it working with that either =\
On Tue, Aug 14, 2012 at 8:58 AM, Paul Campbell notifications@github.comwrote:
Kevin,
Do we have keys for Amazon SES?
The best thing here would be to enable SES, enable @safecast.org as a sender, and then never worry about sending email again.
—P
On Tue, Aug 14, 2012 at 4:32 PM, Kalin KOZHUHAROV notifications@github.comwrote:
Hmm, OK but we have to deal with this anyway. Can't we use any of the older servers as an SMTP relay? Can't we use something directly in rails, say https://github.com/collectiveidea/action_mailer_optional_tls ? We can register api-mailer@safecast.org and then use gmail servers (SMTP or IMAP). Since we don't require a full blown SMTP, if it needs to be, directly writing to a tcp/53 can be coded.
Actually I need my password reset right now, can anybody help? :-|
— Reply to this email directly or view it on GitHub< https://github.com/Safecast/teamdata/issues/3#issuecomment-7729593>.
Paul Campbell paul@hypertiny.ie
web http://hypertiny.ie blog http://www.pabcas.com twitter http://www.twitter.com/paulca github http://www.github.com/paulca phone +353 87 914 8162
— Reply to this email directly or view it on GitHub< https://github.com/Safecast/teamdata/issues/3#issuecomment-7730451>.
— Reply to this email directly or view it on GitHubhttps://github.com/Safecast/teamdata/issues/3#issuecomment-7737559.
Sean Bonner homebase http://seanbonner.com | twitter http://twitter.com/seanbonner | G+ https://plus.google.com/101629211371073711149/posts | SAFECASThttp://safecast.org
AWS SES is so so so easy.
On Tue, Aug 14, 2012 at 8:36 PM, kevin nelson notifications@github.comwrote:
I don't have AWS permissions to enable Production SES, so Sean, you might have to take care of that.
https://console.aws.amazon.com/ses/home
I tried hooking devise up through our Google Apps account, but haven't gotten it working with that either =\
On Tue, Aug 14, 2012 at 8:58 AM, Paul Campbell notifications@github.comwrote:
Kevin,
Do we have keys for Amazon SES?
The best thing here would be to enable SES, enable @safecast.org as a sender, and then never worry about sending email again.
—P
On Tue, Aug 14, 2012 at 4:32 PM, Kalin KOZHUHAROV notifications@github.comwrote:
Hmm, OK but we have to deal with this anyway. Can't we use any of the older servers as an SMTP relay? Can't we use something directly in rails, say https://github.com/collectiveidea/action_mailer_optional_tls ? We can register api-mailer@safecast.org and then use gmail servers (SMTP or IMAP). Since we don't require a full blown SMTP, if it needs to be, directly writing to a tcp/53 can be coded.
Actually I need my password reset right now, can anybody help? :-|
— Reply to this email directly or view it on GitHub< https://github.com/Safecast/teamdata/issues/3#issuecomment-7729593>.
Paul Campbell paul@hypertiny.ie
web http://hypertiny.ie blog http://www.pabcas.com twitter http://www.twitter.com/paulca github http://www.github.com/paulca phone +353 87 914 8162
— Reply to this email directly or view it on GitHub< https://github.com/Safecast/teamdata/issues/3#issuecomment-7730451>.
— Reply to this email directly or view it on GitHubhttps://github.com/Safecast/teamdata/issues/3#issuecomment-7737559.
Paul Campbell paul@hypertiny.ie
web http://hypertiny.ie blog http://www.pabcas.com twitter http://www.twitter.com/paulca github http://www.github.com/paulca phone +353 87 914 8162
Nice!
I'll be the first to test the working password reset once it is ready :-)
Still "pending verification" from Amazon, but shouldn't be much longer... -s
On Wed, Aug 15, 2012 at 6:38 AM, Kalin KOZHUHAROV notifications@github.comwrote:
Nice!
I'll be the first to test the working password reset once it is ready :-)
— Reply to this email directly or view it on GitHubhttps://github.com/Safecast/teamdata/issues/3#issuecomment-7755932.
Sean Bonner homebase http://seanbonner.com | twitter http://twitter.com/seanbonner | G+ https://plus.google.com/101629211371073711149/posts | SAFECASThttp://safecast.org
Any update on SES?
On Wed, Aug 15, 2012 at 10:11 AM, seanbonner notifications@github.comwrote:
Still "pending verification" from Amazon, but shouldn't be much longer... -s
On Wed, Aug 15, 2012 at 6:38 AM, Kalin KOZHUHAROV notifications@github.comwrote:
Nice!
I'll be the first to test the working password reset once it is ready :-)
— Reply to this email directly or view it on GitHub< https://github.com/Safecast/teamdata/issues/3#issuecomment-7755932>.
Sean Bonner homebase http://seanbonner.com twitter http://twitter.com/seanbonner G+ https://plus.google.com/101629211371073711149/posts SAFECASThttp://safecast.org
- I'm no longer on Facebook, here's whyhttp://blog.seanbonner.com/2012/04/15/on-leaving-facebook/ .
—
Reply to this email directly or view it on GitHubhttps://github.com/Safecast/teamdata/issues/3#issuecomment-7762107.
SES was approved several days ago (told Paul) but DKIM keeps being rejected, have resubmitted again..
On Tue, Aug 21, 2012 at 2:02 PM, kevin nelson notifications@github.comwrote:
Any update on SES?
On Wed, Aug 15, 2012 at 10:11 AM, seanbonner notifications@github.comwrote:
Still "pending verification" from Amazon, but shouldn't be much longer... -s
On Wed, Aug 15, 2012 at 6:38 AM, Kalin KOZHUHAROV notifications@github.comwrote:
Nice!
I'll be the first to test the working password reset once it is ready :-)
— Reply to this email directly or view it on GitHub< https://github.com/Safecast/teamdata/issues/3#issuecomment-7755932>.
Sean Bonner homebase http://seanbonner.com twitter < http://twitter.com/seanbonner> G+ https://plus.google.com/101629211371073711149/posts SAFECASThttp://safecast.org
- I'm no longer on Facebook, here's whyhttp://blog.seanbonner.com/2012/04/15/on-leaving-facebook/ .
—
Reply to this email directly or view it on GitHub< https://github.com/Safecast/teamdata/issues/3#issuecomment-7762107>.
— Reply to this email directly or view it on GitHubhttps://github.com/Safecast/teamdata/issues/3#issuecomment-7916077.
Sean Bonner homebase http://seanbonner.com | twitter http://twitter.com/seanbonner | G+ https://plus.google.com/101629211371073711149/posts | SAFECASThttp://safecast.org
It should be working now.
On Tue, Aug 21, 2012 at 10:51 PM, seanbonner notifications@github.comwrote:
SES was approved several days ago (told Paul) but DKIM keeps being rejected, have resubmitted again..
On Tue, Aug 21, 2012 at 2:02 PM, kevin nelson notifications@github.comwrote:
Any update on SES?
On Wed, Aug 15, 2012 at 10:11 AM, seanbonner notifications@github.comwrote:
Still "pending verification" from Amazon, but shouldn't be much longer... -s
On Wed, Aug 15, 2012 at 6:38 AM, Kalin KOZHUHAROV notifications@github.comwrote:
Nice!
I'll be the first to test the working password reset once it is ready :-)
— Reply to this email directly or view it on GitHub< https://github.com/Safecast/teamdata/issues/3#issuecomment-7755932>.
Sean Bonner homebase http://seanbonner.com twitter < http://twitter.com/seanbonner> G+ https://plus.google.com/101629211371073711149/posts SAFECASThttp://safecast.org
- I'm no longer on Facebook, here's whyhttp://blog.seanbonner.com/2012/04/15/on-leaving-facebook/ .
—
Reply to this email directly or view it on GitHub< https://github.com/Safecast/teamdata/issues/3#issuecomment-7762107>.
— Reply to this email directly or view it on GitHub< https://github.com/Safecast/teamdata/issues/3#issuecomment-7916077>.
Sean Bonner homebase http://seanbonner.com twitter http://twitter.com/seanbonner G+ https://plus.google.com/101629211371073711149/posts SAFECASThttp://safecast.org
- I'm no longer on Facebook, here's whyhttp://blog.seanbonner.com/2012/04/15/on-leaving-facebook/ .
— Reply to this email directly or view it on GitHubhttps://github.com/Safecast/teamdata/issues/3#issuecomment-7917671.
Paul Campbell paul@hypertiny.ie
web http://hypertiny.ie blog http://www.pabcas.com twitter http://www.twitter.com/paulca github http://www.github.com/paulca phone +353 87 914 8162
Indeed the email is sent, but the url in the email is invalid.
Closing this issue, since it only related to the inability to receive email. Opening a new one shortly.
Here's EngineYard's rationality for not supporting SMTP out of the box. https://support.cloud.engineyard.com/entries/21016513-set-up-ssmtp-for-mail-relay-to-authsmtp
Looks like we'll need something like SendGrid to handle that.