changes I would like

Chrysalis

Verified User
Joined
Aug 25, 2004
Messages
1,340
Location
uk
Hi

Ok here is a list of minor changes I think would be nice in minor revision of directadmin.

1)crontab feature on/off for user settable by admin.
2)dns record entry add on/off settable by admin (would allow to add accounts without domains and duplicate accounts for 1 domain, as well as adding accounts when slave domain already exists).
3)spamassasin feature enabled but default set to allow all email as normal.
4)system backup changes, add /etc /usr/local/etc and /usr/local/directadmin to default dir list and on freebsd boxes replace /home with /usr/home.
5)make directadmin recognise bind9 is installed (it thinks bind9 is bind8)

thanks and keep up the good work
 
Chrysalis said:
3)spamassasin feature enabled but default set to allow all email as normal.
I'm not sure what you mean. If SpamAssassin is set to allow all email through, why should it be enabled at all?

Do you mean it should mark the spam but not do anything with it? That's what SpamAssassin on my servers does now.
4)system backup changes, add /etc /usr/local/etc and /usr/local/directadmin to default dir list and on freebsd boxes replace /home with /usr/home.
You might want to backup /etc, /usr/local/etc, and /usr/local/directadmin, but you certainly don't want to just restore them; there's lots of ways restoring them could break a newly configured server. And you probably don't want to backup up either /home or /usr/home as one monolithic backup either; our rewrite will backup user directories under /home, but not /home itself.

(Why? Well among other reasons, so our backup won't backup the /home/backup directory.)

Jeff
 
also a moajordomo bug explained here.

http://www.directadmin.com/forum/showthread.php?s=&threadid=5366

jlasman to answer your points.

As I see it now, spamassasin can be either enabled for the user as a feature but by default is enabled meaning until the user discovers it in their user panel it will be marking emails as spam, or it can be disabled removing the feature for the user. I would like the feature abailable for the user but default to disabled.

concerning the backups, DA gives the impression a system backup is been done, its been discovered this is far from the case. I am asking for the interface to make sure a full backup is been done, I am not suggesting the files backed up are blindly restored. (isn't it better to back up too many files rather then not enough) On a FreeBSD server by default DA backs up NO home dir's.
 
Back
Top