Hi Barry,
Although I haven't had time to go through the code, I'm liking what I'm
seeing
here on the mailing list. Just a quick comment.
[...]
Ideally, because this is a command line tool aimed and users, there should
be
a manpage for mmclient. Fortunately, it's *really* easy to write
Rajeev S writes:
Also maybe you can try making your tool a little more smart? Like lets
say I try to create a list abhil...@raj.com and there is no domain
raj.com in the database, so instead of just showing error maybe you can
ask the user:
The domain raj.com does not exist, Do
* Stephen J. Turnbull step...@xemacs.org:
Rajeev S writes:
Also maybe you can try making your tool a little more smart? Like lets
say I try to create a list abhil...@raj.com and there is no domain
raj.com in the database, so instead of just showing error maybe you can
ask the
On May 29, 2014, at 05:20 PM, Patrick Ben Koetter wrote:
Deleting a list/domain requires an (internal) scheduler. Does Mailman have
one? A broom job that can be called via cron?
Sort of, but the way these are handled currently are individual scripts that
each have to be added to cron.
... and
Patrick Ben Koetter writes:
I doubt anyone that igorant of e-mail and how it works will ever
make it to the MM3 command line client, but yes, such cases do
exist.
I think they're actually likely to be reasonably common.
However I think the use case prepare Mailman to handle mail for a
On May 30, 2014, at 03:41 AM, Stephen J. Turnbull wrote:
Probably scripts should not be using commands that need multiple
confirmations, though.
Agreed!
-Barry
___
Mailman-Developers mailing list
Mailman-Developers@python.org
* Stephen J. Turnbull step...@xemacs.org:
Patrick Ben Koetter writes:
I doubt anyone that igorant of e-mail and how it works will ever
make it to the MM3 command line client, but yes, such cases do
exist.
I think they're actually likely to be reasonably common.
However I think
