This is one of the themes that work with this module.

ThemeMetro (Latest Version) Click Here
Impressive Themes (Latest Version) Click Here
SwiftModders (Latest Version) Click Here
ThemeLooks (Latest Version) Click Here
RS Studio (Latest Version) Click Here
AA Layer (Latest Version) Click Here
Lara, WHMCS Admin (Latest Version) Click Here

Other Themes are not fully tested yet, so I am not sure if it work or not. You can contact me first.Click Here

To get an Amazon Web Services (AWS) credentials key (an Access Key ID and Secret Access Key), you must generate them within the AWS Identity and Access Management (IAM) console, as the secret key is only revealed once upon creation.

1. Why don't they show Password Reset Validation in the module?
ANS: Password Reset Validation is not logging in WHMCS You can see this by going to the client summary and clicking on emails

This on the themes that work with this module.

Zomex (Latest Version) Click Here
ThemeMetro (Latest Version) Click Here
Impressive Themes (Latest Version) Click Here
SwiftModders (Latest Version) Click Here
ThemeLooks (Latest Version) Click Here
RS Studio (Latest Version) Click Here
AA Layer (Latest Version) Click Here
Lara, WHMCS Admin (Latest Version) Click Here

Other Themes have not been fully tested yet, so I am not sure if it work or not. You can contact me first. Click Here

This on the Themes that don't work with this module.

SwiftModders (Latest Version) Click Here
Lara, WHMCS Admin (Latest Version) Click Here

Other Themes are not fully tested yet, so I am not sure if they work or not. You can contact me first. Click Here

We would like to thank our members, whose efforts over the years have made this translation what it is.

German: Alfred Pogner

This on the themes that work with this module.

SwiftModders (Latest Version) Click Here
Lara, WHMCS Admin (Latest Version) Click Here

Other Themes are not fully tested yet, so I am not sure if they work or not. You can contact me first. Click Here

Here is a list of error code

Click Here

By MailerSend.com:

I would like to share an important update about our API.

From March 23rd, 2022, at 12:00 UTC, we’ll be introducing a new daily quota to our API for all MailerSend accounts and an API Usage Policy as well.

This means there will be a maximum number of requests a single account can make within a 24-hour period. If you exceed the daily quota, the API or SMTP request will fail and return an HTTP 429 status code (but don’t worry—this can be easily avoided! See below).

The daily quota will:

• Be applied at the account level. All API tokens and SMTP credentials of your account share the same quota
  

• Be based on your account plan. Premium and Enterprise plans have a higher daily quota than Free plan holders
  

• Count all API requests (valid or failed) and SMTP requests (authenticated only). We count an SMTP call when an SMTP client sends valid credentials and the DATA portion is sent through
  

• Be refreshed at midnight UTC
  

• Send your emails using the Bulk Email endpoint: you can send up to 35,000 in a single request
  

• Use webhooks instead of polling for changes
  

• Cache responses wherever possible instead of frequently making the same request
  

• If you’re sending marketing content, consider using a dedicated marketing emailing tool like MailerLite and using MailerSend for all transactional messaging.