Jonathan M. Bresler wrote in list.freebsd-current:
> > FWIW, I got unsubscribed, too. While I were at it, I sent a
> > "which" command to the majordomo, and the result did not list
> > me as a member of freebsd-announce and freebsd-security-
> > notifications. When I tried to re-subscribe, it told me that
> > I am already subscribed...
> >
> > Seems like majordomo is major buggy. ;-)
>
> youare subscribed to freebsd-announce as
> [EMAIL PROTECTED] which oes not match the email
> [...]
Oh, I'm very sorry for the confusion. When I said "I", I
really did not mean myself but the local newsgate (I prefer
to read the lists via NNTP, which is very convenient).
The newsgate is "[EMAIL PROTECTED]".
I sent both the "which" and the "subscribe" commands under
that address, when the problem occured that I described in
my previous mail (see above). I'm pretty sure that I didn't
do anything wrong.
Here's the whole story:
- I sent a "which" command from the newsgate account.
- Got a response with about 30 lists to which that account
is subscribed.
- Compared those lists to the lists that the newsgate
is prepared to handle (and to which it was once subscribed).
- Noticed that three lists were missing: announce, arch, and
security-notifications.
- Sent "subscribe" commands for those three lists to the
majordomo, again using the newsgate account.
- Re-subscription to the -arch list was successful. For the
other two lists, I received a notice that I (the newsgate
account) was already subscribed.
> this is not a majordomo bug.
It is.
Regards
Oliver
--
Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany
(Info: finger userinfo:[EMAIL PROTECTED])
"In jedem Stück Kohle wartet ein Diamant auf seine Geburt"
(Terry Pratchett)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
