Distributed James Server — SMTP Hooks

This command handler check against RBL-Lists (Real-time Blackhole List).

If getDetail is set to true it try to retrieve information from TXT Record why the ip was blocked. Default to false.

before you enable out the DNS RBL handler documented as an example below, please take a moment to review each block in the list. We have included some that various JAMES committers use, but you must decide which, if any, are appropriate for your environment.

The mail servers hosting @apache.org mailing lists, for example, use a slightly different list than we have included below. And it is likely that most JAMES committers also have slightly different sets of lists.

The SpamAssassin user’s list would be one good place to discuss the measured quality of various block lists.

NOTA BENE: the domain names, below, are terminated with '.' to ensure that they are absolute names in DNS lookups. Under some circumstances, names that are not explicitly absolute could be treated as relative names, leading to incorrect results. This has been observed on *nix and MS-Windows platforms by users of multiple mail servers, and is not JAMES specific. If you are unsure what this means for you, please speak with your local system/network admins.

This handler should be considered experimental.

Example configuration:

The Distributed James Server has optional support for DSN (RFC-3461)

Please read carefully this page.

Note that a specific configuration of mailetcontainer.xml is required as well to be spec compliant.

This handler can add a hint to the mail which tells the MailQueue which email should get processed first.

Normally the MailQueue will just handle Mails in FIFO manner.

Valid priority values are 1,5,9 where 9 is the highest.

This handler should be considered experimental.

Example configuration:

If activated you can limit the maximal recipients.

This handler should be considered experimental.

Example configuration:

This connect handler can be used to enable POP3 before SMTP support.

Please note that only the ip get stored to identify an authenticated client.

The expireTime is the time after which an ipAddress is handled as expired.

This handler should be considered as unsupported.

Example configuration:

Checks for resolvable HELO/EHLO before accept the HELO/EHLO.

If checkAuthNetworks is set to true sender domain will be checked also for clients that are allowed to relay. Default is false.

This handler should be considered experimental.

Example configuration:

Checks HELO/EHLO is equal the reverse of the connecting client before accept it If checkAuthNetworks is set to true sender domain will be checked also for clients that are allowed to relay. Default is false.

This handler should be considered experimental.

Example configuration:

This handler allows you to add mime headers to the processed mails.

This handler should be considered experimental.

Example configuration:

This MessageHandler could be used to check message against spamd before accept the email. So it’s possible to reject a message on smtplevel if a configured hits amount is reached.

This handler should be considered experimental.

Example configuration:

This command handler can be used to reject emails with not match the SPF record of the sender domain.

If checkAuthNetworks is set to true sender domain will be checked also for clients that are allowed to relay. Default is false.

This handler should be considered experimental.

Example configuration:

This MessageHandler could be used to extract domain out of the message and check this domains against uriRbllists. See http://www.surbl.org for more information. The message get rejected if a domain matched.

This handler should be considered experimental.

Example configuration:

With ValidRcptHandler, all email will get rejected which has no valid user.

You need to add the recipient to the validRecipient list if you want to accept email for a recipient which not exist on the server.

If you want James to act as a spamtrap or honeypot, you may comment ValidRcptHandler and implement the needed processors in spoolmanager.xml.

This handler should be considered stable.

Example configuration:

If activated mail is only accepted if the sender contains a resolvable domain having a valid MX Record or A Record associated!

If checkAuthNetworks is set to true sender domain will be checked also for clients that are allowed to relay. Default is false.

Example configuration:

The Distributed James Server has optional support for FUTURERELEASE (RFC-4865)

The Distributed server has optional support for SMTP Extension for Message Transfer Priorities (RFC-6710)

The SMTP server does not allow positive priorities from unauthorized sources and sets the priority to the default value (0).

Hook for verifying DKIM signatures of incoming mails.

This hook can be restricted to specific sender domains and authenticate those emails against their DKIM signature. Given a signed outgoing traffic this hook can use operators to accept legitimate emails emitted by their infrastructure but redirected without envelope changes to there own domains by some intermediate third parties. See JAMES-4032.

Supported configuration elements:

Example handlerchain configuration for smtpserver.xml:

Would allow emails using apache.org as a MAIL FROM or from header domain if, and only if they contain a valid DKIM signature for the apache.org domain.