Search results

Normally we assume the customer knows what they are doing. However 99% of the time this is not the case :-). The auto responder system should enforce the following: when adding [email protected] as the autoresponder address, do NOT allow the customer to set [email protected] to be the CC address for...

As the name suggests. At admin and reseller level have a button when viewing a users account to "reset the domain". this resetting would basically verify all aspects of their account is in order and fix things that are broken. e.g. if a customer accidentally deletes their domains folder, it...

Hi Guys, This may catch people out so I think it's an additional but necessary step to put into the DA restore procedure. A warning should be displayed if you are restoring a user onto a server and the same username exists already. Just a warning where the admin/reseller can click "OK" to...

Hi there, Due to new legislation in Europe data retention is not going to go away for us HSP/ISPs that are based in Europe. We've very few options here, so we're going to have to look at keeping logs for upto 24 months as per the directives that the legislation contains. I'm wondering could DA...

Hi there, Currently da checks the named.conf file to decide weather or not a domain is on the system already or not. I think this check is no where near complete enough. I believe a central file in /usr/local/directadmin/data/admin/ would be better suited. Reasons: 1) We for 1 don't use DA...