Re: equal signs omitted in body of message?
"Kevin J. McCarthy" <[email protected]> Wed, 8 Apr 2026 14:44:09 +0800
| Newsgroups | gmane.mail.mutt.user |
|---|---|
| Message-ID | <adX5OZCVhJoL7bMp@qinghai> |
--ZpulTmB/DNRMo72M Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Apr 07, 2026 at 09:01:15PM -0500, Greg Marks wrote: >Following the discussion here: > > https://stackoverflow.com/questions/38324093/php-html-email-equals-sign= -in-email-is-being-converted-to-different-characte > >I attempted to resend the message with the original URL written as: > > https://www.youtube.com/watch?v=3D3DvDktNSENjUU The sender on that stackoverflow question was manually creating and=20 sending an email. In their headers for the HTML part, they said the message contents were: Content-Transfer-Encoding: quoted-printable But they did not in fact encode that part as quoted-printable. So on=20 the receiving side, the client was trying to decode it as such, even=20 though it wasn't properly encoded, creating the problem. When using a real MUA, such as mutt, the MUA will take care of choosing=20 and properly encoding the message for you, if needed. >Might the issue be that I send messages as plain text but the recipient's >MUA reads them as HTML? Is there some setting in .muttrc that I could >adjust to fix this issue from my end? It's hard to say for sure what's happening, but whatever they are using=20 to read the message is likely the problem. Best course of action is to=20 ask them to report a bug to their MUA, or to their email provider if=20 they use a web interface. Some web interfaces provide a "view raw=20 message" option. It might be interesting to see what that shows where=20 you typed the URL. You could compare it to the message in your $record=20 folder. You can manually set the encoding of your message using the=20 <edit-encoding> command, by default bound to ctrl-e at the compose menu.=20 You could try typing quoted-printable or even base64 at the prompt and=20 sending the message to see what happens on the recipient's side. But=20 there isn't an easy way to automate this, because a normal user doesn't=20 need to do this. --=20 Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA --ZpulTmB/DNRMo72M Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEiXWpszqjeRA4XFMIre92hIAxa9oFAmnV+TkACgkQre92hIAx a9qzuBAAn5RSVIwHKyThNTv2ICpirLlwP88XkXNPad93hxOM510advFQ0KnztDnn 5685xJrUmrtRcOD/Poh3HGkoRHL1uAiYlj/FqLjCov+A110DHWiK/b0Xy/tUveRO PRq0ZdcbOLhlcFhhb+Ptk9+PCuk+g6Zju27GroLpUyyI+NNsl2yhQlOWIjUQvP+3 5WwJxiJ1lxDIlkAUO/s7UYCV7NYKfL0F6zOQivRO4WsaRM/meFpyrgKlOIw+CwHZ Hpi2mnPCnKTuAYB2D4jHrRnqAmReFLnzb33dR8weT27rS32c9vCpmcJJGb6FpmD3 PC5vlPJLbVALWWDrvV+ohlzFKMlWr0LQYMmXuwuSzsZi3kY5HyM8t1T+jT6oygbu ic5NoMYm7yo5MoV5PKj2fNlD/tN4j+y4rL2Xdf+6fSzhFW7VfcI4lXbcs22FnM1d RrDNI8oBNlSjIEF2waRxgetA0q1W67aM4qQMkqA6vL9MDVhkvDxsU41HPOLYvtFe pw1/weeVEuaMiu3If/fkI0AwagtZXEXG2czAmAgkdji2L8uREltLlnYvwnEZugxB pwdDjEg7U2fcrjOCqfjSORTfFmPl3IzfwzzrpMzIM7AxF1RVQO4u9wnQYY5Nii9T gnia7AB1LAXYO5RcjR5k21XbIQJTeoHem4RM6OlYO/q6BFWVUsk= =VrTn -----END PGP SIGNATURE----- --ZpulTmB/DNRMo72M--