Comment 3 for bug 1006345

On May 30, 2012, at 12:28 PM, Richard Wackerbarth wrote:

>I think that it is important for this to be controlled an administrative list
>policy setting. When someone logs in using BrowserID, for example, and then
>subscribes to a new mailing list, the subscription can be marked as "email
>confirmed". But if they simply enter an email address on a form, the website
>need to be able to trigger the issuance of a "request subscription
>confirmation" email.

What does "subscribe as an anonymous user" actually mean?

Do you mean, without a user account on Postorius? It makes no sense to me in
the context of the core, because subscribing is the very act of providing an
email address, which de-anonymizes you.

Now, it may make sense to support a subscribe-without-email-confirmation step,
but I think that should not be an exposed workflow for end users. To much
potential for spam.

A valid use case for non-confirmation subscriptions might be: Alice manages a
team at work and wants to run a mailing list for all of her team members. Bob
joins the team, so Alice wants to subscribe him; since he's a direct report,
she doesn't need nor want him to confirm his email.

This can be handled in a number of ways, using the general roster API. mm3
currently supports setting a message's recipients via flat file, so that might
be one way.