>>While we're talking about name changes, we should change dbmail-adduser
>>to dbmail-users, or something along those lines. I'd also like to
replace >>the screwy arguments with a consistent getopt system.
I think this would be a good idea as well since it does more then just add
users. The improvement in argument handling would be tremendous for new
adaptors since dbmail-adduser gave me the most pain when I started with
dbmail. Thankfully, I have never touched that program now that I have my
script to interact with the db directly.
>> 1) dbmail-util (this is probably the most sensible replacement)
>> 2) dbmail-check
>> 3) dbmail-maint
>>I'm a fan of dbmail-check. It's a full word and it fully explains whatthe
>>program does (what exactly is maintenance? different things to different
>>people!). My second choice is dbmail-util. It's a good name, but I think
>>that we might want to use that name for something else, although I have
>>no idea what.
The only problem I see with dbmail-check is that dbmail-maint* also does
the two stage mail purge where it set the purge bit of deleted items and
then physically removing those with the purge bit set with another command.
It would be weird and unexpected for a "check" program to have these types
of functions.
Perhaps move the purge/delete features to its own "dbmai-clean" program?
This is would be the cleanest solution no pun intended.
Name changing suggestions summarized:
1) Change dbmail-adduser to dbmail-user
...because it does a lot more stuff then just add a user.
2) Change dbmail-maint* to dbmail-util or perhaps split the program into
two a) dbmail-check + b) dbmail-clean
...to remove the spelling issue and to improve the transparency of their
functions.
Xing
