Note that there are some explanatory texts on larger screens.

plurals
  1. POSegmentation Fault when sending a simple mail from Rails 3.2
    primarykey
    data
    text
    <p>So I'm not quite sure what to do here.</p> <p>I've got a simple application that's basically done, it's main purpose is to collect RSVPs for a wedding. I set up a simple Mailer to notify me whenever a new RSVP is entered, which looks like in the log it works. However whenever I actually tell it to perform deliveries in dev, there's a segmentation fault and the rails server crashes. I posted a bug in the rails project over on github, and they said it's something to do with my interaction with OpenSSL, which I didn't think I was using. (this is a from scratch rails 3.2 app, nothing special or weird configuration wise)</p> <pre><code> config.action_mailer.default_url_options = { :host =&gt; 'gmail.com' } config.action_mailer.delivery_method = :smtp config.action_mailer.smtp_settings = { :address =&gt; "smtp.gmail.com", :domain =&gt; 'gmail.com', :port =&gt; 587, :user_name =&gt; 'user@gmail.com', :password =&gt; 'secret', :authentication =&gt; 'plain', :enable_starttls_auto =&gt; true } config.action_mailer.raise_delivery_errors = true </code></pre> <p>it produces a giant log, which is posted over at github: <a href="https://github.com/rails/rails/issues/5115" rel="nofollow">https://github.com/rails/rails/issues/5115</a></p> <p>So I'm not sure where to go from here. I installed the openssl package from rvm, which successfully built and installed, and I also tried removing <code>enable_starttls_auto</code> from the config file at the github suggestion, but it just keeps crashing.</p> <p>I'm running Ruby 1.9.3-p0 through RVM, and rails 3.2.0 on OS X Lion</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload