Question

我的应用程序有一个联系页面，用户可以在其中输入他们的姓名/电子邮件/主题/内容并向我发送消息。我正在使用Sendgrid插件到heroku，并认为我已经做了几乎所有的事情。我在我的

中得到了这个

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

（这里的想法是记录每封电子邮件并发送给我）。

我的config / initializers / 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: "unimportant@example.com"

  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_ADDRESS=blah@blah.com
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

此外，我DID添加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

Answer 1

由于它没有出现在您的SendGrid信息中心，我的猜测是您的凭据在应用中是错误的。如果您输入heroku config，您是否看到SENDGRID_USERNAME和SENDGRID_PASSWORD设置正确？

此外，您可能希望尝试设置传递错误以显示在配置文件中。

config.action_mailer.raise_delivery_errors = true

Answer 2

为了澄清一点，您无法访问SendGrid网站上的帐户设置，因为Heroku已将其锁定。您可以直接从Heroku界面调整相同的设置。

Heroku使用Sendgrid错误部署应用程序而没有日志信息

2 个答案: