Re: [mlmmj] RFE: improving access rejection messages
Baptiste Daroussin <[email protected]> Thu, 05 Oct 2023 06:37:47 +0000
| Newsgroups | org.mlmmj.mlmmj |
|---|---|
| Message-ID | <qwhqlgl2grxmcbsfvblsjz6quy3i3cizo4jxmq4gfv5cjodtoj@h2ywqognkpdl> |
Le 4 octobre 2023 23:20:39 GMT+02:00, Konstantin Ryabitsev <[email protected]> a écrit : >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 > > I do like the idea, do you plan to provide a patch? Otherwise please fill an issue with the proposal on codeberg so I keep track of the idea. Best regards, Bapt