Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unknown bounce category 'Ignore' #38

Open
bugfolder opened this issue Nov 27, 2023 · 1 comment
Open

Unknown bounce category 'Ignore' #38

bugfolder opened this issue Nov 27, 2023 · 1 comment

Comments

@bugfolder
Copy link
Contributor

I am getting bounces with an unknown bounce category. The error message in my log (coming from the CiviCRM AirMail extension) is (with some trimming):

Unrecognised Elastic Email webhook event received: Received undocumented category 'Ignore' Event data: {"reset":"1","secretcode":"***","transaction":"***","to":"***","from":"***","date":"***","status":"Error","channel":"SMTP API","account":"***","category":"Ignore","postback":"***","subject":"***","messageid":"***","q":"civicrm/airmail/webhook"}

So the bounce category is 'Ignore'. But this isn't a listed category on https://elasticemail.com/developers/api-documentation/web-api-v2#classes_BouncedCategorySummary

I see in Elastic.php that it is in the $mapElasticCategoryToCiviBounceType array as

      'Ignore'                => NULL, // ? huh? Exists in documentation without definition

I've queried ElasticEmail via their support chat as to what the definition of this category should be.

@bugfolder
Copy link
Contributor Author

After some back-and-forth with ElasticEmail about the undocumented 'Ignore' category, here's what they said:

Thanks for the message ID, if we check the bounce message it shows: The server response was: 452-4.2.2 The recipient's inbox is out of storage space.
So their inbox is simply over quota.

I asked about the missing documentation of the 'Ignore' category, and they said:

as Antoinette mentioned regarding the reasons for bouncing - these are usually explained on our dashboard. As per the documentation update, the APIv2 documentation is no longer developed as it has been replaced by our Rest API v4. Of course - v2 doesn't lose its functionalities, but our Tech Team no longer focus on improving it.

So I guess they will leave it undocumented.

However, I went and checked 5 of the bouncebacks that returned that category, and they were all over-quota errors. So perhaps it would be better to treat such bouncebacks as a CiviCRM "over quota" type (type = 8), rather than as NULL.

Would you agree? If so, I can submit a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant