From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: mlmmj@mlmmj.org
Subject: [mlmmj] RFE: improving access rejection messages
Date: Wed, 04 Oct 2023 21:20:39 +0000 [thread overview]
Message-ID: <20231004-unsnap-cofounder-ed17ed@meerkat> (raw)
Hello:
One of the problems I'm having is not being able to tell submitters exactly
why their message was denied. For example, I may have the following rules in
my access file:
deny ^Content-Type: text/html
deny ^Authentication-Results:.*dmarcúil
deny ^Subject:.*forbidden-topic
Currently, there is only one message generated on deny, and I have to include
all possible reasons why didn't allow the message through. This can be greatly
improved if we can tell the user exactly why their message was rejected,
instead of making them guess.
I propose extending the functionality to additionally include the reason that
can point at a different file, e.g.:
deny-html ^Content-Type: text/html
deny-dmarc ^Authentication-Results:.*dmarcúil
deny-topic ^Subject:.*forbidden-topic
The dash-extension is used to identify the listtext to use, if present. For
example, if "deny-html" is triggered, the rejection message is loaded from
listtexts/deny-post-access-html. If "deny-dmarc" then from
deny-post-access-dmarc. If there is no matching file present, the usual
fallback path is followed (deny-post-access, then deny-post).
Best regards,
-K
next reply other threads:[~2023-10-04 21:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 21:20 Konstantin Ryabitsev [this message]
2023-10-05 6:37 ` [mlmmj] RFE: improving access rejection messages Baptiste Daroussin
2023-10-05 13:30 ` Konstantin Ryabitsev
2023-10-05 13:51 ` Baptiste Daroussin
2023-10-05 16:17 ` Mads Martin Jørgensen
2023-10-06 4:55 ` Robin H. Johnson
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=20231004-unsnap-cofounder-ed17ed@meerkat \
--to=konstantin@linuxfoundation.org \
--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 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).