mlmmj.mlmmj.org archive mirror
 help / color / mirror / Atom feed
From: Florian Berger <flberger-lists@posteo.net>
To: mlmmj@mlmmj.org
Cc: webmaster@plonk.de
Subject: [mlmmj] README.exim4 broken, needs update
Date: Thu,  7 Dec 2023 22:29:20 +0000	[thread overview]
Message-ID: <df58ab7f-0592-4055-b5cd-3769fa210edc@posteo.net> (raw)

The mlmmj.org website hosts a tutorial for exim 4 setup at http://mlmmj.org/docs/readme-exim4/ , 
which in turn refers to https://plonk.de/sw/mlmmj/README.exim4 as the most recent original (hence 
author Jakob Hirsch in cc:).

For the transport configuration, it advertises:

mlmmj_transport:
   [irrelevant lines left out]
   command = /usr/local/bin/mlmmj-recieve -F -L MLMMJ_HOME/${lc:$local_part}

This will no longer work in recent versions of exim (4.94 and above). exim now considers 
sender-derived data tainted, and will refuse to use them as-is. See

- https://git.exim.org/exim.git/blob/HEAD:/src/README.UPDATING
- https://www.exim.org/exim-html-current/doc/html/spec_html/ch-string_expansions.html

As far as the mlmmj config is concerned, $local_part is considered tainted.

It can reasonably be de-tainted by changing it into a directory lookup:

mlmmj_transport:
   [unchanged lines left out]
   command = /usr/bin/mlmmj-receive -F -L "${lookup {$local_part} dsearch,ret=full {MLMMJ_HOME}}"

To avoind exim users running into issues, the tutorial at plonk.de and mlmmj.org should be updated 
accordingly.


Thanks for considering,

Florian



                 reply	other threads:[~2023-12-07 23:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=df58ab7f-0592-4055-b5cd-3769fa210edc@posteo.net \
    --to=flberger-lists@posteo.net \
    --cc=mlmmj@mlmmj.org \
    --cc=webmaster@plonk.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).