A qmail system is made up of several different programs, all running at the same time and doing their own little part of the overall "mail server" job. Each of these programs generally has its own log file, although if you are using syslog, the logs may be combined together. By understanding what each program does, you can easily tell which log file to look at when you need to check something.
The qmail-send program (which normally runs as a daemontools service called "qmail-send", or maybe just "qmail") manages the queue, and starts all delivery processes. The delivery programs run as children of qmail-queue, and therefore their output is contained with the qmail-queue output. If you have a problem with messages being "stuck" in the queue, this log file should be the place to look.
The qmail-smtpd program handles incoming SMTP traffic. If you have a problem with messages not being properly accepted or rejected from other machines, this log file should be the first place to look. Note that if you have multiple SMTP services on the machine (for example, a standard SMTP service on port 25, an SSL-enabled service on port 465, and an AUTH-only service on port 587) each service will have its own log file (again, unless they are being combined by the syslog mechanism.)
If you are using qmail-scanner as a way to have your incoming mail scanned for viruses and/or spam content, the qmail-scanner program also generates a log file of its own, which is totally separate from the qmail-smtpd log. You will find this file in your qmail-scanner directory, with the name qmail-queue.log. This will have a line-by-line description of everything the qmail-scanner program does.
If you are using simscan as a way to have your incoming mail scanned for viruses and/or spam content, you will normally find simscan’s logs in the qmail-smtpd service log.
If you are using clamav, the "clamd" program keeps its own log file. The /etc/clamd.conf file should have a "LogFile" line which tells you where the log is being written.
If you are using spamassassin, its "spamd" program also generates logs. By default it sends the logs to the syslog with the "mail" facility code, but by adding a "-s" option to spamd’s command line it is possible to send the log output to a file, or to the "standard error" channel (which makes it easy to run spamd under daemontools.) You should examine the command line for spamd in order to figure out where its log file will be found.
Any POP3 or IMAP servers will also be generating their own log entries. If you or your users are having a problem with POP3 or IMAP, those would be the place to look.
NicTool is a free DNS management suite that takes all the headaches out of managing DNS. It includes an attractive web interface for users, admins, and clients to access and update their DNS zone data as well as a rich API for provisioning systems to interact with. All zone data is stored in MySQL and is extracted by export scripts to the DNS server of choice (tinydns, BIND, PowerDNS).
Updates are all parsed for validity before being accepted. All changes are logged and it’s easy to determine who made any given change, and when. Permissions are extremely granular. You can delegate permission for a zone to another user, or group of users. You can even delegate only specific zone records to other users or groups. You can grant others permission to publish to your DNS servers, but not the ability to alter them.
NicTool is the holy grail of DNS management packages. It works great for managing one zone, or a million of them.
System Requirement
– apache
– mod_perl
– perl modules
– DNS (TinyDNS or BIND)
Installation
There will be 2 part of NIctool that we need to install NictoolServer and NictoolClient, please go to http://nictool.com/download/ , register and download the free option.
Let’s start install the perl module through CPAN
# perl -MCPAN -e shell
cpan> install LWP
cpan> install RPC::XML
cpan> install SOAP::Lite
cpan> install DBI
cpan> install DBD::mysql
cpan> install Apache2::SOAP
Download the Nictool sources on http://www.nictool.com/download/ , register and download it
1. unzip the package
# tar -zxvf NicTool-2.07.tgz
there will be 2 packet the nictool client and nictoolserver
– NicToolServer-2.07.tar.gz
– NicToolClient-2.07.tar.gz
Install the NicToolClient
2. unzip the NictoolClient package
# tar -zxvf NicToolClient-2.07.tar.gz
3. go to NicToolClient-2.07 folder and install the perl modules
# cd NicToolClient-2.0
# perl Makefile.PL
Checking if your kit is complete…
Looks good
Writing Makefile for NicToolClient
common error :
#perl Makefile.PL
WARNING: LICENSE is not a known parameter.
Checking if your kit is complete…
Looks good
Warning: prerequisite RPC::XML 1 not found.
Warning: prerequisite SOAP::Lite 0 not found.
‘LICENSE’ is not a known MakeMaker parameter name.
Writing Makefile for NicToolClient
the error means that we need to instal perl module RPC::XML and SOAP::Lite
changes $NicToolClient::app_dir = into your httpd virtual directory path , in my case it is
BEGIN {
$NicToolClient::app_dir = ‘/home/line.com/public_html/NicToolClient’;
7. Restart the Apache
# service httpd restart
Install the NicToolServer
1.Unzip the NicToolServer package that we have already download
# tar zxvf NicToolServer-2.07.tar.gz
2. Install dependencies
NicTool requires that Apache and mod_perl be installed. There’s a brief which Apache discussion here.
cd NicToolServer-2.07
perl Makefile.PL
make deps
The ‘make deps’ target will install the required perl modules via ports on FreeBSD/Darwin and via CPAN on everything else. If ports are unavailable, CPAN is used.
3.Install the perl modules:
#make install clean
4.Move the distribution to your own httpd virtual domain ( in my case it is on /home/line.com/public_html/ ) and rename it to NicToolServer
