Answers.Body: <p>I might have the same problem, I'm not sure. I've got a client recently updated to php8.1 and civicrm 5.67.1. Their bounce processing (which has been running for many years), now seems to be ignoring everything.</p>
  <p>Specifically, the bounce mail is arriving into their mailbox (i.e I see it in the new folder) and the the bounce job runs and it all gets put into the .INBOX.CiviMail.ignored/cur directory, and shows no bounces.</p>
  <p>That suggests that there's a parsing of the message that has started failing. I'm pretty sure it's not the php8.1 upgrade, since I have other clients without this symptom that are upgraded to php8.1.</p>
  <p>This might be the same issue, it has a PR against it:</p>
  <p><a href="https://lab.civicrm.org/dev/core/-/issues/4775" rel="nofollow noreferrer">https://lab.civicrm.org/dev/core/-/issues/4775</a></p>
  <p><a href="https://github.com/civicrm/civicrm-core/pull/28354" rel="nofollow noreferrer">https://github.com/civicrm/civicrm-core/pull/28354</a></p>
  <p>Update: yes, that PR resolved it. After applying the patch, I moved all the messages that were in the ignored mailbox into the new folder and reran the job and all kinds of new bounces showed up.</p>
  <pre><code>mv .INBOX.CiviMail.ignored/cur/* new/
  </code></pre>
  <p>And it's fixed in 5.67.3</p>
  <p>Update:</p>
  <p>This related issue looks to be closer to what you're experiencing: <a href="https://lab.civicrm.org/dev/core/-/issues/2801" rel="nofollow noreferrer">https://lab.civicrm.org/dev/core/-/issues/2801</a></p>
  <p>That one doesn't have a specific resolution, though it's identified as related.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-09T04:04:21.693Z
Answers.Text: I updated to 6.67.3, moved all IGNORED messages to INBOX, ran fetch_bounces, but received the same error:
  Parameters raw (from db settings): 
  is_create_activities=0
  Parameters parsed (and passed to API method): 
  a:0:{}
  Full message: 
  Finished execution of Fetch Bounces with result: Failure, Error message: Unknown api version
  
  Is it fixed in 5.68??
Answers.UserDisplayName: Hilary Binder
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-11T16:19:05.710Z
Answers.Text: I think your issue stems from the same time/code, but might be different. Take a look at this issue instead and see if it's relevant: https://lab.civicrm.org/dev/core/-/issues/2801
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-11T16:24:19.193Z
Answers.Text: Alternatively, maybe it's just a cache clearing issue? It certainly seems to be an odd symptom, i.e. the 'api version' error.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-11T20:25:59.743Z
Answers.Text: Thanks for your suggestions, @alandixon, but the issue 2801 was not relevant. Since Bounces aren't being fetched, they aren't being recorded at all, not even incorrectly. I varnished the cache on the server as well as within Civi and the CMS, but still the same error. Any other ideas???
Answers.UserDisplayName: Hilary Binder
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-12T19:52:31.293Z
Answers.Text: I'm going to guess that the "unknown api version" applies to some api call generated as a side effect of the is_create_activities=0 parameter. Can you test this hypothesis? If you call the job without that parameter and it works, at least you've narrowed down the issue ... e.g. maybe you have some extension related to activities that isn't compatible the new version of civi.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-13T11:55:13.993Z
Answers.Text: the fetch_bounce job works without is_create_activities=0 parameter and with is_create_activities=1 parameter. how will is_create_activities=1 parameter affect contacts? i read there might be a problem: https://lab.civicrm.org/dev/core/-/issues/2800
Answers.UserDisplayName: Hilary Binder
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-13T23:02:07.900Z
Answers.Text: Ah, excellent! I have not experienced issue 2800, it looks like it might be specific to the use of VERP, and in any case, might be fixed, and is at worst an annoyance.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-14T08:31:32.130Z
Answers.Text: Thanks for all your help @alandixon! I will mark this as "answered," but if I run into problems, I will post again.
Answers.UserDisplayName: Hilary Binder
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-12-08T19:07:32.503Z
Answers.LastActivityDate: 2023-12-11T16:22:53.177Z
Answers.LastEditDate: 2023-12-11T16:22:53.177Z
Answers.UserDisplayName: Alan Dixon
Body: <p>For some reason, the fetch bounce api method is unrecognized (Fetch Bounces     Finished execution of Fetch Bounces with result: Failure, Error message: Unknown api version).</p>
  <p>not sure if related to recent php upgrade (8.1) or last Civicrm upgrade (5.66.2). Last functioning fetch bounces (October 27) returned api method as Parameters parsed (and passed to API method):
  a:2:{s:7:&quot;version&quot;;i:3;s:20:&quot;is_create_activities&quot;;s:1:&quot;0&quot;;}</p>
  <p>Current failure log message:
  Fetch Bounces
  Entity: Job Action: fetch_bounces<br />
  Summary: Starting execution of Fetch Bounces
  Details:
  Parameters raw (from db settings): is_create_activities=0
  Parameters parsed (and passed to API method): a:0:{}</p>
  <p>Full message:
  Starting execution of Fetch Bounces</p>
  <p>Any help appreciated!</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2023-11-28T14:55:38.893Z
Comments.Text: I have the same problem ? Any solutions?
Comments.UserDisplayName: barbaraec
Tags: <api><failure><bounce-processing>
Title: Fetch Bounces Failure, Error message: Unknown api version
ThreadText: # Fetch Bounces Failure, Error message: Unknown api version
  
  (Asked by: username_0 on 2023-11-09)
  
  For some reason, the fetch bounce api method is unrecognized (Fetch Bounces Finished execution of Fetch Bounces with result: Failure, Error message: Unknown api version).
  
  not sure if related to recent php upgrade (8.1) or last Civicrm upgrade (5.66.2). Last functioning fetch bounces (October 27) returned api method as Parameters parsed (and passed to API method):
  a:2:{s:7:"version";i:3;s:20:"is\_create\_activities";s:1:"0";}
  
  Current failure log message:
  Fetch Bounces
  Entity: Job Action: fetch\_bounces  
  Summary: Starting execution of Fetch Bounces
  Details:
  Parameters raw (from db settings): is\_create\_activities=0
  Parameters parsed (and passed to API method): a:0:{}
  
  Full message:
  Starting execution of Fetch Bounces
  
  Any help appreciated!
  
  **Tags:** api, failure, bounce-processing
  
  > **Comments:**
  > **username_1**: I have the same problem ? Any solutions?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2023-12-08. Score: 2 | Accepted answer
  
  I might have the same problem, I'm not sure. I've got a client recently updated to php8.1 and civicrm 5.67.1. Their bounce processing (which has been running for many years), now seems to be ignoring everything.
  
  Specifically, the bounce mail is arriving into their mailbox (i.e I see it in the new folder) and the the bounce job runs and it all gets put into the .INBOX.CiviMail.ignored/cur directory, and shows no bounces.
  
  That suggests that there's a parsing of the message that has started failing. I'm pretty sure it's not the php8.1 upgrade, since I have other clients without this symptom that are upgraded to php8.1.
  
  This might be the same issue, it has a PR against it:
  
  <https://lab.civicrm.org/dev/core/-/issues/4775>
  
  <https://github.com/civicrm/civicrm-core/pull/28354>
  
  Update: yes, that PR resolved it. After applying the patch, I moved all the messages that were in the ignored mailbox into the new folder and reran the job and all kinds of new bounces showed up.
  
  ```
  mv .INBOX.CiviMail.ignored/cur/* new/
  
  ```
  
  And it's fixed in 5.67.3
  
  Update:
  
  This related issue looks to be closer to what you're experiencing: <https://lab.civicrm.org/dev/core/-/issues/2801>
  
  That one doesn't have a specific resolution, though it's identified as related.
  
  > **Comments:**
  > **username_0**: I updated to 6.67.3, moved all IGNORED messages to INBOX, ran fetch_bounces, but received the same error: Parameters raw (from db settings):  is_create_activities=0 Parameters parsed (and passed to API method):  a:0:{} Full message:  Finished execution of Fetch Bounces with result: Failure, Error message: Unknown api version  Is it fixed in 5.68??  
  > **username_2**: I think your issue stems from the same time/code, but might be different. Take a look at this issue instead and see if it's relevant: https://lab.civicrm.org/dev/core/-/issues/2801  
  > **username_2**: Alternatively, maybe it's just a cache clearing issue? It certainly seems to be an odd symptom, i.e. the 'api version' error.  
  > **username_0**: Thanks for your suggestions, @username_2, but the issue 2801 was not relevant. Since Bounces aren't being fetched, they aren't being recorded at all, not even incorrectly. I varnished the cache on the server as well as within Civi and the CMS, but still the same error. Any other ideas???  
  > **username_2**: I'm going to guess that the "unknown api version" applies to some api call generated as a side effect of the is_create_activities=0 parameter. Can you test this hypothesis? If you call the job without that parameter and it works, at least you've narrowed down the issue ... e.g. maybe you have some extension related to activities that isn't compatible the new version of civi.  
  > **username_0**: the fetch_bounce job works without is_create_activities=0 parameter and with is_create_activities=1 parameter. how will is_create_activities=1 parameter affect contacts? i read there might be a problem: https://lab.civicrm.org/dev/core/-/issues/2800  
  > **username_2**: Ah, excellent! I have not experienced issue 2800, it looks like it might be specific to the use of VERP, and in any case, might be fixed, and is at worst an annoyance.  
  > **username_0**: Thanks for all your help @username_2! I will mark this as "answered," but if I run into problems, I will post again.  
  
  ---
  
  