Answers.Body: <p>I think it would be great to have more active updates for the bounce patterns based on real current bounces.</p>
  <p>I believe the bounce pattern only finds regex matches in the <a href="https://github.com/civicrm/civicrm-core/blob/master/CRM/Utils/Mail/EmailProcessor.php#L143" rel="nofollow noreferrer">body of the email.</a> It is indeed pretty simple.</p>
  <p>If you want to propose some changes or additions, the issue queue would be the place to do that.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-10-17T11:39:49.270Z
Answers.Text: Great. One thing I've noticed is that if a bounce message comes in that does not match any pattern, then civimail moves it to "processed" state but it doesn't do anything else, so it is basically ignored, silently. So there is no default action, even though the bounce means something is wrong. That seems less than ideal.
Answers.UserDisplayName: twowheeler
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-10-17T15:16:42.693Z
Answers.Text: That doesn't seem right. Probably a good idea to open an issue and post some examples of bounces that you are receiving that aren't getting matched at all.
Answers.UserDisplayName: Lars SG
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-10-16T04:16:28.117Z
Answers.LastActivityDate: 2023-10-16T04:16:28.117Z
Answers.UserDisplayName: Lars SG
Body: <p>I am thinking it would be useful to refine or add to the bounce patterns that are stored in civicrm_mailing_bounce_pattern to more accurately capture bounce situations. It looks like the &quot;pattern&quot; field is just a literal string (including options separated by | chars) that the system would grep for through incoming messages. I not sure if the subject line is searched or just the body. But is there any downside to going down that road? It looks simple enough but the inner workings of bounce processing are a bit mysterious.</p>
  <p>Edit: and it seems like this is a subject where the community could share ideas to contribute back to the devs, since very likely we all get the same bounce messages.</p>
  
Tags: <civimail><bounce><bounce-processing>
Title: Can civicrm_mailing_bounce_pattern patterns be edited or supplemented?
ThreadText: # Can civicrm_mailing_bounce_pattern patterns be edited or supplemented?
  
  (Asked by: username_0 on 2023-10-15)
  
  I am thinking it would be useful to refine or add to the bounce patterns that are stored in civicrm\_mailing\_bounce\_pattern to more accurately capture bounce situations. It looks like the "pattern" field is just a literal string (including options separated by | chars) that the system would grep for through incoming messages. I not sure if the subject line is searched or just the body. But is there any downside to going down that road? It looks simple enough but the inner workings of bounce processing are a bit mysterious.
  
  Edit: and it seems like this is a subject where the community could share ideas to contribute back to the devs, since very likely we all get the same bounce messages.
  
  **Tags:** civimail, bounce, bounce-processing
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2023-10-16. Score: 0 | Accepted answer
  
  I think it would be great to have more active updates for the bounce patterns based on real current bounces.
  
  I believe the bounce pattern only finds regex matches in the [body of the email.](https://github.com/civicrm/civicrm-core/blob/master/CRM/Utils/Mail/EmailProcessor.php#L143) It is indeed pretty simple.
  
  If you want to propose some changes or additions, the issue queue would be the place to do that.
  
  > **Comments:**
  > **username_0**: Great. One thing I've noticed is that if a bounce message comes in that does not match any pattern, then civimail moves it to "processed" state but it doesn't do anything else, so it is basically ignored, silently. So there is no default action, even though the bounce means something is wrong. That seems less than ideal.  
  > **username_1**: That doesn't seem right. Probably a good idea to open an issue and post some examples of bounces that you are receiving that aren't getting matched at all.  
  
  ---
  
  