On Thu, 29 May 2014 22:30:25 +0900 "Stephen J. Turnbull" <step...@xemacs.org> wrote:
> > > 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 you want to create one? [y/n]" > > I'm not sure I like this approach. Creating a domain should be a > heavyweight operation, and eventually should include a bunch of sanity > checks, like existence of domains and MX records. I have visions > (nightmares) of users coming to us saying > > User: I said yes, but mail never arrives. > Dev: .... Oh, is there a proper entry in the DNS? > User: Doesn't Mailman create the domain? I agree to your point that it should be a heavyweight operation, I guess i was not able to express myself. I don't know if this CLI client can add domains to mailman(I mean add domain to mailman before and not *create*), there could be a prompt saying "This mailman installation is not configured to use this domain, do you want to do it now?" and then maybe it will walk the user through the "usual" process of adding a new domain? > > > > Or maybe it could schedule a deletion after a pre-defined time with a > > > reasonable default lets say "1 Day"? And for an urgency(to delete) there > > > could be --force argument? > > Deleting a list should be immediate, but I agree it should be confirmed. > -- thanks, Abhilash Raj _______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
