Errors with bounce processing from forwardemail

[Skeyelab]

I am using the forwardemail service and have set my Webhook URL in their settings and my Forward Email Key in my listmonk settings. Listmonk's error log reads:

bounce.go:215: error processing forwardemail notification: invalid signature

Does anyone have any experience with this and have gotten it to work?

[MaximilianKohler]

Have you asked on their forum?

[knadh]

Perhaps @shaunwarman could help.

[titanism]

Hi there @Skeyelab - team here from @forwardemail. Curious if you can get some log output, or debug/print to figure out what the culprit is?

The code is at

listmonk/internal/bounce/webhooks/forwardemail.go

Line 59 in 0878f3e

return nil, fmt.Errorf("invalid signature")

on your instance.

I think that @shaunwarman tested this before his PR was accepted/merged for Forward Email support - but he said he'd chime in when he gets time.

[shaunwarman]

@Skeyelab there's a helpful bit here in the screenshots of a previous setup and testing: #2016 (comment)

The webhook should be sent to the 'Bounce Webhook URL' configured in the forwardemail dashboard /domains/<domain_name>/advanced-settings. This is just above the 'Webhook Signature Payload Verification Key' you have configured in listmonk.

I would also check the My Account -> Emails view in your forwardemail dashboard for some logs as well.

Let me get this set back up and see if I can reproduce the invalid signature.

[Skeyelab]

@shaunwarman I am fairly certain that I have everything configured correctly. ForwardEmail is hitting my webhook, generating the error.

@titanism - as far as adding logging goes, I am using the listmonk/listmonk:latest docker image and when I connect to a terminal, I only see what appears to be an executable file. It does not seem I am able the source... unless I am mistaken

[titanism]

@Skeyelab just to confirm, you're using the "Webhook Signature Payload Verification Key" from My Account > Domains > Settings, and not your API key, correct?

[Skeyelab]

Correct. Thanks

[titanism]

Note you can test with hard reject 550 via [email protected] on your list and soft reject 421 via [email protected]. We created those aliases for test/debug purposes.

[shaunwarman]

Hey @Skeyelab @knadh - my apologies, but I see some issues that are fixed here: #2250

I've validated on a personal VM and see it working end to end.

[titanism]

Awesome stuff @shaunwarman !!!! 🚀

Once it's merged & released all you need to do is upgrade your ListMonk version @Skeyelab

[knadh]

This is merged. Thanks @shaunwarman.

[Skeyelab]

Thanks for the help. When can I expect this to be released?

[titanism]

@knadh the last release was v4.1.0 - can 4.1.1 be released or 4.2.0?

[knadh]

@titanism the next version is v5.0.0 with a major overhaul in the e-mail editor + other small fixes in the next couple of months. No interim releases are planned.