rfc2047 | Encode and decode rfc2047 | Base64 library
kandi X-RAY | rfc2047 Summary
kandi X-RAY | rfc2047 Summary
Encode and decode rfc2047 (MIME encoded words).
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of rfc2047
rfc2047 Key Features
rfc2047 Examples and Code Snippets
Community Discussions
Trending Discussions on rfc2047
QUESTION
I'm trying to send an e-mail using Amazon SDK for .NET and SES. I have an e-mail which consists of special letters, for example:
ęxąmplę@źćż.com
For the domain part, i read about Punycode and that works fine. But for the local part of the address, i can't seem to find a solution: I tried using RFC 2047 encoding for whole e-mail, but then SES return 'missing final @ domain' error, so I tried to encode only a local part, so the e-mail would be
...ANSWER
Answered 2018-Jul-30 at 13:53So here is what I've found out:
The base SMTP email address specification (RFC 5322 Section 3.4) does not allow email addresses outside a limited subset of the 7-bit ASCII range. In order to support email addresses like the one in the question both the sending and receiving email servers need to support an extension to SMTP called SMTPUTF8 defined in RFC 6531.
According to a conversation I had with Amazon SES's support team SMTPUTF8 isn't widely supported currently (23 Nov 2017) and as such they don't support it either. Their development team is working on it, however they have no idea when, or even if, it will make it to production.
The following comment that is currently in the .Net SDK documentation about MIME Encoding seems to be somewhat of a red herring.
By default, the string must be 7-bit ASCII. If the text must contain any other characters, then you must use MIME encoded-word syntax (RFC 2047) instead of a literal string. MIME encoded-word syntax uses the following form: =?charset?encoding?encoded-text?=. For more information, see RFC 2047.
Since I chatted to Amazon about this they seem to be correcting some parts of the documentation a better description can be found in the API documentation.
Amazon SES does not support the SMTPUTF8 extension, as described in RFC6531. For this reason, the local part of a destination email address (the part of the email address that precedes the @ sign) may only contain 7-bit ASCII characters. If the domain part of an address (the part after the @ sign) contains non-ASCII characters, they must be encoded using Punycode, as described in RFC3492.
QUESTION
RFC 2047 defines the encoded-words mechanism for encoding non-ASCII character in MIME documents. It specifies that whitespace characters (space and tabs) are not allowed inside the encoded-word.
However, RFC 5322 for parsing email MIME documents specifies that long header lines should be "folded". Should this folding take place before or after encoded-words decoding?
I recently received an email where encoded-text part of the header had a newline in it, like this:
...ANSWER
Answered 2018-Oct-18 at 14:53I misread the question and answered as if it was a different sort of whitespace. In this case the white space appears inside the MIME word, not multiple ones separated by white space.
This sort of thing is explicitly disallowed. From the introduction to the format in RFC2047:
QUESTION
My apology if I am asking a beginners question.
May I ask what is the difference with The Q encoding in rfc2047 and Quoted-Printable Content-Transfer-Encoding rfc2045?
The "Q" encoding is similar to the "Quoted-Printable" content-
transfer-encoding defined in RFC 2045.
I am trying to implement decode logic using ruby's unpack. I have read below page and trying to understand why first.gsub('_',' ') is required for Q encoding.
...ANSWER
Answered 2018-Feb-08 at 04:12For me by reading RFC 2047 again , I have realized that below approach does not decode underscore properly , in cases where underscore is encoded as =5F.
QUESTION
I am trying to use SMTP in Google Cloud, you will see that Google has blocked ports 25, 587 for sending emails, so I want to use SparkPost for sending emails.
What I have configured in VestaCP is the following:
...ANSWER
Answered 2018-Feb-07 at 23:59Ready!
The solution were in auth_relay:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install rfc2047
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page