I believe a good feature to add to the platform is to integrate any email that is sent through mailjet into gmail, that way I will be able to see the emails that have been sent in my gmail 'sent' tab.

create reports that can be emailed daily, especially reports that show emails that did not get delivered, with the reason why, bad address, blocked, etc. I know this information is available on the website, but it would be nice if this information could be setup in to be emailed to different recipients.

Some servers start to take reputation away from emails signed with 1024-bit DKIM keys.It would be nice to extend the functionality and allow 2048 bit DKIM keys

Add de-block button on blocked email addresses

Add custom SMTP Relay with TLS & Authentication for specific recipients.

Need: Keep the same connection between our app and Mailjet, but be able to set custom delivery options for a set of recipients (based on domain names). Needed by some corporate clients of ours which have private SMTP relays to whitelist automated emails.

I would like to sign my messages that I send with an S/MIME Key that you hold for me.

Currently, if a recipient sends a hardbounce, all Mailjet senders are blocked, including those with a dedicated IP. It would be interesting to block only those belonging to shared pools (to avoid a drop in the overall score) and let the dedicated IPs make a reputation for themselves.

I want to define a soft bounce management within the UI. This should give the ability to define how the system should handled a message that is soft bouncing several times.

Example:
If an email adresse does soft bounce five times i want it to be blocked.

For testing puporses -especially with SMTP- it would be helpful to have a setting per subaccount where we can activate "Sandbox Mode".
As long as the sandbox mode is active all triggered email -regardless via API or SMTP- should not be delivered via Mailjet, but it should stored and rendered via a Sandbox Overview Page in the Dashboard area.

Mailjet is already encrypting emails using TLS but it using opportunistic TLS, which defaults to TLS but fallbacks to plaint text in case the recipient's server doesn’t support TLS.

We want to enforce TLS (for specific emails) so that in case the recipient doesn’t support TLS, the message is not sent at all.

It would be really helpful to see the sender reputation statistics .e.g. reputation score in the statistics area

There are several Events (Webhooks) that are notifying remote URLs about changes. Yet there is one missing: When someone subscribes. Please add this and fix this bug.
Related discussion: https://github.com/mailjet/api-documentation/issues/17

Creating Web Version of e-mail created with SAPI from a 3P - Integration ( CrossEngage ) with the vars given in the call.

It should be possible to match the eventy object in the response to an APIKey or at least to the from sender id.
Both properties are not delivered as properties of the event object.

By now, one can only add a single URL per Event. Some events might need to get sent to multiple services. Please add more than one URL and event.

Ability to update DKIM of a sending domain on a regular basis, such as every 6 or 12 months.

Only the API Key is rendered in the emails which are sent in case an unverified domain was used in one of the accounts.
Especially in complex companies where many subaccounts are existing, it is hard to go to the "Master API Key and Sub API Key Management" area and search for the API key to understand which account uses the unverified domain.
Therefore it would be helpful to render not only the Api Key but also the display name / label of the API Key in the information emails.