Ironclad SecurityDNS MX Lookups with SPF Meridius performs DNS mail exchange record lookups, and routes messages using the MX record that identifies the mail server responsible for handling emails for that domain name. Alternatively, specify a transport target that identifies a specific server destination for messages. Meridius also protects organizations against harmful “phishing” attacks with the industry-standard Sender Permitted Framework (SPF) which utilizes DNS for all lookups. Onboard Caching DNS Server Meridius includes an onboard caching DNS server for optimal performance, with DNS configurations initially created though the Meridius Configuration Wizard. Select this onboard server for mail routing to improve performance significantly, or specify a list of your organization’s external DNS servers. Using Meridius’ onboard caching DNS server also enables you to define custom root name servers. SMTP Configuration and Authentication Settings SMTP is an Internet email system protocol for email delivery for communication between sending machines and receiving machines. The Meridius configuration file contains a data page with the Simple Mail Transfer Protocol (SMTP) settings for each primary Meridius appliance in your mail relay. The Meridius Management Console also enables SMTP authentication to identify authorized or privileged users to access your mail relay. Transport Settings per Domain/Subdomain Define routing rules to help increase email delivery efficiency. Routing rules govern the way the Meridius appliance delivers messages to recipients. For example, define rules that control delivery of all messages going to addresses ending in “org”, or create a different set of routing rules for messages going to the top-level domain (TLD) of “edu”. Carry this process a step further by defining special delivery rules for specific subdomains of a TLD. For example, define rules that ensure that transport settings are optimized for addresses to which your company regularly sends large volumes of email (such as suppliers or major clients). When considered over a large volume of messages, this procedure can make a big difference in the efficiency and cost-effectiveness of your network. A variety of transport settings are covered by the routing rules: the time interval between each retry during SMTP sending, the amount of idle time between SMTP commands before declaring the connection dead, the address of a specific target server (if it is known) to further increase the efficiency of email delivery to a TLD or subdomain, and more. IMAP/POP Proxies Move IMAP4/POP3 servers from your DMZ into your private network by adding an IMAP4/POP3 proxy to your mail relay configuration. Meridius acts as a bridge between Internet clients and the back end servers, making sensitive email stores less prone to security breaches. Meridius’ built-in firewall provides an additional layer of protection. Select the type of encryption used for connection to your POP3/IMAP4 server. Clear Text uses no encryption for messages, and is most appropriate for behind-the-firewall communications between Meridius and your mail server. The Secure Sockets Layer protocol encrypts messages sent over an SSL connection, such as POP/IMAP messages sent to your server from outside your firewall. The Meridius Management console also enables defining entries into the User Login Map to manage special situations in which mapping of usernames is not direct. In these cases, Meridius must translate the local username to a remote username. Maintenance Log Management Log files help network administrators test and troubleshoot email relay systems. When deploying a new configuration file, use Meridius’ log files to view mail routing activity to ensure that traffic is moving smoothly and efficiently, and to pinpoint potential problems. If issues arise after deployment, view the log files to determine problem areas. The Meridius Management Console compiles three types of logs that record the various types of activity on your email relay system: - Mail logs — record the in/out traffic of messages, including the routing and acceptance of email.
- System logs — record the activities involving the operating system, including starting and stopping the server, and displaying error messages (such as low disk space warnings).
- Access logs — record everything done with the Meridius client software to access the server (such as deploying a configuration file).
|
