FreeBSD Installation notes for DirectAdmin
If logging in as a user other than admin or root (using su to gain root access)
You have to add “AllowUsers username” to /etc/ssh/sshd_config before you can log out from root or you’ll lose root on the server forever, and you’ll have to format.
Hint: Use “fetch” instead of “wget” on FreeBSD systems to download the install file.
Tags: DirectAdmin Support, FreeBSD, Installation
Make sure you do not install services such as Apache, PHP, MySQL, Ftp, Sendmail, etc., as this is done by DirectAdmin. All that is needed is a CLEAN install of the operating system.
DirectAdmin Control Panel Software
Apache 1.3, 2.0, 2.2 Web Server
FrontPage 5.0.2.2510 Microsoft FrontPage⢠Extensions (apache 1.3 only)
Php 4.4 and/or 5.2 Php Scripting Language (CLI, or suPhp(cgi))
PhpMyAdmin MySQL Database Manager
MySQL 4.1/5.0 MySQL Databases
Exim 4 Exim Mail Manager
Majordomo 1.94.5 Majordomo Mailing List Manager
vm-pop3d 1.1.7f POP3 Mail Manager
WU-IMAP Imap daemon (with virtual pop modifications)
Dovecot Install option to replace vm-pop3d/wu-imapd. Uses Maildir instead of mbox
Proftpd 1.3 FTP Server
Tags: DirectAdmin Support, installed, Software
Enable SpamAssassin on your DirectAdmin server
To enable Spamassassin on your server, you need to first need to install it. Once installed a few minor changes are needed in your /etc/exim.conf file.
1) Install spamd and spamc:
cd /usr/local/directadmin/scripts
./spam.sh
2) Start the spamd
/usr/bin/spamd -d -c -m 15
Source : http://directadmin.com
Tags: DirectAdmin Support, enable, server, SpamAssassin
How to update your exim.conf in DirectAdmin
You can update your exim.conf by running the following as root:
wget -O /etc/exim.conf http://files.directadmin.com/services/exim.conf
wget -O /etc/exim.pl http://files.directadmin.com/services/exim.pl
chmod 755 /etc/exim.pl
cd /etc/virtual
touch blacklist_domains whitelist_from use_rbl_domains bad_sender_hosts blacklist_senders whitelist_domains whitelist_hosts whitelist_senders
echo 0 > limit
mkdir usage
chown mail:mail blacklist_domains whitelist_from use_rbl_domains bad_sender_hosts blacklist_senders whitelist_domains whitelist_hosts whitelist_senders limit usage
If you are running dovecot, you will need to re-patch your exim.conf:
patch -p0 < /usr/local/directadmin/customapache/exim.conf.dovecot.patch
patch -p0 < /usr/local/directadmin/custombuild/exim.conf.dovecot.patch
Then restart exim:
RedHat:
/sbin/service exim restart
Tags: DirectAdmin Support, exim.conf, Update
Simple Rules to follow to setup a Mail System
Hostname must not match any domain that is being used on the system. Example, if you have a domain called domain.com and you want to recieve mail on user@domain.com, you must *not* set your hostname to domain.com. We recommend using server.domain.com instead. You must make sure that you add the A record for server.domain.com so that it resolves.
For DirectAdmin
- The hostname must be in the /etc/virtual/domains file.
- The hostname must *not* be in the /etc/virtual/domainowners file.
- The hostname must resolve. If not, add the required A records to the dns zone such that it does.
- The directory /etc/virtual/hostname must exist.. (eg: /etc/virtual/server.domain.com). It must not contain any files
- Any domains that you want to use for email (eg: domain.com) must be in both the /etc/virtual/domains file and the /etc/virtual/domainowners file. The directory /etc/virtual/domain.com must exist and the files /etc/virtual/domain.com/passwd and /etc/virtual/domain.com/aliases exist.
- File permissions for virtual pop inboxes should be (not applicable with Dovecot/Maildir):
/var/spool/virtual/domain.com 770 username:mail
/var/spool/virtual/domain.com/* 660 username:mail
- Make sure that your main server IP has a reverse lookup on it.
Tags: DirectAdmin Support, mail, Setup, System