3 ms·
Pretty light on details. By "prefix", do they mean the local part of email address? Like the "someuser" in "someuser@example.com" ? If so, it's not that unu
by tyingq 9y ago
Pretty light on details. By "prefix", do they mean the local part of email address? Like the "someuser" in "someuser@example.com" ?
If so, it's not that unusual that it wouldn't be supported. The local-part used to be constrained to ascii only. RFC6530 (SMTPUTF8) added UTF-8 support, but it's optional. Google only started supporting it in 2014, for example: https://googleblog.blogspot.com/2014/08/a-first-step-toward-more-global-email.html https://googleblog.blogspot.com/2014/08/a-first-step-toward-... Microsoft has support in some places, but not others, etc.
- colinbartlett 9y agoCorrect, there's a Github issue linked[1] that shows åliå@test.com as an example. 1. https://github.com/charlesthk/python-mailchimp/issues/116 https://github.com/charlesthk/python-mailchimp/issues/116
- Twirrim 9y agoIt looks like that has been fixed: https://github.com/charlesthk/python-mailchimp/commit/5a4ed63954aebe0e0f27a680063a8ee27d6efb66 https://github.com/charlesthk/python-mailchimp/commit/5a4ed6...
- tyingq 9y agoIt was just mentioned to confirm that it was the "local-part" that was in question. The article notes that fixing it in the python client doesn't fix the upstream lack of support on mailchimp's back end. This just seems to be a case of high expectations. Support of utf8 local-part is spotty across lots of providers and software.