Sender: |
|
Date: |
Mon, 14 Mar 2011 14:49:07 -0500 |
Reply-To: |
|
Message-ID: |
<525EA0117A034C5D85AAE53AAF59DDFC@Hal9K> |
Subject: |
|
MIME-Version: |
1.0 |
Content-Transfer-Encoding: |
7bit |
In-Reply-To: |
|
Content-Type: |
text/plain; format=flowed; charset="iso-8859-1";
reply-type=original |
From: |
|
Parts/Attachments: |
|
|
Based on personal experience, I believe the problem is that if you don't log
out from ListServ when confirming on behalf of the old account, the login
cookie identifies each successive confirmation with that account. To get it
credited to the new account, you have to be logged in with the new account,
and that won't happen if you click the link while still logged in with the
old account.
On the other hand, last time I tried it, if you log in with the new account
for the first confirmation (the one sent to the old account), ListServ will
think it's done. A confirmation from the new account ends the process.
Hal Keen
--------------------------------------------------
From: "Dayn Schulert" <[log in to unmask]>
Sent: Monday, March 14, 2011 1:44 PM
To: <[log in to unmask]>
Subject: [LSTOWN-L] CHANGE command loop problem
> Hello All,
>
> I've recently had one of our list owners inform me of an issue that he
> is having with his list concerning the CHANGE command. What is basically
> happening is that when someone attempts to use the command they are send
> an email with a click-to-confirm link. When they click this link, they
> get sent another email with a click-to-confirm link. When they click any
> of the confirm links (whether it be the first confirm email or the
> latest) they receive the following message in their browser:
>
> Confirming:
>> CHANGE [log in to unmask]
> A confirmation request is being mailed to your new
> address
> ([log in to unmask]). For security reasons, the change will not be made
> until it has been confirmed from the new address. Simply wait for
> the
> confirmation request to arrive, then follow the instructions to confirm
> the
> change of address.
>
> The following is a more detailed sequence of events:
> 1) An email is sent from the user's current email to the Listserv
> containing the following command:
> CHANGE listnames [log in to unmask]
> 2) The currently subscribed email account receives an email informing
> them that the email change will take place after it is confirmed by the
> new account
> 3) The confirmation email with a click-to-confirm link is received by
> the new email account.
> 4) The link is clicked and the web browser displays the above message in
> the LS interface
> 5) Another confirmation email with a click-to-confirm link is received
> by the new email account.
> 6) The link is clicked and the web browser displays the above message in
> the LS interface
> Repeat steps 5-6
>
> Does anyone have any insight into either:
> A) Fixing this problem
> or
> B) Changing the type of confirmation email to the "reply with ok" type?
>
> Thanks so much in advance,
> Dayn
>
> ############################
>
> To unsubscribe from the LSTOWN-L list:
> write to: mailto:[log in to unmask]
> or click the following link:
> http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=LSTOWN-L&A=1
>
############################
To unsubscribe from the LSTOWN-L list:
write to: mailto:[log in to unmask]
or click the following link:
http://peach.ease.lsoft.com/scripts/wa.exe?SUBED1=LSTOWN-L&A=1
|
|
|