Hi Donald,

I've never seen this error but I have read this:

http://stackoverflow.com/questions/3038852/ruby-mailer-is-coming-up-with-an-eoferror

Could you try changing your email SMTP server to another one?

What if you disable the external SMTP (like in test mode)?

  # Tell Action Mailer not to deliver emails to the real world.
  # The :test delivery method accumulates sent emails in the
  # ActionMailer::Base.deliveries array.
  config.action_mailer.delivery_method = :test

Does the error happen then?

Regards,
Ignacio


El 09/09/13 21:39, Donald Ziesig escribió:
> Hi Everyone,
> 
> This is driving me crazy.
> 
> When I sign up a new user in production mode, I get the following error:
> 
> Sent mail to [email protected](30897ms)  <<<< never arrived
> Completed 500 Internal Server Error in 31129ms
> 
> EOFError (end of file reached):
>   app/models/user.rb:33:in `block (2 levels) in <class:User>'
> 
> When I sign up a new user in development mode, but with
> raise_delivery_errors => true,
> I get the same error but the e-mail generated (which production doesn't
> show) is correct and the activation link works as expected.
> 
> I have not changed any of the code associated with <class:User> or the
> mailer from that generated by hobo.
> 
> I have found references to a similar error (not associated with hobo)
> that has been traced to an improperly formatted email, but, as I said,
> the hobo-generated email looks good.
> 
> Does anyone have any idea how to troubleshoot this further?
> 
> Thanks,
> 
> Don Ziesig
> 
> 
> 

-- 
Ignacio Huerta Arteche
http://www.ihuerta.net
Teléfono: 0034 645 70 77 35
Email realizado con software libre

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to