Mail Store & Forward HOWTO

To use TZO Store and Forward (SAF) you must own a registered Domain Name, and also have DNS service for that domain. This Howto assumes you have previously purchased these services with TZO, or that you have Domain Registration and DNS at a third party service provider. If you are looking to order SAF with a Domain Registration which is still in your cart, please complete the Domain Registration purchase first.

On the Store and Forward product page, specify the domain name you will apply this service to. Select your SAF queue size: 250MB, 500MB, or 1GB. Select the term or length of your SAF subscription (1 year, 2 years, or 5 years). When satisfied with your selections, please press 'Add to Cart'.

The My Shopping Cart page will preview your service purchase and subtotal cost. Before being purchased, you must show and Accept the TZO Terms of Service.

Press 'Configure Details' to continue to Store and Forward Configuration...

The Store and Forward settings can be configured before purchase.

'Mail Server Address or IP' is the Internet address Store and Forward will relay inbound email TO. If you use a hostname for this field, it must resolve to your mailserver. You may use a dynamic DNS domain name. You may also specify a fixed (static) IP address, provided the IP value points to your mailserver. 'Server Port' is the TCP port your mailserver accepts connections from TZO on. The standard value for port is 25, but if your inbound port 25 is blocked by your ISP then you can instruct SAF to relay into another of your unblocked ports (usually port 2525 or port 2025).

Using SAF as a Backup MX
Example: you have a mailserver already working, and you need an offsite MX which can accept, queue, and store your email when your primary MX goes offline (maintenance, modem failure, any reason) with each message held for 14 days.

Using SAF as a Primary MX
Example: you have a workgroup-type mailserver already working for an office LAN, such as Microsoft Exchange or MDaemon. You want to improve performance on these systems by reducing the amount of spam which 'gets' to your server, and also conserve bandwidth. You might also have problems with 'Mailbox Forwarding' sometimes not working (when you 'Enable Mailbox Forwarding' forwarding on a workgroup server, it is sending non-spam and spam alike to the target address, essentially spamming the target ISP). But when you are using Store and Forward as a Primary MX, all mail traffic passes through the SAF filters so the bad email never reaches your server, and the mailbox forwarding issue becomes a non-issue. Of course SAF will still accept, queue, and store your email if your mailserver goes offline.

Using SAF as an Alternate-Port SMTP Relay (Primary MX)
Similar to the previous use case of Primary MX, except your Internet Service Provider blocks all inbound port 25 traffic. Not to worry - use Store and Forward as your Primary MX, and in the SAF Configuration choose one of the following Ports: 25, 26, 465, 587, 2025, 2125, 2525, 8025. Of course SAF will still help you filter out spam as well as accept, queue, and store your email if your mailserver goes offline.

Once you designate your SAF configuration, complete your checkout. If your domain's DNS is hosted with TZODNS, your MX records were automatically updated according to your SAF Configuration during checkout. If your DNS is hosted with a third party, you will need to visit your DNS provider's website and edit your Primary MX to be 'saf.tzo.com' (or saf.tzo.com as the Secondary MX, if that is the configuration you want).

Once Store and Forward is active for your domain, you should begin seeing email connections and deliveries from the Store and Forward servers. However you still must configure your mailserver to 'whitelist' the SAF server IPs 108.59.168.36 and 108.59.160.146 so that your mailserver will never 'graylist' (unnecessarily delay) mail we try to deliver to your server.

If your mailserver performs 'reporting' of Spam, you must disable that reporting so it does not report SAF as the originator of the spam. Disable any OpenSPF or SenderID checks on your server, because it sees the mail as originating from SAF not the sender. Do not use the Store and Forward service with 'hosted' or service-based email (such as Postini) because they will see any spam as 'originating' from SAF and do not allow you to whitelist trusted server IPs. If you use a Barracuda Spam Firewall you must add the SAF IP addresses as a Trusted Forwarder IP.