Answers.Body: <p>The release process means it takes a while from a PR being merged until it appears in a release.  You can find details of the process <a href="https://docs.civicrm.org/dev/en/latest/core/release-process/" rel="nofollow noreferrer">here</a>.  The commit you mentioned will be in 5.35</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-02-13T12:50:14.893Z
Answers.Text: Thank you for the reply. I understand though I am still surprised this is not a huge problem for a lot people.
Answers.UserDisplayName: stijn
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-02-13T12:51:44.033Z
Answers.Text: Is there actually a way to detect in which branch a pull request or patch will get implemented?
Answers.UserDisplayName: stijn
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-02-12T09:31:48.377Z
Answers.LastActivityDate: 2021-02-12T09:31:48.377Z
Answers.UserDisplayName: Aidan
Body: <p>Some weeks ago clients reported problems of mass mailings not being delivered to a part of the destinees. After doing some research it occurred that the problem lied in contacts that had been merged.</p>
  <p>When contact A is merged in contact B, contact A gets deleted (still in the database but status 'is_deleted'). When creating a mailing both A and B seem to be added to the destinees.</p>
  <p>When sending the mailing contact A obviously doesn't receive the mailing because 'is_deleted' but contact B also doesn't get the mailing because the mail is regarded as a duplicate mail.</p>
  <p>After some looking around I found <a href="https://github.com/civicrm/civicrm-core/commit/48b1ff58" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/commit/48b1ff58</a> which solved the issue for us on multiple installs.</p>
  <p>Now I hoped this would quickly find its way into the releases, but when I just took a look at the freshly released 5.34.0 it clearly hasn't.</p>
  <p>The error is so obious though that I feel I must be missing something myself, so I hesitate to file a bug report...</p>
  
Tags: <mailing><deleted>
Title: Deleted contacts considered duplicate in mailing
ThreadText: # Deleted contacts considered duplicate in mailing
  
  (Asked by: username_0 on 2021-02-12)
  
  Some weeks ago clients reported problems of mass mailings not being delivered to a part of the destinees. After doing some research it occurred that the problem lied in contacts that had been merged.
  
  When contact A is merged in contact B, contact A gets deleted (still in the database but status 'is\_deleted'). When creating a mailing both A and B seem to be added to the destinees.
  
  When sending the mailing contact A obviously doesn't receive the mailing because 'is\_deleted' but contact B also doesn't get the mailing because the mail is regarded as a duplicate mail.
  
  After some looking around I found <https://github.com/civicrm/civicrm-core/commit/48b1ff58> which solved the issue for us on multiple installs.
  
  Now I hoped this would quickly find its way into the releases, but when I just took a look at the freshly released 5.34.0 it clearly hasn't.
  
  The error is so obious though that I feel I must be missing something myself, so I hesitate to file a bug report...
  
  **Tags:** mailing, deleted
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-02-12. Score: 1 | Accepted answer
  
  The release process means it takes a while from a PR being merged until it appears in a release. You can find details of the process [here](https://docs.civicrm.org/dev/en/latest/core/release-process/). The commit you mentioned will be in 5.35
  
  > **Comments:**
  > **username_0**: Thank you for the reply. I understand though I am still surprised this is not a huge problem for a lot people.  
  > **username_0**: Is there actually a way to detect in which branch a pull request or patch will get implemented?  
  
  ---
  
  