ApprovedAddMembers(): Rid ourselves of this horror. The right way to

    do it now is to loop over ApprovedAddMember() -- which no longer
    Save()'s after each addition! -- catching any exceptions that it
    might raise.  The whole API for ApprovedAddMembers() was gross.

AddMember(): Change the signature so that it takes only two arguments
    (the cancerous growth of the parameters was becoming a
    nightmare).  The first argument is a "userdesc", essentially an
    instance with some well defined public attributes, and the old
    "remote" parameter.

    Any parsing of strings into fullname, emailname should be done
    before AddMember() is called.  userdesc holds everything relevant
    about this subscription request: the language, password, digest
    flag, etc.

    AddMember() still validates the email address, checks to see if
    its already a member, and applies the list's subscription policy.

ApprovedAddMember(): This now does all the work of adding a new
    member, and setting their digest flag.  It also sends the
    subscriber an acknowledgement, and the admin the subscribeack.
    It assumes that the subscription request has passed list policy.

ProcessConfirmation(): Remove the backwards compatibility hack for
    pre-2.1a3 entries in the requests.db.  That database automatically
    updates its schema now.

0 files changed, 0 insertions, 0 deletions