|
|
| Line 1: |
Line 1: |
| − | == Overview ==
| + | Article moved here: https://wiki.xmission.com/Spamcatcher_SMTP_Service |
| − | | |
| − | XMission's [http://xmission.com/spamcatcher SpamCatcher] or “SMTP Spam Filter” service is a product for our customers running their own mail servers, but don't have either the ability or resources to install and maintain their own copy of SpamAssassin.
| |
| − | | |
| − | Since XMission maintains an excellent spam and virus filtering system, we created a way to apply our filters to customers external mail servers.
| |
| − | | |
| − | SpamCatcher mail feed also covers you in the case of an emergency. Should your mail server break down, XMission spools your mail for up to 8 days providing ample time to repair your mail server without losing critical customer messaging.
| |
| − | | |
| − | == Sales Information ==
| |
| − | | |
| − | [http://xmission.com/spamcatcher SpamCatcher], SMTP Spam Filtering, costs just $15/mo per domain and can be ordered online or by contacting XMission sales.
| |
| − | | |
| − | Some XMission clients qualify for free SMTP Spam Filtering on a number of domains. Please contact your agent if you think you may qualify.
| |
| − | | |
| − | == Configuring SpamCatcher==
| |
| − | | |
| − | To set up SMTP Spam Filtering, the customer needs to point their domain's MX record to “''mx.xmission.com''” and provide XMission support with the ''Static IP address'' of their mail server. Once this information has been updated in the XMission mail servers and the customer's DNS, it will begin working (total time is approximately 15 min).
| |
| − | | |
| − | It works by making XMission's incoming mail servers the customer's incoming mail servers. With the customer domain MX record pointed to XMission, we receive the mail and our incoming servers apply the spam filtering by using the same RBLs, virus scanning, and spam scoring that they do for any other XMission email.
| |
| − | | |
| − | Once the message has been processed and received, it is relayed to XMission's email queuing server which relays the message to our customer's mail server at the IP address provided.
| |
| − | | |
| − | Optionally, XMission can also configure the system to delete mail at a particular score on the customer's behalf, though typically the customer will use the provided SpamAssassin headers to filter mail as they see fit. If you want XMission to enable this please contact your sales agent.
| |
| − | | |
| − | In addition to the filtering, this setup provides the customer with the ability to change their mail server without having to deal with DNS updates, and keeps the customer's mail server “hidden” from the world. They will only see SMTP conversations from the XMission network, and can apply appropriate firewall rules. Finally, in the case of an emergency where the customer server goes down, XMission will queue customer mail for up to one week.
| |
| − | | |
| − | If a customer's mail gets queued, they point their mail servers to etrn.xmission.com and send the ESMTP ETRN command. When their mail server issues that command it will flush all queued mail for their domain to the IP address specified.
| |
| − | | |
| − | == XMission Spam and Virus Filtering Explained ==
| |
| − | | |
| − | For a deeper understanding how XMission's spam and virus filtering works, please reference this article on our blog: http://transmission.xmission.com/2013/08/14/how-xmission-spam-and-virus-filtering-works
| |
