Again, thanks to all of you for your responses. There are a number of thorny
issues in attempting to "fix" (or at least address) what is "wrong" here. The
original conceptual model of something like Mailman isn't quite right for the
situation being faced today in the types of capabilities and
I don't think this is the problem. So far as I know he has been using
single-word passwords with only alphabetic characters in them. I'm really
surprised that there would have been a bug involving initial or terminal
whitespace, but I suppose these things happen. (Trying to imagine how that
coul
t; From: Mark Sapiro [mailto:m...@msapiro.net]
> Sent: Tuesday, January 20, 2015 11:01 PM
> To: ghmerr...@chathamdesign.com; mailman-users@python.org
> Subject: Re: [Mailman-Users] Diagnosing command failures
>
> On 01/20/2015 06:59 PM, Gary Merrill wrote:
> > I was really
2015 6:09 PM
> To: mailman-users@python.org
> Subject: Re: [Mailman-Users] Diagnosing command failures
>
> On 01/19/2015 08:30 AM, Gary Merrill wrote:
> >
> > Second, this is a mailing list for a (loosely run) community band,
> > this user is the president of the band
Thanks.
The suggestions you make about typographical/character issues are precisely
the ones I have made to him -- in part because he has made such errors
previously in other contexts. But unless Mailman provides me with some kind
of record or error log, I have no way of verifying what password h
Is there any technique to diagnose precisely why/how a particular (email)
command to a list has failed?
I have a user (a SINGLE user, so far as I know) who cannot get the list of
members by using the 'who ' command. He successfully gets his
password with the 'password' command, but the 'who' c
