-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
MessageBounced Webhook not sent #2500
Comments
I have the same problem. Other type of webhooks are sent perfectly, but bounced ones not. |
The code still seems present so I'm not sure what the problem could be. postal/lib/postal/message_db/message.rb Lines 439 to 442 in 2f62baa
postal/app/jobs/unqueue_message_job.rb Lines 90 to 98 in 2f62baa
If you're able to trigger a bounce yourself, you could try watching the logs for the workers and see if they log anything relevant but that might be challenging depending on how busy they are. |
I was able to solve the problem by adding below to config/application.rb file seeing from one of the pull request. https://github.com/postalserver/postal/pull/2477/files config.active_record.yaml_column_permitted_classes = [Symbol, Hash, Array, ActiveSupport::HashWithIndifferentAccess] Then I was able to get Bounce Webhooks. |
It works ! Thank you so much. |
This issue is still persisting and #2477 indeed fixes that. |
Apologies for this. I am also encountering this issue. Is anyone able to write an idiots guide (for me, an idiot) on how to patch this directly? Assume I know barely anything about Docker and even less about Ruby. Particularly @vkperumal as it sounds like you may have done this before :) Much appreciated. |
Describe the bug
Even though the message is categorized as bounce, webhook is not getting triggered
SPF, DKIM and Return path have been configured
Postal Version: 2.1.4
Expected behaviour
Webhook should be triggered
Screenshots
Bounce Webhook Configuration
Webhook History
The text was updated successfully, but these errors were encountered: