SEARCH
NEW RPMS
DIRECTORIES
ABOUT
FAQ
VARIOUS
BLOG
DONATE




YUM REPOSITORY

 
 

MAN page from Fedora 14 sendmailanalyzer-8.0-1.fc14.noarch.rpm

SENDMAILANALYZER

Section: User Contributed Perl Documentation (1)
Updated: 2011-08-08
Index 

NAME

SendmailAnalyzer - Sendmail/Postfix log analyzer 

DESCRIPTION

SendmailAnalyzer as is name suggest is a Sendmail log analyzer. It processmaillog files and generate dynamic statistics in HTML and graphical output.The reports are generated in real time so that it let you know at any momentwhat is going on your mail servers. It use time (hour, day, month and yearviews) and cross-linked navigation for easy use.

SendmailAnalyzer is easy to install and highly configurable to match the dozenof Sendmail possible configurations. It also support report for all the majormilter or sendmail filters like SpamAssassin, MailScanner, Clamav, etc.

Collected data are stored in flat files that are automatically archived ordelete to keep disk space. All reports before the current day are cached tosave system resources and are displayed in the 1 second into your browser.

SendmailAnalyzer can be run on a home dedicated mail server, on multipleenterprise mail servers and on ISP mail servers for free. His low resourcesusage allow SendmailAnalyzer appliance embedding. Since version 8.0 the cachingmechanism has a very low memory footprint as well as the reports views.

This is the most advanced and complete statistics tool dedicated tothe great Sendmail MTA. It's goal is not to support any kind of MTA orother log format but only being a full featured tool for Sendmail users andadministrators. If you're searching something more general take a look atSawMill, it's not so bad :-) 

POSTFIX SUPPORT

SendmailAnalyzer is a statistical dedicated tool for Sendmail and it is verygood in this task. As many people ask me to have such free tool for the PostfixMTA, Since release v7.0 SendmailAnalyzer now also support the Postfix mail.logstatistics report.

This is a work in progress and for now you may want to disable spam, virus andnotification menu link to limit the ``No record for this period'' screen.

Note that I don't run Postfix so I need your help to handle more statisticalreport. 

FEATURES

It reports all you ever wanted to know about email trafic on your network. 

Global Statistics

All the following reports also show statistics per bytes and averageof bytes per message.
*
Number of inbound messages.
*
Number of outbound messages.
*
Number of inbound spams.
*
Number of outbound spams.
*
Number of inbound virus.
*
Number of outbound virus.
*
Sendmail rejection rules flow.
*
Syserr flow (Sendmail error messages).
*
Sendmail DSN Flow (Delivery Status Notification)
*
The global MTA status allocation per messages, bytes and percentage.
*
Distributed messages coming from Internet.
*
Distributed messages sent internaly.
*
Distributed messages sent to Internet.
*
Distributed messages coming from and going to Internet.
*
Sendmail SMTP Auth statistics by type (server or client), mechanismi and user.

If you deliver marqued spam / virus to recipients, SendmailAnalyzerwill report the delivery flow for:

*
Spam / virus coming from Internet.
*
Spam / virus sent internaly.
*
Spam / virus sent to Internet.
*
Spam / virus coming from and going to Internet.

Note: In the report you will see 'local' inbound or outbound message, thatmean a mail coming from (sender relay) or going to (recipient relay) the mailserver. This is not the same that internal, which mean coming from or sent toyour internal network / private domain. 

Top Statistics

Once you have define in the configuration file the Top Max statistics to show(25 by default), the Max Recipient for a message (25 by default), the messageSize Max (5Mb by default) you will see the top statistics of:
*
Top sender domain, top sender relay, top sender address.
*
Top recipient domain, top recipient relay, top recipients address.
*
Top spams rules, top spammers domain, top spammers relays, top spammers address,top spam recipients address.
*
Top virus name, top virus sender, top virus sender relay, top virus recipientaddress, top infected filename.
*
Top DSN status, top DSN sender, top DSN Relay, top DSN recipient address.
*
Top rejection rules, top rejected domain, top rejected relay, top rejectedsender, top rejection status.
*
Top Sendmail Error messages.
*
Top max number of recipient for one message.
*
Top max size message with number of recipients and sender address.
*
Top Sendmail SMTP Auth mechanisms, relays and users (server or client).

Note: on daily view you can click on each of the reported element to see thedetailled informations. For example if you follow link on a sender relay youwill see all messages detailled information coming from that relay.This kind of navigation is only available for the days of the current monthto keep disk space, memory usage and privacy. 

ISP like feature

Begining at version 4.0 of SendmailAnalyzer some features could be relatedto an ISP like environment and allow statistics on very huge SMTP flow:
*
Support centralized maillog for multiple Sendmail serveurs througth rsyslog.
*
Support per domain reports with user access control.
*
Support per user reports. Each user can see is own statistics. (Removed in v5.0 until now)
*
Low memory usage, small disk space utilization and really speed with daily caching.
*
Support parsing of compressed maillog file.
 

Milter / Filter supported

SendmailAnalyzer support some of the most used milter and filter forspam and virus filtering. If you don't find yours drop me a line andit will be included.
*
MimeDefang Spam and Virus reports
*
Amavis Spam / Virus detection
*
Clamav virus detection
*
Jchkmail Spam / Virus report
*
MailScanner Spam / virus detection
*
SpamAssassin Spam detection (spamd output)
*
Sendmail DNSLB report (check_relay)
*
Sendmail DSN (Delivery Status Notification)
*
DNSLB-Milter Spam detection

If your one is not listed here and you can send me some relevantmaillog lines I can add his support in a day. 

New features

If you need new features and support for new/other milters or filters,let me know. This help a lot to develop a better/useful tool. Thispiece of software is widely use at my work (espacially for IT report)but this reflect only a part of the Sendmail usage. 

Internationalization

SendmailAnalyzer can be translated to any language with your contribution.At this time only 3 language are supported: French, English and Spanish.If you want to add your own language, it's really simple, take a look inthe cgi-bin/lang/ directory and send me the translation file. 

REQUIREMENT

SendmailAnalyzer can work in any platform where Sendmail and Perl could run.What you need is a modern Perl distribution 5.8.x or more is good but olderversion should also work.

You need the following Perl modules. If they are not yet include in yourOS distribution you can always find them at http://search.cpan.org/

        MIME::Base64;        MIME::QuotedPrint;        GD        GD::Graph        GD::TextUtil        GD::Graph::bars3d;

The graph output are generated using the libgd and libpng. You can get themat the following places:

        http://www.libgd.org/        http://www.libpng.org/
 

INSTALLATION

 

Generic install

Here is the generic installation steps, but if you want you can create andinstall your own distribution package, see ``Package install'' bellow.

1) Unpack the distribution tarball in the desired location as follow:

        tar xzf sendmailanalyzer-x.x.tar.gz        cd sendmailanalyzer-x.x/        perl Makefile.PL        make && make install

2) Follow the instruction given at the end of install. With this defaultinstall everything will be installed under /usr/local/sendmailanalyzer.

3) Edit sendmailanalyzer.conf file to customize your SendmailAnalyzer reports.See the configuration file and CONFIGURATION section bellow for usage. 

Package install

In the packaging/ directory you will find all scripts and file to generatebinary RPM, Slackware and Debian package. See README in this directory. 

Custom install

You can create your fully customized SendmailAnalyzer installation by usingthe Makefile.PL Perl script. Here is a sample:

        perl Makefile.PL \                LOGFILE=/var/log/maillog \                BINDIR=/usr/bin \                CONFDIR=/etc \                PIDDIR=/var/run \                BASEDIR=/var/lib/sendmailanalyzer \                HTMLDIR=/var/www/sendmailanalyzer \                MANDIR=/usr/man/man3 \                DOCDIR=/usr/share/doc/sendmailanalyzer

If you want to build a distro package, there are two other options that you mayuse. The QUIET option is to tell to Makefile.PL to not show the default postinstall README. The DESTDIR is to create and install all files in a packagebuild base directory. For example for Fedora RPM, thing may look like that:

        # Make Perl and SendmailAnalyzer distrib files        %{__perl} Makefile.PL \            INSTALLDIRS=vendor \            QUIET=1 \            LOGFILE=/var/log/maillog \            BINDIR=%{_bindir} \            CONFDIR=%{_sysconfdir} \            PIDDIR=%{rundir} \            BASEDIR=%{_localstatedir}/lib/%{uname} \            HTMLDIR=%{webdir} \            MANDIR=%{_mandir}/man3 \            DOCDIR=%{_docdir}/%{uname}-%{version} \            DESTDIR=%{buildroot} < /dev/null

See spec file in packaging/RPM for full RPM build script. 

USAGE

There's two way to use SendmailAnalyzer. If you don't need real time you can run it each night so that maillog will be parsed and reportsgenerated once a day. Note that if you have a huge MTA load this nota good solution.

The other way is to run it in daemon mode, in this way it can parse hugemaillog (million line per day) preserving system resources.

To know all possible command line arguments, run 'sendmailanalyzer --help'

Important: if you experience high memory usage with SendmailAnalyzeruse the -w (--write-delay) command line option to reduce the time where inmemory data are flushed to disk. Default is 60 secondes, this is good in mostconfiguration but in huge servers you may set it as low as 5 secondes.You must test it to find a compromise between speed and memory usage. 

Standalone

To run SendmailAnalyzer in standalone mode you have to setup a cronentry each night as follow assuming log and configuration files indefault place (/var/log/maillog and /usr/local/sendmailanalyzer/sendmailanalyzer.conf):

        /usr/local/sendmailanalyzer/sendmailanalyzer -i -b -f

This will run the program in interactive mode (-i), parse full maillog seekingafter the last run ending position (-f) and exiting at end of maillog parsing(-b). 

Daemon mode

To run SendmailAnalyzer as a daemon, use the start/stop/restart script givenwith the distribution (in start_script/ directory). The following script isfor Slackware but can be used with any other distribution:

        /etc/rc.d/rc.sendmailanalyzer start

or if you use RedHat or Fedora:

        chkconfig sendmailanalyzer on        service sendmailanalyzer start

It will start as 'sendmailanalyzer -f' that tell him to start in daemon mode(default), parse full maillog seeking after the last run ending position (-f)and to open a pipe to a tail command on /var/log/maillog. It will never enduntil you kill it.

Important: If you have syslog rotate enable (I hope so :-) you will have torestart SendmailAnalyzer after each log rotation to always tail the good filedescriptor.

Edit /etc/logrotate.d/syslog and add the following after syslog restart:

        /etc/rc.d/rc.sendmailanalyzer restart /dev/null 2>&1 || true

or on Redhat or Fedora

        /etc/init.d/sendmailanalyzer restart /dev/null 2>&1 || true

this must be in the postrotate section. 

Stopping SendmailAnalyzer

Just kill it with SIGTERM signal it will flush current collected objectto disk and free open files. Use 'kill -15 `cat /var/run/sendmailanalyzer.pid`'for that or use the starter script. This will kill the current sendmailanalyzerprocess and the pipe to the tail command. 

Caching

SendmailAnalyzer collect maillog entries to write datas to flat files,when you run the CGI script sa_report.cgi it had to read each data filesfor the given period to compute statistics and output HTML reports.This can be enought for day views but when you jump to month view itcost a lot in CPU and memory usage unless you have a home MTA.

To speed up things and free system resources you have to run the scriptsa_cache each night by cron to create cache files. After that viewinga month or year view take less than a second.

The script sa_cache must be run by cron as follow:

        /usr/local/sendmailanalyzer/sa_cache >/dev/null 2>&1

If you have set per domain report sa_cache will create cache files for eachdomains. These cache files are name cache.pm for the MTA global statisticsand cache.pmYOURDOMAIM.DOM for each domain report. To lowered the memoryfootprint of the sa_cache program, since version 8.0 it start computing cachefile per hours.

Since version 4.0 sa_report.cgi will warm you to avoid out of memory whenyour entering a month view without caching. 

Huge MTA activity

On MTA server with very huge activity you can experience out of memory orwait a very long time before seeing anything in day view. In this case youmust run by cron job the perl script sa_cache with the -a option to buildcache files for the current day. Statistics will not be shown in realtime butonly at the time of the last sa_cache run. You can run it each five minute forexample as follow:

    */5 * * * * /usr/local/sendmailanalyzer/sa_cache -a

or

    */5 * * * * /usr/local/sendmailanalyzer/sa_cache --actual-day-only

It will only parse data stored in the current day so five minutes intervalmay be enough for most case. 

Database

SendmailAnalyzer store data into flat file database. Data are store ina time hierarchical directory structure ending at daily level. This structureis composed as follow : 'mailhost'/year/month/day/In each day repository you can find the following data files.

        senders.dat: senders informations.        recipient.dat: recipients informations.        spam.dat: spams informations.        virus.dat: viruses informations.        rejected.dat: rejected mail informations.        dsn.dat: Delivery Status Notification report        syserr.dat: SYSERR MTA informations.        other.dat: other message grabbed into the log file.        auth.dat: SMTP auth message grabbed into the log file.        miltername.dat: message related to a milter, antivir or antispam.

The format of each file is explain in the SendmailAnalyzer code source. 

Archiving

When sa_cache is run and following the value of the FREE_SPACE configurationoption it will try to archive data older than the current month. If FREE_SPACEis set to 'delete' sa_cache will simply remove the data file from disk. If youset it to 'archive', sa_cache will build a gzipped tarball for all daily datafile into the corresponding month directory and the remove date file from disk.

If you set it to 'none', data file are kept.

If you're primary concerned in disk space saving set it to 'delete'. If youwant to preserve data for a year or more you can safely set it to 'archive'.For your information one of my server has 100,000 inbound message a day anda year of 'archive' storage take around 1Gb and a 'delete' storage around250Mb.

One advantage of the 'archive' method is that you can replay the cached stats(for example after an upgrade to fix a sa_cache bug :-). In this case, youjust have to delete any cache file and extract all tarbal as follow :

        find /path/to/SendmailReport/ -name "cache.pm*" | xargs -i rm -f {}        find /path/to/SendmailReport/ -name "history.tar.gz" | xargs -i \                tar xzf {} --directory /

and then rerun sa_cache again.

Important: running sa_cache in one pass on en entire year could cost a lotof resources and takes very long time. In this case add a second argument tothe command line giving the year/month to proceed, for example:

        sa_cache -s 'mailhost' -d "2008/06"

repeat this command for each month. 

CONFIGURATION

The default path to configuration file is /etc/sendmailanalyzer.conf If you wantto change this path, please edit cgi-bin/sa_report.cgi, sa_cache to match you'reneed. For sendmailanalyzer use the --config|-c command line argument.

The configuration file consist in a text file with a configuration optionin upper case and a value or list of value separated by a tab character.

Here are the definition of all this configuration directives. 

System commands options

TAIL_PROG
Path to the system tail command. Can be overwritten with --tail or -t insendmailanalyzer args. Default is /usr/bin/tail.
TAIL_ARGS
Command line argument passed to the tail system command. Can be overwrittenwith --args or -a in sendmailanalyzer args. Default is -n 0 -f.
ZCAT_PROG
Path to zcat system command used to parse compressed log file. Can beoverwritten with --zcat or -z in sendmailanalyzer args. Default is/usr/bin/zcat.
FREE_SPACE
Select the freeing space method for data files older than the current month.The value can be:

        - delete: definitively remove all data files.        - archive: make a gzipped tarball of data files before deleting them.        - none: don't do anything. Need lot of space disk.

Default is archive.

 

Input/output options

LOG_FILE
Path to the maillog file to analyse. Can be overwritten with --log or -lin sendmailanalyzer args. Default is /var/log/maillog. If the extensionis .gz SendmailAnalyzer will automatically use zcat to parse the compressedlog. For Postix you may use /var/log/mail.log instead.
OUT_DIR
Output directory for data storage. Can be overwritten with --output or -oin sendmailanalyzer args. The directory must exist, being writable bythe user running sendmailanalyzer and sa_cache. It must be readableby the http user for CGI script sa_report.cgi.Default is /var/www/sendmailanalyzer
DEBUG
Turn on/off debug/verbose output mode. Can be overwritten with --debug or -din sendmailanalyzer args. Default is 0, disable.
DELAY
Delay in second to flush collected data to disk. Can be overwritten with--write-delay or -w in sendmailanalyzer args. Default is 60 seconds.During this time data are kept in memory to limit disk I/O and gain speed.If you experience an out of memory on huge mail server adjust this valueto something smaller depending of your hardware configuration.
 

Reporting/display options

ERROR_CODE
Path to SMTP error code file (relative to CGI directory) where sa_report.cgiis running. Default: lang/ERROR_CODE.
LANG
Path to the translation file (relative to CGI directory) where sa_report.cgiis running. Default: lang/en_US.
URL_LOGO
Url to the barorng image. Default: /salogo.gif
TOP
Number of object displayed in the top statistics. Default is 25.
TOP_MBOX
Number of object displayed in the top email addresses statistics.Default is 25.
MAX_RCPT
Max number of recipients per message where senders will be reported.Default 25 recipients max.
MAX_SIZE       10000000
Max size in bytes per message where senders will be reported.
Default is 10000000.
MAX_LINE
Max lines to show in detail view. Default is 100.
SIZE_UNIT
Size Unit to use, default is Bytes. Other values are KBytes and MBytes.
DOMAIN_REPORT
Compute statistics and cache for a list of domain and display a link in thefront page for a per domain access. See DOMAIN_USER if you want to grantspecial access on these pages. You can have multiple DOMAIN_REPORT lines.If you are running rsyslog with multiple host use DOMAIN_HOST_REPORT instead.Example:

        DOMAIN_REPORT   domain1.com,domain2.com
DOMAIN_HOST_REPORT
Compute statistics and cache for the given host followed by a list of domainand display a link in the front page for a per domain access under each host.You can have multiple DOMAIN_HOST_REPORT lines. See DOMAIN_USER if you wantto grant special access on these pages. For example:

        DOMAIN_HOST_REPORT      host1   domain1.com,domain2.com        DOMAIN_HOST_REPORT      host2   domain2.com,domain3.com
ANONYMIZE
This option allow the anonymization of the output, i-e it remove anysender/recipient personal information from the report.
REPLACE_HOST
This option replace some hostname in all relay information for anonymizationYou must used one REPLACE_HOST line per replacement.

        REPLACE_HOST    internal.relay.dom      external.relay.dom
SPAM_VIEW
Enable/Disable menu links to Spam views. Default show it: 1
VIRUS_VIEW
Enable/Disable menu links to Virus views. Default show it: 1
DSN_VIEW
Enable/Disable menu links to Notification views. Default show it: 1
SHOW_DIRECTION
Enable/Disable messaging/spam/virus/dsn direction statistics. Default is show.On some mailhost this could show wrong information if the direction couldnot be easily determined. So you can remove these views by setting it to 0.
SPAM_TOOLS
List of antispam name separated by a comma used for Spam details view. You maywant to custom this list to just show menu link on available reports. Defaultlist is:

        spamdmilter,jchkmail,dnsbl,spamassassin,amavis,mimedefang,dnsblmilter

Feel free to remove those you're not using to not see link to empty report inthe menu.

 

Maillog parsing options

FULL
Parse maillog from begining before running tail program. Can be overwrittenwith --full or -f in sendmailanalyzer args. Default is 0, jump at the endof log. Most of the time you may want to enable this to jump at the last parsedline during the previous run.
BREAK
Do not run tail program and exit after a full parsing of the log file.Can be overwritten with --break or -b in sendmailanalyzer args. Defaultis 0, go ahead with tail.
MTA_NAME
Syslog name of the MTA. Syslog write it to maillog with the pid as... sendmail[1234] ... This is required to only parse relevant lines.Can be overwritten with --sendmail or -s in sendmailanalyzer args.Default is sendmail, some distro come with sm-mta instead. Some otherhave multiple names (ex: sm-mta, sendmail and sm-msp-queue) in thiscase you can set the value of this directive to a pipe separated listof values, for example: sm-mta|sendmail|sm-msp-queue.

Default: sm-mta|sendmail|postfix

MAILSCAN_NAME
Syslog name of MailScanner. Syslog write it to maillog with the pid as... MailScanner[1234] ... This is required to only parse relevant linesCan be overwritten with --mailscanner or -m in sendmailanalyzer args.Default is MailScanner.
AMAVIS_NAME
Syslog name of Amavis. Syslog write it to maillog with the pid as... amavis[1234] ... This is required to only parse relevant lines.Default is amavis.
MD_NAME
Syslog name of MimeDefang. Syslog write it to maillog with the pid as... mimedefang.pl[1234] ... This is required to only parse relevant linesbased on parsing mimedefang log generated by method md_graphdefang_log()Default is mimedefang.pl.
CLAMD_NAME
Syslog name of Clamd. When using Mailscanner with clamd if you want virusreport you must configure clamd to log with syslog and use LOG_MAIL. Defaultvalue is 'clamd' (... clamd[1234] ...)Can be overwritten with --clamd or -n
LOCAL_DOMAIN
Coma separated list of internal domain to be used when SendmailAnalyzeris running on a mail host which received message from any side. SA can'tknow what message are internal or external in this case, so the only wayto know if a mail come from Internet or Lan/Wan is to check the domainpart of the relay sender address. You can have multiple LOCAL_DOMAIN linesfor better reading.

For example:

        LOCAL_DOMAIN    domain1.com,domain2.com,...        LOCAL_DOMAIN    domain3.com        LOCAL_DOMAIN    domain4.com
LOCAL_HOST_DOMAIN
Same as above but with host distinction for use with rsyslog.You can have multiple LOCAL_HOST_DOMAIN lines, ie: one per host.

For example:

        LOCAL_HOST_DOMAIN   sysloghost1        domain1.com,domain2.com        LOCAL_HOST_DOMAIN   sysloghost2        domain3.com,domain4.com
MAIL_HUB
FQDN coma separated list of internal mail hubs, aka: where email areredirected if the host is a gateway. For example: mailhost.mydom.domThis directive is very important to help SendmailAnalyzer to find thedirection of incoming and outgoing message.
MAIL_GW
FQDN coma separated list of MTA gateways where external mail comes from.This directive is very important to help SendmailAnalyzer to find thedirection of incoming and outgoing message.
DEFAULT_DOMAIN
Default domain or hostname to add to an email address if there's just theusername. When the host is a delivery system it is possible that the useremail address do not have the domain part (ex: @domain.com). By defaultSendmailAnalyzer will add the '@localhost' domain but you may want to changethis domain, so use this directive
SPAM_DETAIL
This directive allow report for Spam details. Enable by default. This allowyou to see complete detail of your favorite antispam as well as score, cachehit and autolearn if your antispam report it. To disable set it to 0, youwill save disk space.
SMTP_AUTH
This directive allow report for SMTP authentication. Enable by default. Thisallow you to see per authent type (server or client) user and relay statistics.If you not use SMTP Auth set it to 0 to disable this feature. These stats arenot available in per domain views.
MERGING_HOST
Use this directive to combined multiple mailhost report on a single report.This allow you to aggregate multiple mailhost that syslogs to a remote serverthrought rsyslog to have only one SendmailAnalyzer report. The value must onlyuse alphanumeric character as it is used to create subdirectory.
 

Domain / user views options

LOW_LIMIT, MEDIUM_LIMIT, HIGH_LIMIT (NO MORE USED)
User messaging data limit in megabytes to show/warn the level of mail activity.LOW_LIMIT (3 by default), mail activity under this limit is shown as green.MEDIUM_LIMIT (5 by default), mail activity under this limit is shown as orange.HIGH_LIMIT (10 by default), mail activity under this limit is shown as red.above the hight limit the user is warn for abuse. Set all to 0 if you want todisable this feature.
ADMIN
List of admins username separated by coma that must have full access to allreport. The username is checked again the http REMOTE_USER environment variable.Default is every one can access, in this case you may want to add a .htaccess.
DOMAIN_USER
List of per user domain access control. The first field is the username andthe second field (separated by tabulation) is a coma separated list of domainname to be allowed to this user. You could add as many lines of DOMAIN_USERas you want in the configuration file.
 

ACCESS CONTROL

Access control is based on the REMOTE_USER environment variable stored by thehttpd server during an htaccess Authentication. If this variable is not set,there is full access for every one. 

AUTHOR

Gilles Darold <gilles @nospam@ darold.net> 

COPYRIGHT

Copyright (c) 2002-2011 Gilles Darold - All rights reserved.

        This program is free software: you can redistribute it and/or modify        it under the terms of the GNU General Public License as published by        the Free Software Foundation, either version 3 of the License, or        any later version.        This program is distributed in the hope that it will be useful,        but WITHOUT ANY WARRANTY; without even the implied warranty of        MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the        GNU General Public License for more details.        You should have received a copy of the GNU General Public License        along with this program.  If not, see < http://www.gnu.org/licenses/ >.
 

BUGS

Your volontee to help construct a better software by submitting bug report orfeature request as well as code contribution are welcome. 

ACKNOWLEDGEMENT

Thank to Sendmail.org for the kind permission to use the ``Bat'' logo.


 

Index

NAME
DESCRIPTION
POSTFIX SUPPORT
FEATURES
Global Statistics
Top Statistics
ISP like feature
Milter / Filter supported
New features
Internationalization
REQUIREMENT
INSTALLATION
Generic install
Package install
Custom install
USAGE
Standalone
Daemon mode
Stopping SendmailAnalyzer
Caching
Huge MTA activity
Database
Archiving
CONFIGURATION
System commands options
Input/output options
Reporting/display options
Maillog parsing options
Domain / user views options
ACCESS CONTROL
AUTHOR
COPYRIGHT
BUGS
ACKNOWLEDGEMENT

This document was created byman2html,using the manual pages.
 
internet katowice