From: Baptiste Daroussin <bapt@nours.eu>
To: mlmmj@mlmmj.org
Subject: [mlmmj] Where to send patches
Date: Wed, 26 May 2021 13:06:07 +0000 [thread overview]
Message-ID: <20210526130607.us4pobshuj5dnpb4@aniel.nours.eu> (raw)
Hello everyone,
I am migrating FreeBSD's mailing lists from mailman2 to mlmmj, in the process I
had to write a couple of patches for mlmmj, I would like to upstream those
patches if possible.
My understanding is that the origin developement site is dead, and there has been a
kind of takeover on gitlab. Am I right? so pushing things upstream now means
pushing things to that gitlab?
The 2 patches in question are the following:
- A patch which adds a new tunnable (boolean) nobounceprobe to be able to
disable probes on demande if needed.
- A patch which Allow to support X-Origin-From header. This one is quite
special. in our setup we didn't want to use the mungefrom patch that we can
find on the mailing list (and on the gitlab repo), because we only want to
munge when we actually need to and not always. so we are using the
developement version of rspamd to handle the muning part. the interesting this
is when rspamd do munge, it sets the original From into the new
X-Original-From header, so our patch is taking in account this new header for
mlmmj-process when testing is the sender is a subsriber to the mailing list or
a moderator, it also uses it to send back the denial email if the email was
denied.
Best regards,
Bapt
next reply other threads:[~2021-05-26 13:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 13:06 Baptiste Daroussin [this message]
2021-05-30 21:45 ` [mlmmj] Where to send patches Geert Stappers
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=20210526130607.us4pobshuj5dnpb4@aniel.nours.eu \
--to=bapt@nours.eu \
--cc=mlmmj@mlmmj.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.