我的应用程序有一个联系页面,用户可以在其中输入他们的名称/电子邮件/主题/内容并给我发送消息。我将Sendgrid插件用于heroku,并认为我已经完成了几乎所有的事情。我在我的Heroku部署的应用程序与Sendgrid错误没有日志信息
emails_controller.rb
if @email.save
ContactMailer.contact_message(@email).deliver
flash.now[:success] = "Your email has sent! I'll try to get back to you shortly."
render :new
else
flash.now[:error] = "Please correct the highlighted errors and try again."
render :new
end
(这里的想法是让每封电子邮件的记录,并也将其发送给我)有这个。
我的配置/初始化/ mail.rb
# SendGrid Settings
ActionMailer::Base.smtp_settings = {
:address => 'smtp.sendgrid.net',
:port => '587',
:authentication => :plain,
:enable_starttls_auto => true,
:user_name => ENV['SENDGRID_USERNAME'],
:password => ENV['SENDGRID_PASSWORD'],
:domain => 'myappname.com'
}
ActionMailer::Base.delivery_method = :smtp
然后,好措施,下面什么别人在sendgrid支持的问题一样。配置/环境/ production.rb:
config.action_mailer.default_url_options = { :host => 'myappname.com' }
我contact_email.html.erb:
class Contact < ActionMailer::Base
default from: "[email protected]"
def contact_message(email)
@name = email.name
@address = email.address
@subject = email.subject
@content = email.content
mail(:to => ENV['EMAIL_ADDRESS'], :subject => @subject)
end
end
我添加了所有必要的环境变量,通过
heroku config:add [email protected]
heroku config:add SENDGRID_USERNAME=blah
当我推到的Heroku和尽管给自己发一封电子邮件,但它给了我“我们很抱歉,出现了一些错误”的死亡屏幕,并且日志(对我来说)完全没有用处。
下面是从我上次推送到heroku并尝试向自己发送电子邮件时开始的日志。任何想法可能出错?
2013-02-03T20:34:18+00:00 heroku[router]: at=info method=GET path=/ host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=0ms connect=7ms service=201ms status=304 bytes=0
2013-02-03T20:34:18+00:00 heroku[router]: at=info method=GET path=/assets/application-cd9c41b78562d03bb04bcaaa585b31e8.js host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=0ms connect=1ms service=11ms status=200 bytes=125507
2013-02-03T20:34:19+00:00 heroku[router]: at=info method=GET path=/assets/pig3-b2d5155bd2811a87cafec6a447459580.png host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=0ms connect=1ms service=4ms status=200 bytes=3010
2013-02-03T20:34:19+00:00 heroku[router]: at=info method=GET path=/assets/github-e8c3b3f49b0cc737afe9b3cd6e9ab159.png host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=0ms connect=1ms service=4ms status=200 bytes=3687
2013-02-03T20:34:19+00:00 heroku[router]: at=info method=GET path=/assets/odesk2-38dadc2e6b0e94aa6c6766df301716bc.png host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=1ms connect=2ms service=4ms status=200 bytes=3932
2013-02-03T20:34:19+00:00 heroku[router]: at=info method=GET path=/assets/star-02718a47b29575c2d7a0e75ac8bebf4d.png host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=0ms connect=2ms service=4ms status=200 bytes=3104
2013-02-03T20:34:19+00:00 heroku[router]: at=info method=GET path=/assets/empty_star-9bf002077eafec40cf239068f7d4d1ca.png host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=0ms connect=1ms service=43ms status=200 bytes=3072
2013-02-03T20:34:23+00:00 heroku[router]: at=info method=GET path=/emails/new host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=0ms connect=1ms service=119ms status=200 bytes=3022
2013-02-03T20:34:23+00:00 heroku[router]: at=info method=GET path=/assets/application-74fd2354261a1131b26861b47bef1d87.css host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=0ms connect=2ms service=4ms status=304 bytes=0
2013-02-03T20:34:19+00:00 heroku[router]: at=info method=GET path=/assets/headshot-767c8913c7af4fc97cb8e15881884f0e.png host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=4ms connect=6ms service=11ms status=200 bytes=146892
2013-02-03T20:34:39+00:00 heroku[router]: at=info method=POST path=/emails host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=0ms connect=7ms service=131ms status=500 bytes=643
2013-02-03T20:34:39+00:00 heroku[router]: at=info method=GET path=/favicon.ico host=<appname>-2591.herokuapp.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=1ms connect=3ms service=5ms status=200 bytes=0
而且,我确实添加了Sendgrid(跟随Heroku的说明),以及Sendgrid用户界面不显示发送的电子邮件。而最后一次尝试此操作时,以下行似乎是heroku日志中唯一一个在我尝试发送其他邮件时相关时间戳的行。不是非常有帮助:
2013-02-04T18:15:45+00:00 heroku[router]: at=info method=GET path=/contact host=myappname.com fwd=69.181.104.85 dyno=web.1 queue=0 wait=0ms connect=2ms service=334ms status=200 bytes=3695
刚刚添加了最后一行。我100%的用户名是准确的,并且Sendgrid密码没有添加任何内容(并且出于某种原因,Sendgrid的仪表板表示我无法访问我的帐户详细信息),所以我认为这是正确的。我会再试一次,看看它是否会引发任何有趣的错误。谢谢! – Sasha
这有什么更新? – Swift
是的!你的第一个建议已经死了。出于某种原因,该密码已关闭,尽管我无法(并且仍然无法)访问我的帐户设置,但我能够重置密码并将其更改为其他内容。当我这样做时,电子邮件就像魔术一样发送。 (忘记检查直到现在,因此推迟更新)。谢谢! – Sasha