# Email sending failed

**URL:** https://meta.discourse.org/t/email-sending-failed/39801
**Category:** Bug
**Created:** [February 18, 2016, 1:27pm UTC](https://meta.discourse.org/t/email-sending-failed/39801 "2016-02-18T13:27:46Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![javenfang](https://avatars.discourse-cdn.com/v4/letter/j/df705f/32.png) [@javenfang](https://meta.discourse.org/u/javenfang)
#### Post date: [February 18, 2016, 1:27pm UTC](https://meta.discourse.org/t/email-sending-failed/39801/1 "2016-02-18T13:27:46Z")

</div>

For installing discourse with official guideline and env, with many days I encountered email failure.

Latest version upgraded, and failure logs now is shown. The commit - [FIX: don’t create an EmailLog when we can’t send a digest](https://github.com/discourse/discourse/commit/52a66826907bebe81b13ea6bd417f13a05443507)

Now I can see the following error, and it seems it is not due to smtp server error.

Log error is:

```
Job exception: end of file reached

```

The backtrace is:

```
/usr/local/lib/ruby/2.0.0/net/protocol.rb:153:in `read_nonblock'
/usr/local/lib/ruby/2.0.0/net/protocol.rb:153:in `rbuf_fill'
/usr/local/lib/ruby/2.0.0/net/protocol.rb:134:in `readuntil'
/usr/local/lib/ruby/2.0.0/net/protocol.rb:144:in `readline'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:932:in `recv_response'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:555:in `block in do_start'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:942:in `critical'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:555:in `do_start'
/usr/local/lib/ruby/2.0.0/net/smtp.rb:520:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/network/delivery_methods/smtp.rb:112:in `deliver!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/message.rb:2141:in `do_delivery'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/message.rb:236:in `block in deliver'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.5.1/lib/action_mailer/base.rb:543:in `block in deliver_mail'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.5.1/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.5.1/lib/action_mailer/base.rb:541:in `deliver_mail'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/mail-2.6.3/lib/mail/message.rb:236:in `deliver'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionmailer-4.2.5.1/lib/action_mailer/message_delivery.rb:85:in `deliver_now'
/var/www/discourse/lib/email/sender.rb:130:in `send'
/var/www/discourse/app/jobs/regular/user_email.rb:41:in `execute'
/var/www/discourse/app/jobs/base.rb:154:in `block (2 levels) in perform'

```

---

<div class="post-metadata">

### Author: ![downey](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/downey/32/166878_2.png) [@downey](https://meta.discourse.org/u/downey)
#### Post date: [April 6, 2016, 4:08pm UTC](https://meta.discourse.org/t/email-sending-failed/39801/2 "2016-04-06T16:08:06Z")

</div>

I have also been getting this error lately … first I see the following in `/admin`:

> Some problems have been found with your installation of Discourse:  
> Email polling has generated an error in the past 24 hours. Look at the logs for more details.

I actually don’t think the above message is related, but the errors seems to be related to `Jobs::UserEmail` and `Jobs::NotifyMailingListSubscribers`.

---

<div class="post-metadata">

### Author: ![cmtonkinson](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/cmtonkinson/32/108574_2.png) [@cmtonkinson](https://meta.discourse.org/u/cmtonkinson)
#### Post date: [April 29, 2016, 3:47pm UTC](https://meta.discourse.org/t/email-sending-failed/39801/3 "2016-04-29T15:47:55Z")

</div>

Same error here @downey: `end of file reached` is what the JSON returns.

Stack trace the same as @javenfang.
