dandre added the comment:
Erm, sorry.
The header, of course, does not have much to do with the address the email is
to be delivered to.
With my provider's setup, the mailer will reply that =?utf-8?q?my?= is not a
known user.
Which could change, of c
dandre added the comment:
I made a test and, interestingly, I /can/ send an email to myself setting up
the header like this:
h.append(b'My Name', charset='utf-8')
h.append(b' < ', charset='us-ascii')
h.append(b'my',
dandre added the comment:
Thanks again for the clarification.
I may not look like it ;), but my fanciness has to go even further. So, for the
sake of completeness, it appears that the world is now up to UTF-8 local parts
of email addresses, and punycode for the domain?
https
dandre added the comment:
Thank you for pointing out my wrong usage of Header.
Does this mean I should call Header.append() for each token, with tokens being
separated by WS, or probably rather COMMASPACE in the case of To:? Or does it
mean I should call Header.append() for each "lo
New submission from dandre :
Hello there, first of all, thank you all for Python. I didn't know it was so
great; otherwise I'd have checked it out before.
Using 2.7.2 MSC v.1500 32 Intel bit for now.
Playing with email.header, I came across an odd behaviour.
Attached please fin
