BarricadeMX. QUICK GUIDE FOR COMMON TASKS Step by step instructions for Getting started with BarricadeMX, version 2.x Fort Systems Ltd 2009

Transcription

1 2009 BarricadeMX QUICK GUIDE FOR COMMON TASKS Step by step instructions for Getting started with BarricadeMX, version 2.x Fort Systems Ltd 2009

2 This Quick Guide for Common Tasks This reference is intended to assist you with to quickly find out how to perform the most common tasks in BarricadeMX. Adding a domain to route or relay for Whitelisting / Blacklisting senders Whitelisting / Blacklisting URIs and URLs Routing mail for Domains In the Barricade web interface click on the Domain and Relays tab and you will see this screen: The three bank text boxes at the bottom of the page are for entering data to search for, route for or relay for. The left text box should contain the Domain or IP address to Route or RELAY for. The middle text box should contain the Deliver to Host: Port number And the right text box should contain the Verification Host If the check-box is enabled any host with a Fully Confirmed DNS name (FCrDNS) that is within the domain that you are routing for, will be allowed to RELAY out through the gateway or gateways. For a detailed definition of FCrDNS. A simple explanation of an FCrDNS records is a DNS record where the domain name of the A and PTR reords for a given host match. For example: PTR Record ---> hostname.example.com hostname.example.com --- A Record ---> For a more detailed explanation of ah FCrDNS Please see: Fort Systems Ltd

3 The Add button saves an entry The Search button searches for entries that match any text entered into one or more of the three text boxes. Example 1: Accept mail for the xyz.com domain, forward accepted message directly to the mail hub at and verify the address is valid on the mail hub before accepting the message. Allow any host with a FCrDNS record ending in the.xyz.com domain to RELAY out through the gateway(s). Fill-in 1: Domain or IP address: xyz.com Host:Port: (Port number is not needed if Port=25) Verification Host: (leave blank. Not needed if Verification Host = Deliver to Host) Check Box: yes (allows any host with a DNS record ending in xyz.com to RELAY through the gateway or gateways) Example 2: Accept mail for the abc.net domain, forward accepted message to sendmail listening on port 26 on this system and verify the address is valid on the mail hub, before accepting the message. Any host with a FCrDNS record in the abc.net domain will be allowed to RELAY messages out through the gateway(s). This is a typical setup where MailScanner or DefenderMX is also running on this gateway and used to further process the messages. Fill-in 2: Domain or IP address: abc.net Host:Port: :26 Verification Host: Check Box: yes Example 3: Accept mail for the mydomain.net domain, forward accepted message to sendmail listening on port 26 on this system and verify the address is valid on the mail hub, before accepting the message. Allow any host on the host subnet to RELAY messages out to any domain through the gateway and allow only the mail hub to relay out through the gateway. Fill-in 3a: Domain or IP address: abc.net Host:Port: :26 Verification Host: Check Box: no Fill-in 3b: Domain or IP address: Host:Port: RELAY Verification (leave blank) Check Box: yes Fort Systems Ltd

4 Fill-in 3c: Domain or IP address: Host:Port: RELAY Verification (leave blank) Check Box: yes RELAYing mail from other systems To allow a host without an FCrDNS record, a domain or a subdomain to RELAY out through the gateway, you must create a separate record using the Domains and Relay tab. In this case is always safer to use an IP address to specify the IP address of the host or subdomain that should be allowed to relay. Example 1: The host with IP address should be allowed to relay messages out though the gateway. Fill-in: 1 Domain or IP address: Host:Port: (leave blank. not needed) Verification Host: (leave blank. not needed) Example 2: hosts on subnet should be allowed to relay messages out though the gateway. Fill-in 2: ( Domain or IP address: Host:Port: (leave blank. not needed) Verification Host: (leave blank. not needed) Select Add when finished to save the entry) The 'local route' The local route is the entry where the IP address is set to ' '. This entry must be present for BarricadeMX to function correctly. The local route is used by BarricadeMX when it needs to relay mail outbound and it connects to the host defined in 'Deliver to Host' to do this, so the host defined as here must allow BarricadeMX to relay and by default this is defined as the local host on port 26, presuming that a local MTA is configured and listening on this port. If a verification host is configured on the local route then it will be used whenever SMTP AUTH is used and the username that is sent is unqualified. Fort Systems Ltd

5 Whitelisting / Blacklisting The Access Controls' tab defines local white and black lists, exemptions to some tests and the defaults for other tests. The pull down menu at the top middle of the page selects control to be configured. For White and black listing the controls select Network Access: connect, to, from, connect:from, connect:to, to:from The bottom of the screen contains: The left pull-down menu should contain Tag to control the action The middle text box should contain the Key to match And the right text box should contain the Value that defines the action The Add button saves an entry The Search button searches for entries that match any text entered into one or more of the two text boxes. Example 1: Whitelist any from fsl.com Fill-in 1: Tag: connect Key: fsl.com Example 2: Whitelist any from jane@fsl.com Fill-in 2: Tag: from Key: jane@fsl.com Fort Systems Ltd

6 Example 3: Whitelist any from the subnet Fill-in 3: Tag: connect Key: Example 4: Blacklist any from Fill-in 4: Tag: connect Key: Value: REJECT Example 5: Whitelist any from freeoffers.com Fill-in 5: Tag: From Key: freeoffers.com Value: Reject Example 6: Whitelist any from the and to Fill-in 6: Tag: connect:from Key: Example 7: Blacklist any from abc.com and to Fill-in 7: Tag: from:to Key: Value: REJECT Example 8: Whitelist any from the subnet Fill-in 8: Tag: connect Key: Fort Systems Ltd

7 Whitelisting / Blacklisting URI and URLs The Access Controls' tab also defines what URI and URLs can be present in a message even if that URI or URL Is present in URI/URL blacklists that are configured for use: It may also be used to specify text strings that you never want to allow in a URI or URL in a message. The pull down menu at the top middle of the page selects control to be configured. For White and black listing of URI/URSL, the Control selected should be URI Black and White Listing: body The bottom of the screen contains: The left pulldown menu should always contain the Tag body The middle text box should contain the Key to match And the right text box should contain the Value that defines the action The Add button saves an entry The Search button searches for entries that match any text entered into one or more of the two text boxes. Example 1: Whitelist the URI offers@goodoffers.com Fill-in 1: Tag: body Key: goodoffers.com Fort Systems Ltd

8 Example 2: Blacklist the URL Fill-in 2: Tag: body Key: spamsite.com Value: REJECT Fort Systems Ltd