Compatibility Issues Found with Amazon SES/SNS and Stripe Subscription Extension

[n.business]

Hi, this is a nice messaging application, but I wanted to report a few compatibility issues we encountered while setting up and testing the latest MailWizz release 3.0.4:

1. Amazon SES Web API
The SES Web API integration had an issue when using an SES domain identity. The API was attempting to handle feedback forwarding using the full FROM email address rather than the verified domain identity.

2. Amazon SNS Webhook
The AWS SNS webhook endpoint was being blocked by MailWizz's CSRF validation. The configured `dswh/*` route was correct, but the CSRF handler was not being detached correctly, preventing SNS POST notifications from being processed.

3. Stripe Subscription Gateway Extension
The Stripe subscription webhook extension appears to rely on older Stripe Invoice fields. With the current Stripe API payload, `invoice.subscription` and `invoice.paid` were no longer available in the expected locations. As a result, successful Stripe payments were received and returned HTTP 200, but the corresponding MailWizz orders remained `incomplete`.

4. Users are unable to see their subscription duration.

5. When user deletes payment from My Account -> subscription. The user quota is set to unlimited everything.

 

[n.business]

Number 5 has been figured out, you have to create "No payment" group for users.

 

[twisted1919]

1. Amazon SES Web API
The SES Web API integration had an issue when using an SES domain identity. The API was attempting to handle feedback forwarding using the full FROM email address rather than the verified domain identity.

This is how it suppose to work, it looks for email rather than domain, that's how it always worked.

2. Amazon SNS Webhook
The AWS SNS webhook endpoint was being blocked by MailWizz's CSRF validation. The configured `dswh/*` route was correct, but the CSRF handler was not being detached correctly, preventing SNS POST notifications from being processed.

This has been corrected, we'll do a release today to address it.

3. Stripe Subscription Gateway Extension
The Stripe subscription webhook extension appears to rely on older Stripe Invoice fields. With the current Stripe API payload, `invoice.subscription` and `invoice.paid` were no longer available in the expected locations. As a result, successful Stripe payments were received and returned HTTP 200, but the corresponding MailWizz orders remained `incomplete`.

We'll try to address this asap and contact you with the new extension so you can check it.

4. Users are unable to see their subscription duration.

We'll look into his as well.

Thank you for reporting!

 

[n.business]

Thank you for your swift response @twisted1919

Also look into domain verification for users. When sending server's Force FROM email is set to "when no valid domain", the admin's email is still shows when emails are delivered even when user as validated their domain.