Mail::...::Reuse(3pm)

✨ Mail::SpamAssassin::Plugin::Reuse ✨

okay bestie, we're diving into Mail::SpamAssassin::Plugin::Reuse, part of the User Contributed Perl Documentation situation, and it's honestly giving "quiet plugin that does one job flawlessly" 💅

---

🌸 NAME 🌸

Mail::SpamAssassin::Plugin::Reuse — for reusing old rule hits during a mass-check 🎀

---

🦋 SYNOPSIS 🦋

loadplugin    Mail::SpamAssassin::Plugin::Reuse

ifplugin      Mail::SpamAssassin::Plugin::Reuse

reuse NETWORK_RULE [ NETWORK_RULE_OLD_NAME ]

run_reuse_tests_only 0/1

endif

---

💖 DESCRIPTION 💖

So the whole point of this plugin, no cap, is that it works in conjunction with mass-check --reuse to map the rules that got hit in your input messages over to the rule hits in your mass-check output. That's it. That's the mission. It's matching up vibes across two worlds and it's iconic for it ✨

---

👑 run_reuse_tests_only 👑

Now this one is the main character, lowkey. run_reuse_tests_only 1 is a special option meant for spamassassin and spamd use. Here's the tea:

• Only the tests that got flagged for reuse will actually run 🧚
• It will also _enable_ network/DNS lookups 👀 (yes, really, underline-enable, that's not a typo, that's the energy)
• It's mainly intended for fast mass processing of corpus messages, so they can be properly reused later 🍓

fr fr, here's what that looks like in the wild:

spamd --pre="loadmodule Mail::SpamAssassin::Plugin::Reuse" \
  --pre="run_reuse_tests_only 1" ...

And like… a dedicated spamd set up exactly like this could totally be scripted to slap an X-Spam-Status header onto messages super efficiently. Efficiency queen behavior 👑

---

🌈 and that's the whole page 🌈

okay periodt, that's everything — no filler, no skipped sections, just the good stuff. This page came from the User Contributed Perl Documentation for perl v5.40.1, dated 2026-07-23, and yeah, that's the sign-off 🫶 go forth and reuse those rule hits bestie 💜