SYMPA::REQUEST::HANDLER::DEL(3Sympa)

✨ NAME ✨

Sympa::Request::Handler::del — the request handler that handles del, bestie 💅 it's part of sympa 6.2.80, and yeah it lives in section 3 of the manual (the library-call girlies), so you'll see it written out all fancy like Sympa::Request::Handler::del(3Sympa).

---

🌸 DESCRIPTION 🌸

Okay so picture this: one user wants to yeet another user off a list. That's the whole job here — remove a user from a list when somebody else requested it. Not the user themselves being like "unsubscribe me", no no, this is a third party doing the removing 👑

Before it does anything spicy, it verifies the authorization, then it sends out acknowledgements — unless quiet is specified, in which case it just… doesn't 📪

Heads up, and this is important: the authorization scenario del.* is applicable only when the {role} attribute is 'member' (which is the default). In the other cases, the scenario processing should be skipped. Don't skip that part of reading this. I'm serious 😭

🎀 Attributes 🎀

Also go look at "Attributes" in Sympa::Request::Handler — there's lore there too 💖

• {email} — Mandatory. This is the e-mail of the user who's getting deleted. No email, no deletion, sorry bestie.
• {force} — Optional. If you give it a true value, users will get deleted even if the list is closed. Yeah, it's giving "no doors can stop me" 🔥
• {role} — Optional. What kind of user are we deleting here: 'member', 'owner' or 'editor'. The default value is 'member'.

Little history moment: this attribute was introduced way back on Sympa 6.2.67b.2 🫶

• {quiet} — Optional. Don't notify addition to the user. 🤫

---

👑 SEE ALSO 👑

• Sympa::Request::Handler.

---

🦋 HISTORY 🦋

And that's the whole vibe, babes ✨ this page is from version 6.2.80, dated 2026-10-19, and it's all under the Sympa umbrella — go off, del handler, you ate 💅🌸🎀