Outgoing email should be deliverable over IPv4 and IPv6.

Need the ability to rate limit the number of emails sent in an hours time, if a list/campaign is 12,000 contacts have a function that says deliver 5,000 emails per hour until finished. This will also help with keeping from being rate limited by recipient systems like Microsoft and Google and being put into a queue to retry or soft bounced.

We've noticed that reports of spam are counted at the time of the report, not the time the email was sent. So if a recipient received multiple emails over the course of a month and then decided later to mark them all as spam, we see an immediate spike in the spam counts. This means that a single recipient could cause our account to be throttled. We'd like to see the time the original email was sent factored into the spam reporting so that our account is not limited based on an action that we have no way of fixing.

Add ability to customize return-path via API to avoid to do it manually (same as domain validation).

Please add automatic return-path stamping and self service for the same.

Right now there is only one custom return path pr. sub account.

We should simply be able to setup this return-path once for a domain, and have is useable by multiple sub accounts

Just like with DKIM.

You can use plus addressing to make sure bounces are stored in the right subaccount.

Since many other vendors are doing this already, I expect to see the same form mailjet as it is essential for compliance and flexibility of the platform.

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.

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.

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

permettre l'envoi de mails dont la taille serait supérieure à 15Mo et pouvant aller jusqu'à 100Mo

allow the sending of emails whose size would be greater than 15MB and up to 100MB

It would be great to see how much people of my email-list have opened their mail using Outlook or another email client.

Add de-block button on blocked email addresses

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

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.

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.

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.

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.

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

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