48 results found

1. why i can't get webhook?

   when i invoker your api send email, when i receive email i should get a webhook ,but i can't get anything,why? my webhook is ok and test is receive .

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Properly handle headers encoding when the target MTA lacks SMTPUTF8 and the client app uses UTF8 when sending to mailjet

   When enabling UTF8 support between the client app and mailjet SMTP API, the client library generally encodes SMTP headers like the Subject using UTF8 rather than quoted-printable + US-ASCII. So when using any UTF8-ready SMTP client library (in our case the SmtpClient from .NET 6), a Subject like "Caractères accentués" will be sent to mailjet as "Subject: Caractères accentués" when UTF8 is enabled (SmtpDeliveryFormat.International in .NET), and "Subject: =?UTF-8?Q?=Caract=C3=A8res_accentu=C3=A9s?=" when it is not (SmtpDeliveryFormat.SevenBit in .NET).

   This is correct behavior from the client library, but there is an issue with mailjet when the recipient MTA does not support SMTPUTF8 itself: mailjet just forwards the headers as it received them in the first place, including the Subject encoding (i.e. mailjet sends a UTF8 Subject header value to a MTA that does not support UTF8). This results in broken subject messages in the recipient's mailbox (non-ASCII characters are replaced with "???", so in this example the recipient sees "Caract???res accentu???s"). This happens with the few email providers that do not support SMTPUTF8 (iCloud, yopmail, or any MTA using Postfix < 3.0).

   One odd thing to note is that mailjet DOES reencode the Subject header using quoted-printable + US-ASCII when it contains the "[" character, meaning "[test] Caractères accentués" will be correctly displayed in thoses mailboxes whereas "Caractères accentués" will not. The correct behavior would be to reencode the Subject header if the recipient does not list SMTPUTF8 as a supported extension, instead of reencoding it using the current logic.

   Possible workarounds:
   - ignore the issue - most mailboxes support SMTPUTF8 (iCloud and some self-managed mailboxes being notable exceptions) ;
   - always include the character "[" in your email subjects (e.g. use "[xxx]" prefixes) ;
   - disable UTF8 encoding in the client app (use SmtpDeliveryFormat.SevenBit in .NET) - however this means UTF8 email addresses will not be supported ;
   - keep UTF8, but force the Subject header to be encoded using quoted-printable + US-ASCII - this might not be possible depending on the level of control your SMTP library offers (e.g. this is not possible using the SmtpClient from .NET).

   When enabling UTF8 support between the client app and mailjet SMTP API, the client library generally encodes SMTP headers like the Subject using UTF8 rather than quoted-printable + US-ASCII. So when using any UTF8-ready SMTP client library (in our case the SmtpClient from .NET 6), a Subject like "Caractères accentués" will be sent to mailjet as "Subject: Caractères accentués" when UTF8 is enabled (SmtpDeliveryFormat.International in .NET), and "Subject: =?UTF-8?Q?=Caract=C3=A8res_accentu=C3=A9s?=" when it is not (SmtpDeliveryFormat.SevenBit in .NET).

   This is correct behavior from the client library, but there is an issue with mailjet when the recipient MTA does not support SMTPUTF8 itself:… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Rust SDK

   Pourriez-vous proposer un SDK pour Rust s'il vous plaît afin d'apporter un support complet aux devs de cette technologie

   merci

   Could you please propose an SDK for Rust in order to bring a complete support to the devs of this technology

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Pouvoir modifier le lien de tracking depuis l'API - Be able to modify the tracking link from the API

   Il serait bien de pouvoir modifier le lien de tracking personnalisé depuis l'API afin de pouvoir procéder à un paramétrage complet de la plateforme depuis un accès via cette API

   It would be nice to be able to modify the custom tracking link from the API in order to be able to proceed to a complete parameterization of the platform from an access via this API

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Allow template variables in sender

   For transactional mails, we sometimes want to replace the sender name only, so instead of sending with the organization's name, we show the name of the person who has sent a message to the recipient in out application.

   Instead of sending from

   Organization noreply@organization.com

   We want to send from

   {{var:name}} via Organization noreply@organization.com

   I found out the hard way that although template variables can be used in the subject, they lead to an error when used in the sender name field. Internally, this creates a new sender address and an administrator will receive a mail that that (invalid) address should be verified.

   In order to fulfill the requirements stated above, we now have to set the sender email address and the dynamically replaced name in the app and send both the from field in the call to the Send API.

   It would be easier to do one of the following

   • Allow for variable replacement in the template configuration for the "Name" field in "Email and sender details"
   • Allow overriding the from.name in the Send API call and leaving the from.email empty.

   For transactional mails, we sometimes want to replace the sender name only, so instead of sending with the organization's name, we show the name of the person who has sent a message to the recipient in out application.

   Instead of sending from

   Organization noreply@organization.com

   We want to send from

   {{var:name}} via Organization noreply@organization.com

   I found out the hard way that although template variables can be used in the subject, they lead to an error when used in the sender name field. Internally, this creates a new sender address and an administrator will receive a mail that that (invalid) address should… more

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Reports por Subject

   Sería bueno poder contar con la posibilidad de hacer reportes de estadísticas para un determinado Subject de mail.
   Es decir, un reporte de métricas eligiendo solo los despachos a un determinado Subject. Me refiero a los despachos realizados a través de la appi

   It would be nice to be able to have the possibility to report statistics for a specific email Subject.
   That is to say, a report of metrics choosing only the dispatches to a certain Subject. I am referring to the dispatches made through the app.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. API edit settings

   Allow API bounce and spam notifications to be sent out to a specific email. Sengrid has this capability built-in to their API key.

   •  

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Individual Sender Address in Email API

   Based on a real-world ticket:

   We are using Mailjet as an SMTP relay for our domain, and the only valid sender address we have set up is our domain sender address "@mydomain.com". Now when emails are soft bounced, one could go to the Mailjet web portal and on the Stats page view which emails were not delivered and more importantly which individual sender sent the email (for example "harry@mydomain.com" taken from the email's From field). Therefore Harry could be informed that his email was not delivered.

   We have tried to automate the above process using the Mailjet API, but to do so we need to extract what was the value in the email's original From field. This is not made available anywhere in the Email API, and we also confirmed this through a ticket.

   Therefore it would be most helpful if somewhere in the message information, we could get this field, as otherwise, we have to manually download a CSV from the web portal and run a script that does the checking and sending. Having the From info in the API would allow us to completely automate this process.

   Thanks for your time and consideration.

   Based on a real-world ticket:

   We are using Mailjet as an SMTP relay for our domain, and the only valid sender address we have set up is our domain sender address "@mydomain.com". Now when emails are soft bounced, one could go to the Mailjet web portal and on the Stats page view which emails were not delivered and more importantly which individual sender sent the email (for example "harry@mydomain.com" taken from the email's From field). Therefore Harry could be informed that his email was not delivered.

   We have tried to automate the above process using the Mailjet API,… more

   0 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Email API  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close