On Wed, 12 May 1999, Ben Parker wrote:

>On Wed, 12 May 1999 10:40:58 PDT, Rich Greenberg <[log in to unmask]> wrote:
>
>>The
>>subscriber can use:
>>
>>   Change Listname-L newaddress@newnode
>>
>>which MUST be sent from the old address and confirmed from both
>>addresses, so can't be used by the subscriber unless they have
>>overlapping access to both addresses.
>
>No, it is confirmed from the New Address only.  Yes, the user must have access
>to both addresses for this to be successful.

I hate to spoil anyone's party here, but I just did this last night,
and I just checked the confirmation cookie, and it was sent to my
***OLD*** address.  The confirmation that the change had occurred was
also sent to my old address.  The new address is actually an alias for
this one, but checking both Listserv's "To" address and the routing
information in the headers shows that Listserv sent both the cookie
and the confirmation to *this* address, and not the new (as yet
implemented on only one list) alias for it.

The version of Listserv involved in this is still 1.8d Beta, not the
1.8d release.

Dennis Budd

>
>>From the LISTSERV 1.8d Release Notes:
>
>*****************************************************
>* New CHANGE command to update subscriber addresses *
>*****************************************************
>
>A new CHANGE command is available in version 1.8d. There are two
>syntaxes: A general user syntax and a list owner/LISTSERV maintainer
>syntax.
>
>General user syntax:
>CHANGE listname|* newaddr
>
>List owner/LISTSERV maintainer syntax:
>[QUIET] CHANGE oldaddr|pattern newaddr|*@newhost
>
>The first form can be used by any subscriber and results in a cookie
>being sent to the new address. This cookie MUST be confirmed by the new
>address, exactly as it was entered, or the command will fail. This is the
>only case where a 1.8d cookie must be confirmed by a specific address.
>Note that this assumes that the user still has login access to both
>addresses, or at least the ability to send mail from the old address.
>
>The list owner form does not use cookies but simply applies the standard
>"Validate=" rules (as for a DELETE command). You can specify a wildcard
>pattern for the old address and *@newhost for the new address to rename
>certain addresses to a new hostname. The CHANGE1 template is sent unless
>you specify QUIET.
>