# Failed email status only after three attempts

**URL:** <https://forum.mautic.org/t/failed-email-status-only-after-three-attempts/23522>\
**Category:** General Discussion\
**Created:** [April 3, 2022, 9:49am UTC](https://forum.mautic.org/t/failed-email-status-only-after-three-attempts/23522 "2022-04-03T09:49:13Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![silavapi](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.mautic.org/silavapi/32/7424_2.png) [@silavapi](https://forum.mautic.org/u/silavapi)\
**Post date:** [July 15, 2022, 12:39pm UTC](https://forum.mautic.org/t/failed-email-status-only-after-three-attempts/23522/22 "2022-07-15T12:39:45Z")

</div>

Hi folks!

We have a PR to mark emails as failed if they fail, and not set DNC:

> <https://github.com/mautic/mautic/pull/11285>
>
> \<!-- ## Which branch should I use for my PR?
> 
> Assuming that:
> 
> a = current ma…jor release
> b = current minor release
> c = future major release
> 
> \* a.x for any features and enhancements (e.g. 4.x)
> \* a.b for any bug fixes (e.g. 4.0, 4.1, 4.2)
> \* c.x for any features, enhancements or bug fixes with backward compatibility breaking changes (e.g. 5.x) --\>
> 
> | Q | A
> | -------------------------------------- | ---
> | Bug fix? (use the a.b branch) | \[\]
> | New feature/enhancement? (use the a.x branch) | \[\]
> | Deprecations? | \[\]
> | BC breaks? (use the c.x branch) | \[\]
> | Automated tests included? | \[\] 
> | Related user documentation PR URL | mautic/mautic-documentation#... 
> | Related developer documentation PR URL | mautic/developer-documentation#... 
> | Issue(s) addressed | Fixes #... 
> 
> \<!--
> Additionally (see https://contribute.mautic.org/contributing-to-mautic/developer/code/pull-requests#work-on-your-pull-request):
> - Always add tests and ensure they pass.
> - Bug fixes must be submitted against the lowest maintained branch where they apply
> (lowest branches are regularly merged to upper ones so they get the fixes too.)
> - Features and deprecations must be submitted against the "4.x" branch.
> \--\>
> 
> \#### Description:
> 
> \<!--
> Please write a short README for your feature/bugfix. This will help people understand your PR and what it aims to do. If you are fixing a bug and if there is no linked issue already, please provide steps to reproduce the issue here.
> \--\>
> 
> \#### Steps to test this PR:
> 
> On email failed we set contact to DNC. 
> But failed send email could have a lot of reasons (smtp timeout etc). 
> Then I suggest mark email as failed and do not set contact as DNC.
> 
> \<!--
> This part is really important. If you want your PR to be merged, take the time to write very clear, annotated and step by step test instructions. Do not assume any previous knowledge - testers may not be developers.
> \--\>
> 1. Open this PR on Gitpod or pull down for testing locally (see docs on testing PRs \[here\](https://contribute.mautic.org/contributing-to-mautic/tester))
> 2. Hard to tell how to reproduce. Need make failed send email
> 3. Probably code review and unit tests are enoiught
> 
> \<!--
> If you have any deprecations, list them here along with the new alternative.
> If you have any backwards compatibility breaks, list them here.
> \--\>
> 
> 
> \<a href="https://gitpod.io/#https://github.com/mautic/mautic/pull/11285"\>\<img src="https://gitpod.io/button/open-in-gitpod.svg"/\>\</a\>

We would value testing and your thoughts!

Here’s how to test:

> **[Tester](https://contribute.mautic.org/contributing-to-mautic/tester#the-easy-way-using-gitpod)**
>
> . Every new feature and bug fix that is released in Mautic has undergone testing and code review by members of the community before it makes it into a release.We are always looking out for people to help us with these processes. Even if you can spare...

---

_[View the full topic](https://forum.mautic.org/t/failed-email-status-only-after-three-attempts/23522)._