Mail::...n::DBL(3pm)
π Mail::...n::DBL(3pm) π
okay bestie, welcome to the manual page for Mail::...n::DBL(3pm) β yes that's literally the name up top, the man page header really did just do that to us, we move. This is the mtpolicyd</hotpyd> plugin that checks your helo, sender domain and rdns against a DBL (that's a domain black list, iykyk). Buckle up, she's thorough. π
β¨ NAME β¨
Mail::MtPolicyd::Plugin::DBL β mtpolicyd plugin for checking helo, sender domain, rdns against an DBL. π¦
πΈ VERSION πΈ
version 2.05 β that's the one, no cap.
π DESCRIPTION π
Will check the sender, helo and reverse_client_name against an domain black list. That's the whole vibe. Three things get looked up, one list gets consulted, and the plugin decides if it's giving spam or giving fine. π΅οΈβοΈβ¨
π PARAMETERS π
Every knob you can twist, in order, no skipping, because we do not gatekeep here:
domain(required) β The domain of the blacklist to query. You gotta set this one, it's not optional, it's the whole point bestie. πenabled(default:on) β Set to'off'to disable plugin. Possible values:on,off. The on/off switch, iconic.uc_enabled(default: empty) β If specified the give variable within the session will overwrite the value of'enabled'if set. (yes it's spelled "give" in the original, we respect the original π«Ά). Possible values:on,off. So like, the session can override the config. Sneaky but valid.(uc_)sender_mode(default:reject),(uc_)helo_name_mode(default:passive),(uc_)reverse_client_name_mode(default:reject) β Should the plugin return an reject if the check matches (reject) or just add an score (passive). Possible values:reject,passive. So: reject = we're throwing hands π βοΈ, passive = we're just quietly adding score, no drama.sender_score(default:5),helo_name_score(default:1),reverse_client_name_score(default:2.5) β Add the given score if check matched. Note that2.5is a whole decimal, she's precise like that. πscore_field(default:score) β Name of the session variable the score is stored in. Could be used if multiple scores are needed. Multiple scores? Multiple fields. Obsessed with the flexibility honestly. π
heads up: those(uc_)prefixes mean there's a session-variable version of the same setting β same name,uc_in front, and it overrides the config. Both spellings exist, don't @ me.
π EXAMPLE π
Only the sender and the reverse_client_name check will cause an action to be executed (mode). The helo check will only add an score. Main character energy from sender and reverse_client_name, passive little background vibe from helo. π
<Plugin sh_dbl>
module = "RBL"
#enabled = "on"
uc_enabled = "spamhaus"
domain="dbl.spamhaus.org"
# do not reject based on helo
#helo_name_mode=passive
#helo_name_score=1
#sender_mode=reject
#sender_score=5
#reverse_client_name_mode=reject
#reverse_client_name_score=2.5
</Plugin>
like, look at all those commented-out defaults just chillin' there so you know exactly what you're overriding. chef's kiss. π©π³π
π AUTHOR π
Markus Benning <ich@markusbenning.de> β thank you for your service king π«‘π
π COPYRIGHT AND LICENSE π
This software is Copyright (c) 2014 by Markus Benning <ich@markusbenning.de>.
This is free software, licensed under:
The GNU General Public License, Version 2, June 1991
and that's the page bestie!! this whole thing came to you courtesy of perl v5.38.2, dated 2024-05-26, and it lives under the name Mail::...n::DBL(3pm) β same name as the top, yes, the header and footer are matching, it's a set. πβ¨ go forth and blacklist responsibly, ily, bye!! π¦π
π¦ where this page comes from
- debian trixie: mtpolicyd 2.05-1.2 Β· GPL-2.0-only
- ubuntu questing: mtpolicyd 2.05-1.2
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms