Search Engine: Elastic

Article ID: 116264, created on Jun 13, 2013, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 5.x

Additional Information

This article describes integration between qmail and mail filtering software in the POA environment.

A mailbox can have a .qmail file, which describes the actions necessary to perform with messages for this account. If the spam filter is enabled, it should have content like the following:
|spamc_wrapper_{$sa_service_id} a/b/{$mailname_id} f m|maildir
The wrapper for spamc is the shell script:
[root@mta1 root]# cat  /usr/local/qmail/bin/spamc_wrapper_{$sa_service_id}
case $server_mode in
        f ) port=783;;
        l ) port=784;;
        * ) exit 0;;
case $spam_action in
        d ) /usr/bin/spamc -f -u $email_name -d {$sa_ip_address} -p $port -c <&0 || exit 99;;
        m ) /usr/bin/spamc -f -u $email_name -d {$sa_ip_address} -p $port <&0;;
        * ) exit 0;;
These wrappers are not rewritten by POA frequently, so it is possible to edit them manually and bind a qmail server with a specific SpamAssassin server.

A mailbox may also have the .antivirus file that indicates if the mailbox should be behind Antivirus check. This file is parsed by the DrWeb agent qmail-queue.override, which transfers messages to a DrWeb server specified next to the Address =  directive in /etc/drweb/drweb_qmail.conf:
Address = inet:3000@
Address = inet:3000@
Address = inet:3000@
The DrWeb filter tries these addresses sequentially until it establishes a connection successfully. For better load balancing, you may specify addresses in a different order on different qmail servers.

See also:
POA Linux Mail Hosting Deployment Guide >> Deploying Linux Mail Hosting > Installing SpamAssassin > Installation Requirements for SpamAssassin

2554725ed606193dd9bbce21365bed4e caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF