Directadmin 1.39.2 - Release Candidate 1

DirectAdmin Support

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

DirectAdmin 1.39.2 release candidate 1 is now ready for testing.
This is primarily a minor bugfix release, but there are a few minor new features as well.

The full list of changes can be found here:
http://www.directadmin.com/versions.php?version=1.392000

1) The main bug fix relates to the brute force failed login attempt log not clearing old values, as well as major efficiency optimizations (so the dataskq doesn't go crazy):
http://www.directadmin.com/features.php?id=1243

2) It's also important to note that the new internal default for the brute force monitor is disabled by default, due to many requests. If you've already saved your "Admin Settings", then the value you've set will be in your directadmin.conf. If you did not make any changes to your Admin Settings, then the BFM may turn off, to revert to the default state. After updating, ensure it's set how you want it by checking your Admin Settings.

3) Handy feature: Ability to suspend just one email account.

4) Ability to change the default apache ports from 80/443, to something else. Very useful for anyone trying to run nginx/lighttpd at the same time as apache.

John
 
Last minute additions, so I'll push the release to tomorrow (30th):

Very handy new feature (limited testing so far). Requires new exim.pl.
Per-Email send limit to put a cap on smtp-auth sending.
http://directadmin.com/features.php?id=1246

Minor logic change for writing user httpd.conf files:
http://directadmin.com/features.php?id=1247

valign=top for "Show All Users" Cells, so accounts with hundreds of domains on them have the username/data visible, and not several pages down:
http://directadmin.com/features.php?id=1248

As usual, these are already in the pre-release binaries for anyone who'd like to try them now.

John
 
Very cool release. This will allow us to suspend problematic email accounts without pissing off the customer by suspending the entire domain. I don't think any other panel allows this.

Thumbs up for DA!
 
There is a bug - redirect_virtual_host.conf still has :80 not |PORT_80|
 
Thanks. I've updated the code and re-uploading the binaries now (allow about an hour from the time of this post). If you need the redirect_virtual_host.conf, and have downloaded the 1.39.2 in the window from yesterday until the time the new binaries are updated, just update manually to grab the fresh version.

John
 
Ive not read anything about redirect_virtual_host.conf yet but i think that the way you linked would still be valid. Am i wrong?
 
It only breaks something with the hardcoded :80 in the template if you're trying to tell apache to use some other port, eg: port 81 (in which case you'd need to edit the template, which is still a minor event). There was just a short period of time where the 1.39.2 release had :80 instead of :|PORT_80|.. but was not significant enough to make a whole new version for the small change. It should be fine now.

John
 
ok, ive added |PORT_80| and |PORT_443| in mine custom templates for webmail.domain feature.

Ive also added the variables in directadmin.conf (not necessary needed but i want to be sure).

Now, for a test, how i should rewrite httpd confs? I know there is an echo for dataskq but i cant remember it now :)

Im gonna search on forum hoping to find it :)

Regards
 
FYI:

Code:
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq d800

By the way, John does you have any time for email_modify_post.sh and/or user_data_modify_post.sh ? Would be very appreciated.

Also, what about my idea on creating mysql main user on user creation for bypass the mysql user main pass to be different from user account (and changed ofc)?

Thanks for your good work, as always :)

Regards
 
FYI:

Code:
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq d800

By the way, John does you have any time for email_modify_post.sh and/or user_data_modify_post.sh ? Would be very appreciated.

Also, what about my idea on creating mysql main user on user creation for bypass the mysql user main pass to be different from user account (and changed ofc)?

Thanks for your good work, as always :)

Regards

If you change port you must rewrite IPs also:
#!/bin/bash
echo "action=rewrite&value=httpd" >> /usr/local/directadmin/data/task.queue
echo "action=rewrite&value=ips" >> /usr/local/directadmin/data/task.queue
/usr/local/directadmin/dataskq d400
 
Thats a strange name for a variable...should of just named it http_port and https_port or something :p
 
Back
Top