Mailets and Matchers Reference

Mailets

LocalDelivery

Mailet Info: Local Delivery Mailet
Receives a Mail from JamesSpoolManager and takes care of delivery of the message to local inboxes. Since James 2.3.0 this mailet is a composition of UserRepositoryAliasingForwarding and ToMultiRepository configurated to mimic the old "LocalDelivery" behaviour.

ToMultiRepository

Mailet Info: ToMultiRepository Mailet
Receives a Mail from JamesSpoolManager and takes care of delivery of the message to local inboxes or a specific repository. Differently from LocalDelivery this does not lookup the UserRepository This simply store the message in a repository named like the local part of the recipient address or the full recipient address, depending on the configuration (repositorySelector). If no repository is specified then this fallback to MailServer.getUserInbox. Otherwise you can add your own configuration for the repository e.g: file://var/spool/userspools/ SPOOL file://var/mail/inboxes/ MAIL Header "Delivered-To" can be added to every message adding the Delivered-To defaults to "localpart" and can be changed to "full" if you prefer to use full recipient emails as repository names.

UsersRepositoryAliasingForwarding

Mailet Info: Local User Aliasing and Forwarding Mailet

Receives a Mail from JamesSpoolManager and takes care of delivery of the message to local inboxes. Available configurations are: true: specify wether the user aliases should be looked up or not. Default is false. true: enable the forwarding. Default to false. LocalAdmins: specific users repository name. Default to empty. If empty does lookup the default userRepository.

VirtualUserTable

Mailet Info: VirtualUserTable Mailet

Mailet which should get used when using VirtualUserTable-Store to implementations for mappings of forwards and aliases. If no VirtualUsertable-Store name is given the default of DefaultVirtualUserTable will get used. eg. DefaultVirtualUserTable