DirectAdmin 1.44.0 has been released

DirectAdmin Support

DirectAdmin Support

Administrator
Staff member
Joined
Feb 27, 2003
Messages
9,158
Hello,

DirectAdmin 1.44.0 has been released:
http://www.directadmin.com/versions.php?version=1.440000

This is a major release, with many new features and fixes.

Some major new features:
- Inodes, to limit the number of files per User: http://www.directadmin.com/features.php?id=1445
- SPF dns records (disabled by default, requires named suppors them): http://www.directadmin.com/features.php?id=1477
- MX records for subdomains within the same zone: http://www.directadmin.com/features.php?id=1497
- php mail() log to better track sends from php: http://www.directadmin.com/features.php?id=1498
- Ability to create a User without caring which IP they're assigned to (API): http://www.directadmin.com/features.php?id=1500
- Full API output for email data: http://www.directadmin.com/features.php?id=1505
- Ability to automatically set multiple access_host values for new databases: http://www.directadmin.com/features.php?id=1507
- exim.pl version 14, requires manual update: http://directadmin.com/features.php?id=1491

Other changes:
- Major changes to the backup system to improve security: http://www.directadmin.com/features.php?id=1481

Plus many bug fixes.

Also, these are not new, but some many not know they exist:
- Per-Email daily limits (instead of just per-DA User): http://help.directadmin.com/item.php?id=514 (use exim.pl VERSION=14 or newer)
- Login Security Questions, extra layer of security: http://www.directadmin.com/features.php?id=1439

John
 
It's a feature that was added a while back, but disabled by default.
If you turn it on:
Code: 
echo 50 > /etc/virtual/user_limit
echo "user_can_set_email_limit=1" >> /usr/local/directadmin/conf/directadmin.conf
/etc/init.d/directadmin restart
then then Users can set limits for each E-Mail account they've created at:
User Leve -> E-Mail Accounts

This prevents run-away Users (eg: if their password is stolen) from sending too much spam, so they won't affect other E-Mail accounts under that domain.
Note, the above example set a global default of 50 emails per day, per E-Mail account.

So, for example, if:
/etc/virtual/limit is set to 100
/etc/virtual/user_limit is set to 50

then:
- DA User fred has a domain, and created an email account: [email protected]
- [email protected] can send a maximum of 50 emails per day.
- fred can change the number of emails bob@ can send by going to User Level -> E-Mail Accounts
- Once bob@ sends 50 emails, he cannot send anymore, but because DA User fred has a limit of 100, other E-Mail accounts (eg: [email protected]), can continue to send, up until the total of bob@ and gary@ (etc..) reach 100.


If fred wants to give bob@ a limit of 80 emails per day, then the directadmin.conf option would need to be changed:
max_per_email_send_limit=80
Where the the default internal setting is -1, and will use the number from /etc/virtual/user_limit as the max.
The max_per_email_send_limit is an override to the user_limit.
Do not use 0 here.. (it is an option for "unlimited"). If you need to, just set a higher number than you think you might need.

The per-DA-User limit (/etc/virual/limit) is always enforced, regardless of the per-Email limit.
The wording choice of /etc/virtual/user_limit is probably confusing. In hindsight, should have used /etc/virtual/email_limit, but too late now.

John
 
Excellent! This is exactly what I wanted.
Is it possible do it through API? Because I have registration form where users make free account by them selv, i use PHP and API.
 
Yes, you'd do it at the same place you create the account (eg: similar to setting the quotas), and changing the account.
You can see samples by running DA in debug mode (b2000) with the "|grep string" option, and create/set an account through the browser.
Use the same variables with the API.
http://help.directadmin.com/item.php?id=293

John
 
upgraded to 1.44 and restarting any services in the DA got error:

An error has occurred

/sbin/service httpd restart 2>&1


An error has occurred

/sbin/service proftpd restart 2>&1
 
Installed on two Centos systems, along with latest php and apache and now neither httpd will start (first logged the issue here http://forum.directadmin.com/showthread.php?t=47438, following report from a Centos user. Forgive me for cross posting, just warning centos users that maybe there is a problem with the upgrade).

One server is CentOS release 6.4. Other is release 5.9.

6.4 reports
AH00526: Syntax error on line 3 of /etc/httpd/conf/extra/httpd-fastcgi.conf:
FastCgiIpcDir /var/run/fastcgi: access for server (uid -1, gid -1) failed: write not allowed

5.9 reports
AH00526: Syntax error on line 3 of /etc/httpd/conf/extra/httpd-fastcgi.conf:
FastCgiIpcDir /var/run/fastcgi: access for server (uid 4294967295, gid 4294967295) failed: write not allowed

Thank you.


Jonathan
 
Peter Laws said:
Which templates/confs are rewritten for this?
Click to expand...

All of the following templates in /usr/local/directadmin/data/templates have the changes related to mail() logging:
Code: 
virtual_host2.conf
virtual_host2_secure.conf
virtual_host2_secure_sub.conf
virtual_host2_sub.conf
php-fpm.conf
user_virtual_host.conf

NOTE: Apache 1.x templates do not have the mail() logging functionality added (virtual_host.conf, virtual_host_*.conf)
 
Last edited:
Do you mean contents of /usr/local/directadmin/data/templates?

All the following show new dates...

user_virtual_host.conf
virtual_host2.conf
virtual_host2_secure.conf
virtual_host2_secure_sub.conf
virtual_host2_sub.conf
virtual_host.conf
virtual_host_secure.conf
virtual_host_secure_sub.conf
virtual_host_sub.conf

Is that what you meant?
 
I've updated my post, it probably answers your question about Apache 1.x templates and the path of templates :) Thank you.
 
jonathanc said:
Installed on two Centos systems, along with latest php and apache and now neither httpd will start (first logged the issue here http://forum.directadmin.com/showthread.php?t=47438, following report from a Centos user. Forgive me for cross posting, just warning centos users that maybe there is a problem with the upgrade).

One server is CentOS release 6.4. Other is release 5.9.

6.4 reports
AH00526: Syntax error on line 3 of /etc/httpd/conf/extra/httpd-fastcgi.conf:
FastCgiIpcDir /var/run/fastcgi: access for server (uid -1, gid -1) failed: write not allowed

5.9 reports
AH00526: Syntax error on line 3 of /etc/httpd/conf/extra/httpd-fastcgi.conf:
FastCgiIpcDir /var/run/fastcgi: access for server (uid 4294967295, gid 4294967295) failed: write not allowed

Thank you.


Jonathan
Click to expand...

The issue seems not to be related to the upgrade. Usually it means that you have custom apache configuration files placed in /usr/local/directadmin/custombuild/custom that create the problem. More information can be found here: http://forum.directadmin.com/showthread.php?t=47438&p=243483#post243483
 
DirectAdmin Support said:
[..]
- SPF dns records (disabled by default, requires named suppors them): http://www.directadmin.com/features.php?id=1477 [..]
Click to expand...

Regarding the quoted new feature. I am running CentOS 6.4 64bit, on 4 servers with DirectAdmin multiserver setup.

Many of my customers have added a custom spf txt record (customized for GoogleApps/Gmail). If I add dns_spf=1 and restart DirectAdmin, will automatically all existing spf txt records be converted to the new format? If not, how can I convert existing domains? And also, if existing spf txt records is converted automatically, will customers with custom spf txt records loose the customization of the spf record?

Will the new spf dns records be default in the future, and is it any reason I should convert existing domains to this new format? Thanks.
 
Last edited:
@ditto: It will be default if we can find a good bind command to determine if SPF records are supported in the current version of named or not. If anyone knows of one, let us know. Most currently running versions named don't actually support it (usually slightly older boxes)

@steamservice: That's entirely possible. I didn't test that option, so not 100% sure, but looking at the code, I don't see why not.

John
 
Just for clarification regarding max_per_email_send_limit, to make sure I'm interpreting it correctly:

limit set to 1000
user_limit set to 150
max_per_email_send_limit set to 500

With this setup, it should mean that e-mails are limited to 150 by default but can be set up to 500 if need be and then the default user limit is 1000. Is this correct? If so, I seem to keep getting errors that I cannot set an e-mail above user_limit, despite max_per_email_send_limit=500 being in place and having restarted DA.
 
You must log in or register to reply here.
Back
Top