Answers.Body: <p>I was just encountering the same problem ...</p>
  
  <p>There is already an issue on github: <a href="https://github.com/civicrm/org.civicrm.flexmailer/issues/23" rel="nofollow noreferrer">https://github.com/civicrm/org.civicrm.flexmailer/issues/23</a></p>
  
  <p>It would be really helpful to get that solved. Currently, as workaround, I am switching to PHP mail(), which I expect to cause problems regarding spam reputation...</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-02-06T09:35:13.513Z
Answers.Text: Unfortunately, the github issue link now says: "This repository has been archived by the owner on Feb 6, 2023. It is now read-only. "
  So probably, where is no hope for a change. 
  I wonder why not more are encountering the problem. We did not have this issue since our last CiviCRM upgrade, where we updated from a quite old version.
Answers.UserDisplayName: Weidenrinde
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-10-31T11:37:07.197Z
Answers.Text: I have the same problem. Where can [this issue](https://github.com/civicrm/org.civicrm.flexmailer/issues/23) be reported now?
Answers.UserDisplayName: masetto
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-11-05T06:45:23.577Z
Answers.Text: @masetto do you you that issue on a current version of civicrm? In this case, you should file a new issue in gitlab: https://lab.civicrm.org/groups/dev/-/issues
  
  (without diving deeper into it, I believe the underlying problem was solved some time ago... but if you still see that issue, you should report it again!)
Answers.UserDisplayName: Detlev Sieber
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-11-14T17:44:32.850Z
Answers.Text: Thanks @DetlevSieber, I opened [this issue](https://lab.civicrm.org/dev/core/-/issues/5586).
Answers.UserDisplayName: masetto
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-06-04T16:28:48.467Z
Answers.LastActivityDate: 2020-06-04T16:28:48.467Z
Answers.UserDisplayName: Detlev Sieber
Body: <p>When a CiviMail job is running, if one of the recipients has a bad email address, the CiviMail processor throws a set of errors into the Drupal watchdog log, with this message:</p>
  
  <p>SMTP Socket Error or failed to set sender error. Message: Failed to add recipient: ted@jessicommunity.org [SMTP: Invalid response code received from SMTP server while sending email.  This is often caused by a misconfiguration in Outbound Email settings. Please verify the settings at Administer CiviCRM >> Global Settings >> Outbound Email (SMTP). (code: 450, response: 4.1.2 : Recipient address rejected: Domain not found)], Code: 10005</p>
  
  <p>There seem to be two problems.</p>
  
  <p>First, the error message seems to be misleading by suggesting that the problem is a misconfiguration in Outbound Email settings, which doesn't offer any settings related to handling unfound domains.</p>
  
  <p>The more serious problem is that CiviMail will keep trying this address every time the CiviMail processor runs, thereby it will never complete the job and fills the watchdog log with error messages. The only way to stop the loop without actually cancelling the mailing job is to delete the relevant row in civicrm_mailing_event_queue (and then put the offending email on hold to prevent it from happening in the future).</p>
  
  <p>It seems like the proper behavior would be for CiviCRM to treat that error like a bounce; but certainly not to keep trying it over and over.</p>
  
  <p>Is that the appropriate behavior?</p>
  
Tags: <civimail>
Title: SMTP Socket Error or failed to set sender error....Recipient address rejected: Domain not found; CiviMail keeps trying
ThreadText: # SMTP Socket Error or failed to set sender error....Recipient address rejected: Domain not found; CiviMail keeps trying
  
  (Asked by: username_0 on 2020-05-12)
  
  When a CiviMail job is running, if one of the recipients has a bad email address, the CiviMail processor throws a set of errors into the Drupal watchdog log, with this message:
  
  SMTP Socket Error or failed to set sender error. Message: Failed to add recipient: ted@jessicommunity.org [SMTP: Invalid response code received from SMTP server while sending email. This is often caused by a misconfiguration in Outbound Email settings. Please verify the settings at Administer CiviCRM >> Global Settings >> Outbound Email (SMTP). (code: 450, response: 4.1.2 : Recipient address rejected: Domain not found)], Code: 10005
  
  There seem to be two problems.
  
  First, the error message seems to be misleading by suggesting that the problem is a misconfiguration in Outbound Email settings, which doesn't offer any settings related to handling unfound domains.
  
  The more serious problem is that CiviMail will keep trying this address every time the CiviMail processor runs, thereby it will never complete the job and fills the watchdog log with error messages. The only way to stop the loop without actually cancelling the mailing job is to delete the relevant row in civicrm\_mailing\_event\_queue (and then put the offending email on hold to prevent it from happening in the future).
  
  It seems like the proper behavior would be for CiviCRM to treat that error like a bounce; but certainly not to keep trying it over and over.
  
  Is that the appropriate behavior?
  
  **Tags:** civimail
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-06-04. Score: 2
  
  I was just encountering the same problem ...
  
  There is already an issue on github: <https://github.com/civicrm/org.civicrm.flexmailer/issues/23>
  
  It would be really helpful to get that solved. Currently, as workaround, I am switching to PHP mail(), which I expect to cause problems regarding spam reputation...
  
  > **Comments:**
  > **username_2**: Unfortunately, the github issue link now says: "This repository has been archived by the owner on Feb 6, 2023. It is now read-only. " So probably, where is no hope for a change.  I wonder why not more are encountering the problem. We did not have this issue since our last CiviCRM upgrade, where we updated from a quite old version.  
  > **username_3**: I have the same problem. Where can [this issue](https://github.com/civicrm/org.civicrm.flexmailer/issues/23) be reported now?  
  > **username_1**: @username_3 do you you that issue on a current version of civicrm? In this case, you should file a new issue in gitlab: https://lab.civicrm.org/groups/dev/-/issues  (without diving deeper into it, I believe the underlying problem was solved some time ago... but if you still see that issue, you should report it again!)  
  > **username_3**: Thanks @DetlevSieber, I opened [this issue](https://lab.civicrm.org/dev/core/-/issues/5586).  
  
  ---
  
  