Subscription Approval allows the list owner of a mailing list to make the final decision of if a would-be subscriber is allowed to join a mailing list.
What's neat is that the entire rest of the subscription process, including the closed-loop opt-in can still be enabled and used - this just tacks on (yet) another step.
The other neat thing is, if you find some of those other steps uneeded and redundant, this allows you to have another, alternative and direct confirmation process, without giving up too much security.
This feature can be enabled per list, in the list control panel under,
Your Mailing list - Options
Looking for the fieldset labeled,
Subscription Requests Approving/Denying
Check the option labeled,
Enable Subscription Requests Approving/Denying
When a would-be subscriber completes the subscription confirmation process, they'll be told that their subscription is being held until the list owner approves it.
At the same time, an email message will be sent to the list owner, with instructions on how to approve, or deny a subscription.
The list owner may also log into their mailing list control panel and view all the awaiting addresses to be approved by visiting:
Your Subscribers - View
Click the button on the top labeled,
This should present the list owner with the entire list of addresses that are awaiting approval.
There are two buttons to act upon this list of address.
Check the addresses you'd like to work with and either press the button labeled,
Approved Checked Subscription Requests
to approve requests, or press the button labeled,
Deny Checked Subscription Requests
to deny requests.
Since this feature basically skips *over* all the options you can set in the, Subscriptions fieldset in the, Your Mailing List - Options screen, so none of those options are available, if this feature is turned on.
Even though the email messages that get sent out and the, "Subscription Successful" HTML message *are* templated out, the interface to edit them on a per-list basis has not been made.
You may edit them on a installation-wide basis by editing the defaults in the Config.pm file.