Hi Hamish,

I thought you might be interested to know you email, by the time it
reached me through the mailing list, had an RFC violation in its header.

    "multipart/alternative" type in message must be encoded in
    7bit, 8bit, or binary, per RFC 2045 (6.4).

Here are some of the relevant header fields.

     1  Content-Type: multipart/alternative;
            boundary="----sinikael-?=_1-16757796127270.6809426512989821"
     2  User-Agent: Desktop
     3  Content-Transfer-Encoding: quoted-printable
     4  X-ZohoMailClient: External
       
     5  ------sinikael-?=_1-16757796127270.6809426512989821
     6  Content-Type: text/plain; charset=utf-8
     7  Content-Transfer-Encoding: quoted-printable
       
        ...
       
     9  ------sinikael-?=_1-16757796127270.6809426512989821
    10  Content-Type: text/html; charset=utf-8
    11  Content-Transfer-Encoding: quoted-printable
       
        ...
    13  ------sinikael-?=_1-16757796127270.6809426512989821--

The complaint is about 3 because 1's multipart/alternative means
‘quoted-printable’ isn't valid, as the error message says.

That encoding is fine for the MIME parts within the email so 7 and 10
aren't a problem.

You may want to check your emails which don't go through the mailing
list have the same issue and if so report it upstream, presumably to
ZohoMail, given 4 and 2.  Failing the RFC validation is a nudge towards
considering the email spam in some quarters.

-- 
Cheers, Ralph.

-- 
  Next meeting: Online, Jitsi, Tuesday, 2023-03-07 20:00
  Check to whom you are replying
  Meetings, mailing list, IRC, ...  http://dorset.lug.org.uk
  New thread, don't hijack:  mailto:dorset@mailman.lug.org.uk

Reply via email to