Re: [Mailman-Users] Diagnosing command failures

Gary Merrill writes: > I know the kinds of problems you guys are facing -- although you > should be somewhat grateful that you aren't dealing with the FDA, > insurance companies, gigantic healthcare organizations, the CDC, > and multiple pharma companies. :-) I don't have to deal with them, b

Re: [Mailman-Users] Diagnosing command failures

On 1/22/2015 10:10 AM, Gary Merrill wrote: > 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

Re: [Mailman-Users] Diagnosing command failures

ext release. ___ Gary H. Merrill Chatham Design Consultants +1 919.271.7259 > -Original Message- > From: Stephen J. Turnbull [mailto:step...@xemacs.org] > Sent: Thursday, January 22, 2015 5:44 AM > To: Peter Shute > Cc: 'ghmerr...@chathamdesign.com'; &#x

Re: [Mailman-Users] Diagnosing command failures

Peter Shute writes: > A lot of people use the cPanel version and can't do anything > complicated for support. Even though this particular case is about > trying to help a difficult user to do something that's normally > straightforward that's probably pointless anyway, I hope v3 at > least gi

Re: [Mailman-Users] Diagnosing command failures

> 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

Re: [Mailman-Users] Diagnosing command failures

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 environ

Re: [Mailman-Users] Diagnosing command failures

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 afterwar

Re: [Mailman-Users] Diagnosing command failures

l Chatham Design Consultants +1 919.271.7259 > -Original Message- > From: Mailman-Users [mailto:mailman-users- > bounces+ghmerrill=chathamdesign@python.org] On Behalf Of Mark Sapiro > Sent: Wednesday, January 21, 2015 9:04 PM > To: mailman-users@python.org > Subject: Re: [M

Re: [Mailman-Users] Diagnosing command failures

On 01/21/2015 08:42 AM, Mark Sapiro wrote: > > And, you could send him an email with a > 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 |

Re: [Mailman-Users] Diagnosing command failures

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 wrote: > > And, you could send him an email with a >

Re: [Mailman-Users] Diagnosing command failures

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 un

Re: [Mailman-Users] Diagnosing command failures

h is going to be unlikely with him), there's not much I can do. But the simple change I've suggested in this one particular diagnostic response would allow me to help him remotely. ___ Gary H. Merrill Chatham Design Consultants +1 919.271.7259 > -Original Message- &g

Re: [Mailman-Users] Diagnosing command failures

Gary Merrill writes: > Personal consultation and observation appears to be the only > approach here that will be successful. If the security implications are acceptable (which I think they are), you can also provide the user with a precomposed URL that they can put in their bookmarks list, as M

Re: [Mailman-Users] Diagnosing command failures

On 01/20/2015 06:59 PM, Gary Merrill wrote: > I was really asking whether there is a way to diagnose command > failures in Mailman, and it's clear at this point that the answer is "No." > This isn't entirely unexpected, but I just wanted to check in case there > happened to be something that I'd mi

Re: [Mailman-Users] Diagnosing command failures

ch here that will be successful. ___ Gary H. Merrill Chatham Design Consultants +1 919.271.7259 > -Original Message- > From: Mailman-Users [mailto:mailman-users- > bounces+ghmerrill=chathamdesign@python.org] On Behalf Of Mark Sapiro > Sent: Monday, January 19,

Re: [Mailman-Users] Diagnosing command failures

On 01/19/2015 03:09 PM, Mark Sapiro wrote: > > I suggest the easiest thing is to direct him to the list info page at a > URL like http://example.com/mailman/listinfo/LISTNAME, enter his email > address and list password in the Address: and Password: boxes near the > bottom of the page and click th

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 and needs access to the mailing list. > Implementing a Mailman list had as its primary goals addressing the problems > involved in this user's

Re: [Mailman-Users] Diagnosing command failures

At Mon, 19 Jan 2015 10:10:32 -0500 ghmerr...@chathamdesign.com wrote: > > 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 '

Re: [Mailman-Users] Diagnosing command failures

259 > -Original Message- > From: Robert Heller [mailto:hel...@deepsoft.com] > Sent: Monday, January 19, 2015 11:10 AM > To: ghmerr...@chathamdesign.com > Cc: Mailman Users; Robert Heller > Subject: Re: [Mailman-Users] Diagnosing command failures > > At Mon, 19 Jan 2015 10:

[Mailman-Users] Diagnosing command failures

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