> Not sure what you mean by "doc contrib", but the main docs source
> is in the exim git repo. git.exim.org.
> Only devs have commit permission for that though.
I meant maybe it could be improved how to find the source for the docs
and how someone can submit patches/bug reports.
> Then, there's exim wiki at https://github.com/Exim/exim/wiki which
> is anothoer source of docs.
Interestingly
https://github.com/Exim/exim-website seems to be out of
date. There is no `docbook/4.94/spec.xml`.
> You can raise docs bugs at bugs.exim,org or for minor typoes etc.
> raise it here on the ML, or mail me direct.
I changed the file locally and diffed it. I hope that helps:
❯ diff -u docbook_4.94_spec{,_new}.xml --label=docbook/4.94/spec.xml{,}
--- docbook/4.94/spec.xml
+++ docbook/4.94/spec.xml
@@ -63583,17 +63583,26 @@
<variablelist>
<varlistentry>
<term><varname>$mime_anomaly_level</varname></term>
-<term><varname>$mime_anomaly_text</varname></term>
<listitem>
<para>
<indexterm role="variable">
<primary><varname>$mime_anomaly_level</varname></primary>
</indexterm>
+If there are problems decoding, <varname>$mime_anomaly_level</varname> will be
+1 for broken Quoted-Printable encoding or 2 for broken BASE64 encoding.
+</para>
+</listitem></varlistentry>
+<varlistentry>
+<term><varname>$mime_anomaly_text</varname></term>
+<listitem>
+<para>
<indexterm role="variable">
<primary><varname>$mime_anomaly_text</varname></primary>
</indexterm>
-If there are problems decoding, these variables contain information on
-the detected issue.
+If there are problems decoding, <varname>$mime_anomaly_text</varname> will be
+"Broken Quoted-Printable encoding detected" for a
<varname>$mime_anomaly_level</varname>
+value of 1 or "Broken BASE64 encoding detected" for a
<varname>$mime_anomaly_level</varname>
+of 2.
</para>
</listitem></varlistentry>
<varlistentry>
