sendgrid-csharp: Cannot send internationalized email address / non ASCII characters

Issue Summary

I cannot send an email to an address with non ASCII characters.

Example email: pepé@lefrenchplace.com

Gmail web interface works fine to send so the test email address is set up fine.

Using SendGrid, Non ASCII characters work fine in subject line and message body.

Relevant standard: RFC6530, RFC6531, RFC6532

Steps to Reproduce

SMTP throws an SMTPException with the message The client or server is only configured for E-mail addresses with ASCII local-parts: pepé@lefrenchplace.com

var smtp = new SmtpClient(Server)
{
    Credentials = new NetworkCredential(Username, ApiKey),
    DeliveryFormat = SmtpDeliveryFormat.International
};

var message = new MailMessage(From, To)
{
    Subject = Subjet,
    Body = BodyPlainText
};

smtp.Send(message);

Using the V3 API example I get an Accepted status code returned. On the SendGrid dashboard it shows as Dropped with Invalid as the reason.

Technical details:

  • sendgrid-csharp Version: 9.9.0
  • Platform WebForms
  • .NET Version: 4.6.1

About this issue

  • Original URL
  • State: closed
  • Created 9 years ago
  • Reactions: 38
  • Comments: 42 (9 by maintainers)

Most upvoted comments

Hi @thinkingserious, thanks for your update. No offense, but sendgrid is kind of in the business of sending emails, right? Would be great if actual email addresses were supported. Couldn’t find the feedback link, btw. Best, Florian

Closing as this is not something that can be fixed in this library.

Support and back-end product teams use support tickets to track customer impact and do not rely on nor check GitHub. Recommend anyone experiencing this issue contact support in order to help drive the issue.

Hi!

We’ve also run into this problem. Some of our users have names with non ascii characters in them and they can’t use their email addresses. I don’t mean to be rude but it is kind of weird to have an email service that can’t deliver emails to valid email addresses.

C’mon, guys. You deliver email. It’s all you do. You’ve got one job. You have to be good at it. You have to do it right. Do it.

In January, 2017, Len Schneyder, VP of Industry Relations at Sendgrid, had this to say:

“I’m really excited about this thing called SMTPUTF8 and it really, right now, affects a miniscule portion of the marketplace. But ideologically, it’s the democratization of, or the further localization of, email…It will make email more accessible to more people, in more places.”

“We’re kind of trying to track and see how many, if any, of those UTF8 addresses are winding up flowing through our networks”

It’s June 2021, and Sendgrid still doesn’t support SMTPUTF8. And they won’t see any such addresses flowing through their networks, since they actively reject them.

I think it’s fair to say that they’re not working on this at all. We’re sending several billion emails through Sendgrid each year and have brought up the issue many times. Nothing happens. We’re actively pursuing a switch now.

Will this issue ever get solved? There is a surprising amount of people with these kinds of chars in their email addresses

@lawhi The best approach for us was to just switch to AWS SES.

After contacting SendGrid they have effectively said that they will not fix this issue, we have to remove the Unicode characters ourselves. We have implemented the answer from this Stack Overflow question and it covers most cases. Hopefully this is useful for anyone else finding this ticket.

https://stackoverflow.com/questions/249087/how-do-i-remove-diacritics-accents-from-a-string-in-net

We recently started to use SendGrid because someone recommended SG as a reliable provider. It’s now been almost four full years, since this issue was raised in this thread, for something so simple to fix and has such an inpact. With something so simple, taking so fricking long to fix, how long will more complex issues take?

Any possibility that this will be fixed at all, or do we have to look for a company that actually cares about doing the one job they claim to do - send emails?

@JWilliams-CINC removing/replacing characters results in a different email address. A different email address that possibly doesn’t exist or if it does, is owned by another person.

Hello @ftamin,

Could you please add your voice via this link. Thank you!

Can we please get a deadline on when this pretty serious shortcoming will be fixed?

@toul The last thing my product person was able to get from our SendGrid contacts was that they refused to address the issue.

I got an answer from SendGrid Tier 2 support on June 17, 2020, unfortunately it is not very helpful.

Please note that we do not currently support non-ASCII characters in email addresses, for which I apologize as I can absolutely understand it is a big pain point.

SendGrid’s allowed character set is US-ASCII.

Please note that encoding is not a good solution for this issue, our sincere apologies for any confusion or frustration. Our teams are aware of the customer demand for this enhancement and are working on plans to include the ability. Unfortunately, we’re unable to provide an estimated time of rollout for this, but the definitive answer is that yes: SendGrid is committed to addressing this issue.

Latest reply from SendGrid support

I understand you are having issues when sending to recipient addresses with non-ASCII characters. Unfortunately, currently we do not support email addresses with non-ASCII characters. This is a hard limitation on our end.

Wow. Emailadresses with non-ASCII are valid email addresses and they are actually being used by the users of our software. I cannot sell to our customers that they cannot mail out.

@thinkingserious This issue was brought up almost 2 years ago for the first time and it touches the core of what you guys do for us: Send email in a reliable way.

Can we please get a deadline on when this pretty serious shortcoming will be fixed?

@tuol, @gliljas,

Thank you for the additional context!

The issue has been closed as it does not relate to this helper library. That said, we will circle back and update this thread as new information is uncovered. Thank you!

Hello @ftamin,

Could you please add your voice via this link. Thank you!

I would appreciate to follow this whole discussion in the open and don’t understand why this issue was closed in the first place.

None of my contact attempts with the help desk felt like they were useful. This concerns a crucial shortcoming to your service that hasn’t been resolved.

Like @ftamin wrote; It’s been 3 years. What are you going to do?

it’s been 3 years, any update/progress/release plan for this issue?

Thanks for taking the time to report this @leogiertz!

Please take a moment to use the feedback link at sendgrid.com to help bring more attention to the issue.