Skip to Content.
Sympa Menu

en - [en@sympa] Quoted Printable corruption involving Sympa (6.2.80) and Exchange Online

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: David Carter <address@concealed>
  • To: "address@concealed" <address@concealed>
  • Subject: [en@sympa] Quoted Printable corruption involving Sympa (6.2.80) and Exchange Online
  • Date: Fri, 23 Oct 2026 08:25:12 +0100

Good morning,

I _think_ that the following is a problem with Exchange Online rather than Sympa. This message is just trying to find out if anyone else is seeing the same thing right now.

We have been running Sympa for a good few years now. I upgraded from 6.2.78 to 6.2.80 shortly after it was released, but otherwise very little has changed recently.

A few weeks back our users started to report problems with messages that they had received via our Sympa instance. The first report was some time after the 6.2.80 upgrade. I don't _think_ that 6.2.80 is to blame, but it seems important to report the sequence of events accurately.

It looks like Quoted-Printable encoding in text/html sections:

Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

are being corrupted. As one specific example, the following:

---8<---
We are pleased to present the Term Card for the Michaelmas meetings of the =
Moral Sciences Club (attached), and to announce our first meeting of term. =
---8<---

was transformed into:

---8<---
We are pleased to present the Term Card for the Michaelmas meetings of the =
=3Doral Sciences Club (attached), and to announce our first meeting of term=
. =3Dn=0A=
---8<---

"Moral" following a QP soft line break has become "=3Doral", where "=3D" is QP encoding for '='. =0A (carriage return, \r) is also interesting.

It looks like something has attempted to decode the quoted-printable, and then made a hash of re-encoding it after re-flowing the lines.

Curiously the corresponding text/plain sections aren't affected at all.

I now have reports involving half a dozen different lists, but that is probably only the tip of an iceberg. I (personally) am on a lot of different mailing lists, and I don't see any problems.

This problem only seems to affect messages sent to our Exchange Online tenancy: messages sent to 3rd parties such as gmail or 163.com at the same time seem to be fine. It also only seems to affect a fraction of the users on our Exchange Online tenancy.

This only seems to affect lists which have large numbers of subscribers. However this might just be the lists who have enough subscribers who notice the problem and complain.

Sympa is generating a number of outgoing messages in these cases because of "nrcpt 250" in /etc/sympa/sympa.conf. These are further limited to 100 recipients per SMTP transaction by the (default) settings on the SMTP transport used by Exim.

If a single RFC822 message on our Exim spool is delivered as multiple SMTP transactions capped to 100 recipients, we have evidence that messages in one batch are fine, but messages in another batch might be corrupted. I don't currently have any evidence either way about the messages delivered inside a single SMTP transaction.

All of the messages have been DKIM signed by our Sympa instance, and the DKIM signature appears in the messages that people receive.

The recipients who see valid data all have:

dkim=pass (signature was verified) header.d=cam.ac.uk

Meanwhile the recipients with corrupted messages all see:

dkim=fail (body hash did not verify) header.d=cam.ac.uk

This implies something downstream of Sympa is mashing the messages.

I don't have any reason to think that Exim on our outgoing SMTP smarthost might be doing this, especially given that some recipients see corrupted messages while others see intact messages from a single message on the Exim spool (delivered as multiple SMTP transactions).

If a single RFC822 message on the Exim spool is delivered in multiple batches, then multiple *.mail.protection.outlook.com gateways are likely to be involved. It looks like Microsoft always advertise 4 different IP addresses for our tenancy, and the list is constantly changing.

I am unable to reproduce the fault by using "swaks" to replay SMTP deliveries via specific *.mail.protection.outlook.com gateways.

I'm 99% sure that this is Exchange Online doing something daft, but the 1% of doubt is causing quite a lot of stress. I was just curious if anyone else running Sympa with lots of users in an Exchange Online tenancy have been seeing something similar recently, hence this message.

Thanks in advance for any wisdom that people can share,

--
David Carter Email: address@concealed
University of Cambridge,
Information Services,
7 J J Thomson Avenue,
Cambridge UK. CB3 0RB



  • [en@sympa] Quoted Printable corruption involving Sympa (6.2.80) and Exchange Online, David Carter, 10/23/2026

Archive powered by MHonArc 2.6.19+.

Top of Page