{"id":23505,"date":"2019-07-16T00:00:00","date_gmt":"2019-07-16T00:00:00","guid":{"rendered":"https:\/\/www.mailgun.com\/blog\/aprender-un-nuevo-idioma-mailgun-tambien\/"},"modified":"2026-09-16T09:56:11","modified_gmt":"2026-09-16T09:56:11","slug":"aprender-un-nuevo-idioma-mailgun-tambien","status":"publish","type":"blog","link":"https:\/\/www.mailgun.com\/es\/blog\/product\/aprender-un-nuevo-idioma-mailgun-tambien\/","title":{"rendered":"\u00bfTe interesa aprender un nuevo idioma? \u00a1A Mailgun tambi\u00e9n!"},"content":{"rendered":"\n

Despite rapid changes in how users communicate with one another, email has remained the most ubiquitous form of communication on the Internet. Other channels like instant messaging have grown in popularity and usage but ultimately serve to supplement email rather than replace it. This is due to the open standards and extensibility of the SMTP protocol that has allowed for continual advancement while still maintaining backwards compatibility.<\/p>\n\n

SMTP, the protocol that allows messages to be exchanged from one system to another, was created during a time where ASCII was the prevailing character set. Based on the English alphabet, ASCII encodes 128 different characters into seven-bit integers, but the 128 character limitation is insufficient for many non-Latin languages. Consequently, over the years many different character sets were introduced to support different languages and symbols. These character sets often were highly fragmented so maintenance requirements varied greatly from business to business. It wasn\u2019t until the ratification of Unicode, which contains 128,237 different characters supporting 135 languages, when there was a globally adopted standard to support all languages worldwide.<\/p>\n\n

Over time, various extensions were built for SMTP that allowed the content of messages to leverage different content encodings in the message, including Unicode. Despite these extensions, however, email addresses themselves remained limited to ASCII. It was only recently that many mailbox providers around the world started adopting support for the\u00a0SMTPUTF8<\/a>\u00a0extension which finally removes this constraint and allows users to obtain internationalized email addresses.<\/p>\n\n

Over the last several months here at Mailgun, we\u2019ve seen increasing demand from customers who need to be able to communicate to users who use these internationalized addresses. As a result, we\u2019ve built out the infrastructure of the Mailgun platform to meet these customers\u2019 needs. Not only can users send messages to internationalized addresses, but we\u2019ve also added support across our entire platform including\u00a0inbound messaging<\/b>,\u00a0routes<\/b>\u00a0(match_recipient & forward),\u00a0mailing lists<\/b>(list names and members),\u00a0email address validation<\/b>, and\u00a0suppression lists<\/b>.<\/p>\n\n

To take advantage of this new feature, there is no change required. As long as the receiving mailbox provider supports the SMTPUTF8 extension, Mailgun will automatically detect support for this extension and deliver the message accordingly.<\/p>\n\n

A large portion of the work we\u2019ve done to enable internationalized email addresses is part of Flanker, our address and MIME parsing library. When we first built Mailgun, there wasn\u2019t a great Python address parsing library, so we built one and open sourced the project. We\u2019re pretty proud of it. You can check it out\u00a0here<\/a>\u00a0to learn more.<\/p>\n\n

If you have any questions or feedback on this new feature, please let us know by creating a ticket for our customer support team within your Mailgun dashboard. For anything else email-related, our email experts are always here to help.\u00a0Please don\u2019t hesitate to reach out<\/a>, and they\u2019ll be in touch soon to assist.<\/p>\n\r\n