brightmail – Brightmail Module

brightmail "brightmail1"{
  server = "10.10.10.20:41111"
  num_workers = 10
  sieve_mode = "on"
  sieve_prefix = "brightmail"
  max_size = 2048
  timeout = 15
}

idle_timeout

Open connections to the brightmail server are cached. This defines how long to keep an idle connection open.

max_messages_per_connection

**Configuration Change. ** This feature is available starting from Momentum 3.1.

The brightmail module will drop a connection after processing this many messages. Set this option to 0 to process an unlimited number. The default value for this option is 0.

max_size

This option specifies the number of bytes sent to the brightmail server. For example, if this is set to 2048 and a message of 4,000 bytes is received, only 2048 will be sent to the Brightmail server.

max_tries

The number of times to attempt a connection to the brightmail server; if we can't connect and max_tries is greater than one, retry the connection max_tries number of times.

num_workers

Specifies the concurrency of access to the Brightmail service. For numbers greater than zero, this specifies the number of threads that will be used to concurrently communicate with Brightmail. Each thread will have its own TCP/IP connection to the server and be capable of handling new messages serially. 0 (zero) has a special meaning: exactly one connection will be made synchronously to the main Momentum process and thus block other operations—this is highly discouraged.

server

Specifies the IP address and port on which the Brightmail service should be reached. Since the module makes a TCP connection it isn't essential that it run on the same server as Momentum. Instead of an IP address, you can also specify the hostname.

sieve_mode

This option specifies whether to operate in script-only mode or not. If this option is active then no brightmail checking will occur unless called for directly from a Lua or a Sieve script. If the module is loaded with "sieve_mode = off" then the scanner will be run from the module (rather than a script) for all messages in the data phase. If you set sieve_mode to on then you need to invoke the brightmail_scanner manually. This can be invoked at the data, spool or each_rcpt phases. It will not work at the connect, ehlo, mailfrom or rcptto phases. If you don't want brightmail to see a given message, do not call msys.brightmail.scan or brightmail_scanner for that message.

In version 3.x, this option must be set to on if you wish to use the Lua function, msys.brightmail.scan.

For more information on using brightmail from Sieve see brightmail.

sieve_prefix

Specifies a name for a specific brightmail server instance. Allows you to concurrently interface with any number of servers that use the brightmail module. This setting also determines the prefix for the validation context variable and the names of the brightmail Sieve functions. See “Brightmail Runtime Usage” and brightmail. The default value for this option is brightmail.

timeout

Specifies the maximum time to wait for a response before assuming a failure on the part of the brightmail server.

*`brightmail`*::error

This variable, if it exists, contains information pertaining to the error that occurred while attempting to process the current message through the Brightmail service.

$err = vctx_mess_get "brightmail::error";
if not ec_test :is $err "" {
  ec_action 451 "Brightmail issue";
}