Mail::...figData(3pm)

💖 Mail::DMARC::ConfigData — the group chat notes 💖

okay bestie, so this is the perl manual page for Mail::DMARC::ConfigData, and yes it lives in section 3pm (that's the "perl module" section, iykyk). It's the lil' config locker for Mail::DMARC and it's lowkey iconic. Let's get into it 🫶

---

✨ NAME ✨

Mail::DMARC::ConfigData — it's literally configuration for Mail::DMARC. That's the whole job. 💅

---

🌸 SYNOPSIS 🌸

here's the vibe, copy-paste ready:

use Mail::DMARC::ConfigData;
$value = Mail::DMARC::ConfigData->config('foo');
$value = Mail::DMARC::ConfigData->feature('bar');

@names = Mail::DMARC::ConfigData->config_names;
@names = Mail::DMARC::ConfigData->feature_names;

Mail::DMARC::ConfigData->set_config(foo => $new_value);
Mail::DMARC::ConfigData->set_feature(bar => $new_value);
Mail::DMARC::ConfigData->write;  # Save changes

read it, get it, slay it. ⭐

---

🦋 DESCRIPTION 🦋

bestie, listen. This module holds the configuration data for the Mail::DMARC module. It also hands you a whole programmatic interface for getting or setting that configuration data — so you're not out here editing files with your bare hands like it's 2009. 🙈

⚠️ not me forgetting the plot twist: to actually make changes, you have to have write access to the Mail::DMARC::ConfigData module. And fr fr, you should attempt to understand the repercussions of your actions before you go changing stuff. Like, know what you're doing. That's the vibe check. 👑

---

💅 METHODS 💅

💜 config($name)

Give it a string argument, and it hands back the value of the configuration item with that name. If no such item exists? You get undef. simple as that. 🎀

💜 feature($name)

Same energy, different closet: pass a string argument and you get the value of the feature with that name. No such feature? undef, bestie. ✨

💜 set_config($name, $value)

Sets the configuration item with the given name to the given value. now here's the tea about what counts as a value: it may be any Perl scalar that will serialize correctly using Data::Dumper. That includes references, objects (usually), and complex data structures. It probably does not include transient things like filehandles or sockets — so don't try it, that's giving chaos. 😭

💜 set_feature($name, $value)

Sets the feature with the given name to the given boolean value. The value gets converted to 0 or 1 automatically — the module does the math so you don't have to. slay. 🔥

💜 config_names()

Returns a list of all the names of config items currently defined in Mail::DMARC::ConfigData. In scalar context? You get the number of items instead. versatile queen. 👑

💜 feature_names()

Returns a list of all the names of features currently defined in Mail::DMARC::ConfigData, or — in scalar context — the number of features. same trick, different list. 🌈

💜 auto_feature_names()

Returns a list of all the names of features whose availability is dynamically determined, or in scalar context, the number of such features. And here's the fine print, don't skip it: this does not include such features that have later been set to a fixed value. 🧚

💜 write()

Commits any changes from set_config() and set_feature() to disk. periodt. Requires write access to the Mail::DMARC::ConfigData module — so if it fails, check your permissions before you spiral. 💀

---

🎀 AUTHOR 🎀

Mail::DMARC::ConfigData was automatically created using Module::Build. Module::Build was written by Ken Williams — but he holds no authorship claim or copyright claim to the contents of Mail::DMARC::ConfigData. iconic of him honestly. 🫶

---

okay and for the lil' footer moment: this page is from perl v5.40.1, dated 2026-07-07, and it's all filed under Mail::...figData(3pm) in the User Contributed Perl Documentation. mwah, go configure something iconic bestie 💖✨🎀🦋🌸