You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From: =?UTF-8?Q?Sender=20Name?= <from@example.com>\r\n
To: =?UTF-8?Q?Recipient=20Name?= <to@example.com>\r\n
But some email validation services (RSPAMD or SpamAssassin) gives to us a warning "TO_EXCESS_QP: To that contains encoded characters while quoted-printable is not needed as all symbols are 7bit", because the strings "Sender Name" and "Recipient Name" has ASCII compatibility already. So, without direct fix in Laminas\Mail\Header\AbstractAddressList::getFieldValue() has no any ability do not encode those strings always.
I would like do not encode ASCII compatibility strings without any reasons.
From: Sender Name <from@example.com>\r\n
To: Recipient Name <to@example.com>\r\n
@Slamdunk Hi!
I would like to, but the problem is not at To/From headers only. For the other headers the encoding may be not necessary either. HeaderWrap::mimeEncodeValue() using by many different places, therefore, the library need to refactor the all. It's a big work and, for some reasons, the better option will use the PHPMailer library, that respect necessary of encoding.
Bug Report
Version: 2.14.1
Summary
For example, we have the follows code:
From
andTo
headers will looks like:But some email validation services (RSPAMD or SpamAssassin) gives to us a warning "TO_EXCESS_QP: To that contains encoded characters while quoted-printable is not needed as all symbols are 7bit", because the strings "Sender Name" and "Recipient Name" has ASCII compatibility already. So, without direct fix in
Laminas\Mail\Header\AbstractAddressList::getFieldValue()
has no any ability do not encode those strings always.I would like do not encode ASCII compatibility strings without any reasons.
Therefore, I think, the fix should looks like
The same problem was in Symphony CMS symphonycms/symphonycms#2858
Current behavior
Name of email encode always.
How to reproduce
See summary section.
Expected behavior
Do not encode name of email without necessary.
The text was updated successfully, but these errors were encountered: