Thanks for your responses. After I sent the note we did
notice LISTSERV(tm) spam notices with similar addresses too
so we knew others were probably getting the spam.

    It looks like the only mystery really is that there is the
curious naming of the forged addresses. The other weird things
were explained when we did a bit more checking. I'm not sure
if the bot or whatever that is generating these is more
prolific than others or if it is just easier to identify
these as having something in common.

    marty

Listserv Admin wrote:
> Hello Marty,
>
> Yes - this started here on July 20th non-stop and is still going strong.
>
> The variation of [log in to unmask], changes frequently, but one
> pattern that
> we can see in the logs is that quite often, e-mail is sent to both
> Listname-Request@ and Listname-L@, but always to the listname-request@
> address
> first and in these cases the variation of [log in to unmask] is
> identical.
>
> What is a puzzle here is that some of this e-mail is going to only recently
> created Confidential= Yes mailing lists - so we don't know how they are
> getting the listnames.
>
> We anticipate problems if the time delay between sending to
> listname-Request@,
> presumably a subscription request, and to the corresponding Listname-L@ was
> increased, as some of our List Owners might approve/add the subscription.
>
> --Trish
>
> Trish Forrest
> Queen's University
>
>
> On Thu, 26 Jul 2007, Marty Hoag wrote:
>
>>   I used to administer LISTSERV(tm) here long ago but the
>> current administrators came to me and I volunteered to check
>> with this list. We're having some mysterious behavior lately.
>> I just wanted to send a quick note to see if anyone else has
>> seen this or it is an old problem. We've just started looking
>> into this.
>