This article applies to:

• Trustwave MailMarshal (SEG)

Question:

Procedure:

In smaller organizations where there is no existing POP3 mail server, MailMarshal can function as a POP3 server. All internal mail will be stored in mailboxes on the MailMarshal server, ready for collection by POP3 clients. This article explains how to set up MailMarshal as a POP3 server.

• Note: POP3 in SEG/MailMarshal is a convenience feature.
  • It cannot be used in an array with multiple nodes.
  • Due to the limited configuration abilities, this feature is only suitable for very small numbers of mailboxes.
  • Many free POP3 servers are available. Customers requiring POP3 as a main solution for user mailboxes should explore those options.

For additional information about these procedures see the User Guide and Help for your version of MailMarshal.

1. Set the Routing information for Local Domains in MailMarshal to 'POP3'. Delivery is handled by routing tables. If POP3 routes exist, MailMarshal automatically starts an additional service to respond to POP3 requests. This POP3 service appears in the list of services in the user interfaces. To enable POP3 delivery for a domain, create or edit the Route for the domain and select "Deliver to POP3 mailboxes." You can also create a single route for all Local Domains.
2. Routing Messages for Undefined Accounts. If a message arrives for an undefined POP3 mailbox, you may want to send it to an administrator account, attempt delivery to an internal email server, or reject the message.
   1. Forward the message to an administrator account: To forward to the administrator e-mail address, when you set routing to POP3, check the box For undefined messages... The messages that do not match an account will be delivered to the Administrator account as set on the Notifications tab of Server Properties.
   2. Forward the message to another mail server: To forward to another server, create an additional route for the domain, with lower priority. Set the route to the server name or IP address of the server. The messages that do not match an account will be forwarded to this server for final delivery.
   3. Reject the message: If neither of the above options is set, then any message to a POP3 domain that does not match an existing account will be undeliverable. A non-delivery message will be returned to the sender with a 'Mailbox/User is unknown' reason code.

• Changing Existing 'Relay' Type Domains. To change an existing 'Relay' type domain to a POP3 domain, edit the routing information for the domain.

1. Set up POP3 Accounts in MailMarshal.  An account must be created for each mailbox that will be hosted by MailMarshal. To create an account and mailbox, select the Accounts node in the MailMarshal Configurator or Management Interface. Add one or more accounts. Enter the details of the POP3 account holder and authentication information. MailMarshal will automatically enter an appropriate SMTP alias. You can change or add additional SMTP aliases as required. You can use the value Local Domains to stand for all local domains.
   
   Notes:
   • Ensure you create an account for the administrator address.
   • If more that one POP3 account has the same SMTP alias, messages directed to that alias will be delivered to all of the mailboxes.
2. Configure POP3 Clients to Point at the MailMarshal Server. All e-mail sent from within the organization will be sent to the MailMarshal server on port 25. E-mail for internal addresses will be delivered to MailMarshal POP3 mail boxes for collection by e-mail clients. E-mail clients will need to be configured to:
   1. Send mail to the MailMarshal server on port 25.
   2. Collect mail from the MailMarshal server on port 110, using POP3.

Notes:

Related KB article:

• Q10216 : How do I automatically create POP3 accounts in  MailMarshal?

This article was previously published as:

NETIQKB29511

Marshal KB288