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

bounce.go:170: error processing SES notification: notification type is not bounce #1807

Open
robguthrie opened this issue Apr 3, 2024 · 6 comments

Comments

@robguthrie
Copy link

Version:

  • listmonk: [eg: v3.0.0]
  • OS: [e.g. Ubuntu / Docker]

Description of the bug and steps to reproduce:
I've setup SNS notification topic as described in #1668 (comment) but I'm not getting bounce notifications, in the logs I can see this error:

bounce.go:170: error processing SES notification: notification type is not bounce

I've tripple checked my settings and it seems correct.

@knadh
Copy link
Owner

knadh commented Apr 3, 2024

SES sends many types of notifications. Perhaps you've enabled non-bounce notifications. I'm not familiar with SES config though.

@robguthrie
Copy link
Author

Sorry, I should have added these are logs in response to me using the bounce@simulator.amazonses.com address to test. There are no other logs happening during this time, and the count of logs corresponds to my tests sent.
The SNS topic confirmation request works correctly though.

Is there a way to enable more log output so I can see the body of the request?

@knadh
Copy link
Owner

knadh commented Apr 3, 2024

There are no verbose payload logs. It should be fine to ignore those errors as non-bounce (bounce/complaint) notifications are discarded with that particular message. The simulator must be sending non bounce/complaint notifications.

@MaximilianKohler
Copy link
Contributor

I wouldn't say this is fine and to ignore it. I haven't tested v3.0, but earlier versions had this issue before being fixed. I'm on v2.5.1 with that exact setup and everything works normally.

If you're only emailing bounce@simulator.amazonses.com, then there's clearly something wrong. The SES simulator does not send non-bounce/complaint notifications.

Since there are no verbose logs, you may want/have to try v2.5.1 to test, and if you're still getting the error then you've misconfigured something. If it works properly then it's a bug with v3.0.

Make sure that in this part of the instructions the 3rd option (1 bounce, 2 complaint, 3) is left blank:

In the AWS console, go to Simple Email Service and click "Verified identities" in the left sidebar.
Click your verified domain and go to the "Notifications" tab.
Next to "Feedback notifications", click "Edit".
For "Bounce feedback" and "Complaint feedback", select the SNS topic you created earlier.

@robguthrie
Copy link
Author

Thanks, I've verified with a webhook tester that the SNS notifications are correct.

Is it safe to rollback from v3 to v2.5.1 without changing the database?

@MaximilianKohler
Copy link
Contributor

MaximilianKohler commented Apr 4, 2024

Is it safe to rollback from v3 to v2.5.1 without changing the database?

According to the docs it is not safe. I'd recommend cloning your server temporarily to test it.

EDIT: you don't even need to clone it actually, just temporarily create a new server and install v2.5.1 to test.

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

3 participants