On Fri, 15 Oct 2010 15:02:10 -0700, Ian Fairclough
<[log in to unmask]> wrote:

>Archived posts are currently not available. Either the archives do not exist or 
>you are not authorized to browse them with the email address you used to log in.
>
>She has registered with the Listserv site here at Mason, and still gets this 
>message.

The email address that she registered a password for is different from the
address as subscribed to the list, perhaps only slightly but importantly.

>In an attempt to troubleshoot, a co-worker who has had nothing to do with the 
>list (and whose computer therefore should not be "recognized") got a password 
>and accessed Listserv.  She got the same error message.  

Anybody can obtain a LISTSERV password for their address, but this conveys no
privileges whatever.  To access a list you must be subscribed (or an Owner or
Administrator).  If the subscribed address is even slightly different from the
address that registered the password, LISTSERV does not see you as the same
person and does not grant you access.  So everything is working exactly as it
should for both persons.

>She was, however, able 
>to access the archives page of a different list to which she is subscribed.

Ah, but the important difference is her exact registered address is subscribed
to that other list.  It is that exact match, NOT the password, that grants
access to that other list.  As to the first person, her addresses do not
match.  Until they do, she will not have access.  

If the subscribed address is [log in to unmask] and she registered the address
[log in to unmask] those addresses do not match (Linda@... <> linda@...) and she
will not have access.  The right side of @ is not case sensitive, but the left
side is, unless the Owner encodes 
Misc-Options= IGNORE_EMAIL_CASE
in the list configuration.

Of course it might be still another problem as [log in to unmask] vs.
[log in to unmask]  Again these might function equally but LISTSERV will not see
them as the same and will not grant access.