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 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?
> > 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.
_______________________________________________
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
