# SMTP failure not reported and too many login attempts on backlog clearing

**URL:** <https://meta.discourse.org/t/smtp-failure-not-reported-and-too-many-login-attempts-on-backlog-clearing/70732>\
**Category:** Product Support\
**Created:** [September 25, 2017, 1:38pm UTC](https://meta.discourse.org/t/smtp-failure-not-reported-and-too-many-login-attempts-on-backlog-clearing/70732 "2017-09-25T13:38:34Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![RBoy](https://avatars.discourse-cdn.com/v4/letter/r/2bfe46/32.png) [@RBoy](https://meta.discourse.org/u/RBoy)\
**Post date:** [July 2, 2019, 3:50pm UTC](https://meta.discourse.org/t/smtp-failure-not-reported-and-too-many-login-attempts-on-backlog-clearing/70732/22 "2019-07-02T15:50:09Z")

</div>

> [@amalg](#):
>
> send multiple emails on a single TCP connection for starters

When I ran into this issue I had a look at the code and from what I could make out the way discourse is designed there isn’t any central queue or email service. Each job just uses a email object to send an email so there isn’t no way to reuse existing connections. If I’m correct this would require a redesign of discourse email to have a centralized email system/queue management to make things more efficient, have a retry mechanism, backoff delays etc.

It would be nice to have those features and infact I think it would be a huge plus to have a centralized email service manager with queue management but that would require redesign and some work.

---

_[View the full topic](https://meta.discourse.org/t/smtp-failure-not-reported-and-too-many-login-attempts-on-backlog-clearing/70732)._