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

AWS SNS Bounce and complaints not processed #1869

Closed
benstaf opened this issue May 23, 2024 · 7 comments
Closed

AWS SNS Bounce and complaints not processed #1869

benstaf opened this issue May 23, 2024 · 7 comments
Labels
needs-investigation Potential bug. Needs investigation

Comments

@benstaf
Copy link

benstaf commented May 23, 2024

Version:

  • listmonk: Repocloud
  • OS: [e.g. Fedora]

Description of the bug and steps to reproduce:

I tried to set up Bounce Processing following the documentation:
https://listmonk.app/docs/bounces/

The AWS SNS subscription is confirmed, but bounces and complaints are not counted by Listmonk

Screenshots:
If applicable, add screenshots to help explain your problem.
Screenshot_2024-05-23-23-54-31-493_com android chrome-edit

@MaximilianKohler
Copy link
Contributor

Anything in your logs? It's working for me with these instructions: https://listmonk.app/docs/bounces/#amazon-simple-email-service-ses

@benstaf
Copy link
Author

benstaf commented May 25, 2024

yes, when I configured SNS I got this log:

2024/05/22 15:39:10 error processing SES notification: notification type is not bounce
2024/05/22 15:39:10 error processing SES notification: notification type is not bounce

@MaximilianKohler
Copy link
Contributor

Repocloud may have an old version of listmonk?

@benstaf
Copy link
Author

benstaf commented May 25, 2024

It's v3.0.0

Screenshot_2024-05-25-17-20-10-066_com android chrome

@MaximilianKohler
Copy link
Contributor

Well, I don't know if it matters for this issue, but that "public URL" is not supposed to be localhost:9000. It should be the first part of the one you put in your Endpoint.

@benstaf
Copy link
Author

benstaf commented May 26, 2024

I did it and nothing changed. It's actually the same issue as #1807

@knadh knadh added the needs-investigation Potential bug. Needs investigation label May 28, 2024
@benstaf
Copy link
Author

benstaf commented May 29, 2024

Problem solved here:

#1668 (comment)

@benstaf benstaf closed this as completed May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-investigation Potential bug. Needs investigation
Projects
None yet
Development

No branches or pull requests

3 participants