This question often comes up in Google, so I decided to add an important note. Don’t ever use X-Auto-Response-Suppress in your filters as suggested in the other answer. X-Auto-Response-Suppress is used by Exchange to tell other servers to not send auto-replies in response to an email. It doesn’t mean that this email is an auto-response. … Read more
To elaborate on the answer by @Fls’Zen, yes the proper method is to enclose the name in double-quotes. From a practical point of view there’s no harm in wrapping all names in double-quotes, just be sure to escape a double-quote if it appears in the display name \” (or just replace with a single-quote). But … Read more
Update For a more practical and up-to-date answer, have a look at Palec’s answer. The specified character encoding in Content-Type does only describe the character encoding of the message body but not the header. You need to use the encoded-word syntax with either the quoted-printable encoding or the Base64 encoding: encoded-word = “=?” charset “?” encoding … Read more
I tested dkarp’s solution with gmail and it was filtered to spam. Use the Reply-To header instead (or in addition, although gmail apparently doesn’t need it). Here’s how linkedin does it: Sender: messages-noreply@bounce.linkedin.com From: John Doe via LinkedIn <member@linkedin.com> Reply-To: John Doe <John.Doe@gmail.com> To: My Name <My.Name@gmail.com> Once I switched to this format, gmail is … Read more