If he can't get that to work, perhaps you could schedule a script to run it
yourself and email him the results, say once a week.
Peter Shute
Sent from my iPad
On 22 Jan 2015, at 3:42 am, Mark Sapiro m...@msapiro.net wrote:
And, you could send him an email with a
On 01/21/2015 06:25 AM, Gary Merrill wrote:
Finally, let's consider The problem here is we don't anticipate a third
party acting at a distance and unable to get reliable information from his
user. Why not? This seems quite a reasonable scenario to anticipate.
Users are notoriously
Gary Merrill wrote:
Now you might argue that Mailman was never intended to be
deployed in such a lame support environment. That is almost
It sounds like a fairly typical mailman support environment.
certainly true. But it's ALMOST good enough to stand on its
own feet in this
On 01/21/2015 08:42 AM, Mark Sapiro wrote:
And, you could send him an email with a
mailto:LISTNAME-request@...?subject=who%20PASSWORD link in it hand
have him just click that and send.
I assume you can find his password with something like
bin/dumpdb lists/LISTNAME/config.pck | grep his
On 01/21/2015 07:44 PM, Gary Merrill wrote:
I do appreciate your efforts to help, but you should realize that some of
them are based on assumptions that simply don't hold in this case --
although they pretty universally held when Mailman was originally written,
and for some time afterward.
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
Gary Merrill wrote:
Now you might argue that Mailman was never intended to be
deployed in such a lame support environment. That is almost
It sounds like a fairly typical mailman support environment.
certainly true. But it's ALMOST good enough to stand on its
own feet in this
Well, let's think about this ...
It's NOT true that The user who sends an email command is provided with a
response that tells him what's wrong. The example in question is where a
valid user sends (from his registered address) the command 'who PASSWORD'
but employs the wrong password or mistypes
