modify.dkim.require_sender_match doesn't do anything in practice #465
Labels
bug
Something isn't working.
ready-for-release
Feature is implemented and available for testing in dev branch. It will be included in the next rele
Milestone
My apologies for not following the bug report template. This is a bug I've spotted by reading the source code, not running Maddy in production - I'm trying to replace an ancient Postfix server and still figuring out the configuration I need, using source as a supplemental documentation.
I believe
modify.dkim
'srequire_sender_match
setting is not doing anything. The setting is recognized, but all it does is creation of emptystruct{}{}
s inModifier.senderMatch
, with this field not referenced anywhere else. To best of my awareness, it's simply not used. Unit tests only ever use"off"
as a value.Before 9915c8a there used to be a
shouldSign
function that did some checks, but those checks were lost during the overhaul.The dysfunctionality is probably harmless, as it's a responsibility of
check.authorize_sender
module to perform the proper authorization checks. Nonetheless, to avoid confusion and possible false expectations I would suggest entirely removingsenderMatch
struct field and adding a depreciation warning upon seeingrequire_sender_match
, saying that this setting is non-functional.Thank you!
The text was updated successfully, but these errors were encountered: