DirectAdmin Docs
Search K

Appearance

Version 1.26.2 ​

Released: 2006-01-20

Option to hide outlook button in pop list new ​

hide_outlook=0

in the directadmin.conf will be the default. (won't exist, but will be the default anyway).

To hide the outlook reg file link, set it to:

hide_outlook=1

and restart DA.

TXT records in DNS (SKINS) new ​

TXT records in dns.

will be a new dns_txt.conf file for txt records.

named.db will not have the spf record.. will be in the dns_txt.conf file.

Info to come.

Also, add full NS control instead of just for the domain (eg, sub.domain.com. in NS ns1.domain.com.)

admin/dns_admin_control.html

change:

html
<td class=list><input type=hidden name=value value='|DOMAIN|.' >|DOMAIN|.</td>

to:

html
<td class=list><input type=text name=value value='|DOMAIN|.' ></td>

add:

html
<form action='/CMD_DNS_ADMIN' method='POST'>
<input type=hidden name=action value=add>
<input type=hidden name=domain value="|DOMAIN|">
<input type=hidden name=type value="TXT">
<tr><td class=list><input type=text name=name value="|DOMAIN|."></td><td class=list align=center>TXT</td><td class=list><input type=text name=value size=26 ></td>
<td class=list align=center><input type=submit name=add value="Add" ></td></tr>
</form>

user/dns_control.html

add:

html
<form action='/CMD_DNS_CONTROL' method='POST'>
<input type=hidden name=action value=add>
<input type=hidden name=domain value="|domain|">
<input type=hidden name=ptr_val value="|ptr_val|">
<input type=hidden name=type value="TXT">
<tr><td class=list><input type=text name=name |DNS_DISABLED|></td><td class=list align=center>TXT</td><td class=list><input type=text name=value size=26 |DNS_DISABLED|></td>
<td class=list align=center><input type=submit name=add value="Add" |DNS_DISABLED|></td></tr>
</form>

change:

html
<td class=list><input type=hidden name=value value='|DOMAIN|.' |DNS_DISABLED|>|DOMAIN|.</td>

to:

html
<td class=list><input type=text name=value value='|DOMAIN|.' |DNS_DISABLED|></td>

--config=/path/to/directadmin.conf new ​

directadmin and dataskq flags for adding a custom config file.

Sample usage:

./directadmin --config=/usr/local/directadmin/conf/directadmin.conf.new d

Note, this flag is not intended for usage other than for the DA, running as a deamon. (don't run it with the installer, ./directadmin i).

The order of flags will make a difference.

Eg, if you run:

./directadmin c --config=file.txt

vs

./directadmin --config=file.txt c

it might give you 2 different outputs, as 'c' before --config will dump out the data when the 'c' is found, before --config is checked.

Sample dataskq usage:

bash
./dataskq --config=file.txt
./dataskq d --config=file.txt
./dataskq --config=file.txt

The order with the dataskq does not matter because flags are all processed before anything is run.

new global tokens new ​

RESELLERAFTP
RESELLERCGI
RESELLERPHP
RESELLERSSL
RESELLERDNSCONTROL
RESELLERUSERSSH
USERCGI
USERPHP
USERSSH

value is ON or OFF for them.

This allows for

|*if RESELLERSSL="ON"|
show something
|*endif|

type statements in the html skins (eg, in the "modify user","modify user package", or "create custom user" skin to hide the options if the Reseller does not have access to them)

USEREMAILQUOTA   in bytes.
USEREMAILQUOTAMEG in Meg
USEREMAILQUOTAGIG in Gig
USERDBQUOTA in bytes
USERDBQUOTAMEG in Meg
USERDBQUOTAGIG in Gig

nameservers:

USERNS1
USERNS2

spamd template changes for 3.x fix ​

https://forum.directadmin.com/posts/63294

2 new TOKENS to the user_prefs template:

VERSION - not used, but hold the SA version, eg, "3.1.0"

VERSION3=yes or no. "yes" if you have 3.x.x

New template looks like:

|?RW_HEADER_SUB=rewrite_header subject \`subject_tag\`|
|*if subject_tag=""|
|?RW_HEADER_SUB=|
|*endif|

|*if VERSION3="yes"|
required_score |required_hits|
|RW_HEADER_SUB|
|*else|

required_hits   |required_hits|
rewrite_subject |rewrite_subject|
subject_tag     |subject_tag|

|*endif|

report_safe     |report_safe|

|blacklist_from|
|whitelist_from|

Email disk usage totals for dovecot fix ​

wu-imap saved everything as root, so DA always assumed that it was not in the quotas, and always counted the files owned by root in the ~/imap directory.

With dovecot, files are all owned by the user, so none need to be counted.

DA was still checking for the root files, which no longer existed, thus the email totals showed 0. The system quotas are counting the emails though, it's just a cosmetic issue.

Fix will count the non-root files in the imap directory if dovecot is being used. It won't be added to the total disk usage as the system quotas have that taken care of already. It will just fix the email usage total.

dovecot new user directory has 750 instead of 770 fix ​

If you create a new pop account with spam turned ON, DA will create the full path to the user for the spambox, eg: /home/username/imap/domain.com/user/Maildir.

The bug happened as a result of the mkdir(path,mode) function. The correct mode was being passed to the function S_IRWXU | S_IRWXG (770), but it was creating the driectories with 750, likely due to the umask (mkdir uses 'mode & ~umask & 0777'). So the fix is to run a chmod after each mkdir so as to not trust the mkdir function for setting the correct mode.

subdomain bandwidth uses non-ordered webalizer.hist fix ​

Sample webalizer.hist entry:

3 2004 15 0 1 5000 1 1 15 1
5 2005 1 1 1 0 22 22 1 1
6 2005 10 1 1 0 14 14 10 1
12 2004 6 0 1 10000 9 9 6 1

note, the time entries are not in chronological order.

It was previously assumed the last entry was the most recent.

Fix requires a lot of parsing and finding the highest date.

IP adding, range feature: more checking fix ​

To address this issue:

https://forum.directadmin.com/posts/65344

The feature listed here:

Ability to create symlink from private_html to public_html (SKINS)

will create a symbolic link from the private_html to the public_html directory.

DA tries to chown the link to the user, so the usre can delete if needed. The problem was when you chown a symbolic link, you're not chowning the link, but rather what the link points to. This cause the ownership of the public_html to change.

If you were using apache_public_html=1, then the public_html would go from user:user, chmod 750, to user:user 750 giving the public_html a forbidden error (apache can't read inside it).

The fix was to simply not chown the link as creating the link as the correct user will accomplish the same thing.

ftp bandwidth only on users IP fix ​

ftp bandwidth for a user is only tallied for the IP the user is using.

Fix will check all shared IPs for bandwidth.