Spamcatcher SMTP Service - Revision history

Ehigbee: /* Disable default spam tools */

2020-06-22T16:25:35Z

Disable default spam tools

← Older revision		Revision as of 10:25, 22 June 2020
Line 33:		Line 33:
	== Disable default spam tools ==		== Disable default spam tools ==

	It is highly recommended you disable any spam scanning that is included in your own mail server when using SpamCatcher to avoid any conflicts. Should you choose to run your own spam scanning software, be sure you ~~whitelist~~ XMission's ip range (198.60.22.0/24, 166.70.13.0/24 and 166.70.11.0/24). Additionally, if your mail server uses SpamAssassin, you MUST disable this, as it will prevent XMission's SpamCatcher service from functioning properly.		It is highly recommended you disable any spam scanning that is included in your own mail server when using SpamCatcher to avoid any conflicts. Should you choose to run your own spam scanning software, be sure you allow XMission's IP range (198.60.22.0/24, 166.70.13.0/24 and 166.70.11.0/24). Additionally, if your mail server uses SpamAssassin, you MUST disable this, as it will prevent XMission's SpamCatcher service from functioning properly.

	Example: Zimbra mail servers include SpamAssassin by default. If you run Zimbra for your mail server, be certain to disable the SpamAssassin service.		Example: Zimbra mail servers include SpamAssassin by default. If you run Zimbra for your mail server, be certain to disable the SpamAssassin service.

Jab at 22:38, 25 September 2018

2018-09-25T22:38:09Z

← Older revision		Revision as of 16:38, 25 September 2018
Line 55:		Line 55:

	For a deeper understanding how XMission's spam and virus filtering works, please reference this article on our blog: https://xmission.com/blog/2013/08/14/how-xmission-spam-and-virus-filtering-works		For a deeper understanding how XMission's spam and virus filtering works, please reference this article on our blog: https://xmission.com/blog/2013/08/14/how-xmission-spam-and-virus-filtering-works

			[[Category: Security]]
			[[Category: Email]]

John: /* Disable default spam tools */

2015-09-01T21:45:23Z

Disable default spam tools

← Older revision		Revision as of 15:45, 1 September 2015
Line 32:		Line 32:

	== Disable default spam tools ==		== Disable default spam tools ==

	Many mail server softwares have their own SpamAssassin, ClamAV, or other anti-spam tools built in by default. These need to be disabled for SpamCatcher to work, otherwise the mail server will disregard the XMission SpamCatcher scoring and use its own.

	It is highly recommended you disable any spam scanning that is included in your own mail server when using SpamCatcher to avoid any conflicts. Should you choose to run your own spam scanning software, be sure you whitelist XMission's ip range (198.60.22.0/24, 166.70.13.0/24 and 166.70.11.0/24). Additionally, if your mail server uses SpamAssassin, you MUST disable this, as it will prevent XMission's SpamCatcher service from functioning properly.		It is highly recommended you disable any spam scanning that is included in your own mail server when using SpamCatcher to avoid any conflicts. Should you choose to run your own spam scanning software, be sure you whitelist XMission's ip range (198.60.22.0/24, 166.70.13.0/24 and 166.70.11.0/24). Additionally, if your mail server uses SpamAssassin, you MUST disable this, as it will prevent XMission's SpamCatcher service from functioning properly.

John: /* Disable default spam tools */

2015-09-01T21:40:40Z

Disable default spam tools

← Older revision		Revision as of 15:40, 1 September 2015
Line 34:		Line 34:

	Many mail server softwares have their own SpamAssassin, ClamAV, or other anti-spam tools built in by default. These need to be disabled for SpamCatcher to work, otherwise the mail server will disregard the XMission SpamCatcher scoring and use its own.		Many mail server softwares have their own SpamAssassin, ClamAV, or other anti-spam tools built in by default. These need to be disabled for SpamCatcher to work, otherwise the mail server will disregard the XMission SpamCatcher scoring and use its own.

			It is highly recommended you disable any spam scanning that is included in your own mail server when using SpamCatcher to avoid any conflicts. Should you choose to run your own spam scanning software, be sure you whitelist XMission's ip range (198.60.22.0/24, 166.70.13.0/24 and 166.70.11.0/24). Additionally, if your mail server uses SpamAssassin, you MUST disable this, as it will prevent XMission's SpamCatcher service from functioning properly.

			Example: Zimbra mail servers include SpamAssassin by default. If you run Zimbra for your mail server, be certain to disable the SpamAssassin service.

	== Configuring SpamCatcher==		== Configuring SpamCatcher==

John at 21:21, 1 September 2015

2015-09-01T21:21:52Z

← Older revision		Revision as of 15:21, 1 September 2015
Line 30:		Line 30:

	In addition to the filtering, this service provides customers the ability to change their mail server without having to deal with DNS updates. It also keeps the customer's mail server “hidden” from the world. Customer mail servers will only see SMTP conversations from XMission's network, and can apply appropriate firewall rules.		In addition to the filtering, this service provides customers the ability to change their mail server without having to deal with DNS updates. It also keeps the customer's mail server “hidden” from the world. Customer mail servers will only see SMTP conversations from XMission's network, and can apply appropriate firewall rules.

			== Disable default spam tools ==

			Many mail server softwares have their own SpamAssassin, ClamAV, or other anti-spam tools built in by default. These need to be disabled for SpamCatcher to work, otherwise the mail server will disregard the XMission SpamCatcher scoring and use its own.

	== Configuring SpamCatcher==		== Configuring SpamCatcher==
Line 41:		Line 45:

	Once this information has been updated in the XMission mail system and to your DNS, it will begin working. Total time with XMission is approximately 15 minutes. Your domain name DNS propagation may take longer.		Once this information has been updated in the XMission mail system and to your DNS, it will begin working. Total time with XMission is approximately 15 minutes. Your domain name DNS propagation may take longer.

	~~== Disable default spam tools ==~~

	Many mail server softwares have their own SpamAssassin, ClamAV, or other anti-spam tools built in by default. These need to be disabled for SpamCatcher to work, otherwise the mail server will disregard the XMission SpamCatcher scoring and use its own.

	== Clearing Mail Queue ==		== Clearing Mail Queue ==

John at 21:21, 1 September 2015

2015-09-01T21:21:12Z

← Older revision		Revision as of 15:21, 1 September 2015
Line 21:		Line 21:
	== Pre-emptive Blocking ==		== Pre-emptive Blocking ==

	SpamCatcher can be configured 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.		SpamCatcher can be configured to delete mail at a particular score on the customer's behalf. It is typical for customers to use the provided SpamAssassin headers to filter mail as they see fit.

	~~Customers then configure mail filters on their own~~ mail server ~~for the~~ X-Spam-* headers.		For example, Zimbra mail server software will filter everything that has "X-Spam-Flag: YES" into the "Junk" folder by default.

	To set a custom discard score for your mail server, please contact XMission support.		To set a custom discard score for your mail server, please contact XMission support.
Line 41:		Line 41:

	Once this information has been updated in the XMission mail system and to your DNS, it will begin working. Total time with XMission is approximately 15 minutes. Your domain name DNS propagation may take longer.		Once this information has been updated in the XMission mail system and to your DNS, it will begin working. Total time with XMission is approximately 15 minutes. Your domain name DNS propagation may take longer.

			== Disable default spam tools ==

			Many mail server softwares have their own SpamAssassin, ClamAV, or other anti-spam tools built in by default. These need to be disabled for SpamCatcher to work, otherwise the mail server will disregard the XMission SpamCatcher scoring and use its own.

	== Clearing Mail Queue ==		== Clearing Mail Queue ==

John: /* Pre-emptive Blocking */

2015-09-01T21:01:55Z

Pre-emptive Blocking

← Older revision		Revision as of 15:01, 1 September 2015
Line 21:		Line 21:
	== Pre-emptive Blocking ==		== Pre-emptive Blocking ==

	SpamCatcher can be configured 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. To set a custom discard score for your mail server, please contact XMission support.		SpamCatcher can be configured 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.

			Customers then configure mail filters on their own mail server for the X-Spam-* headers.

			To set a custom discard score for your mail server, please contact XMission support.

	== Easy DNS Handling ==		== Easy DNS Handling ==

John: /* Pre-emptive Blocking */

2015-09-01T20:57:04Z

Pre-emptive Blocking

← Older revision		Revision as of 14:57, 1 September 2015
Line 21:		Line 21:
	== Pre-emptive Blocking ==		== Pre-emptive Blocking ==

	~~By default, any mail with a score of 25 or higher is rejected and thus not delivered to the customer mail server saving bandwidth and mail server load.~~		SpamCatcher can be configured 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. To set a custom discard score for your mail server, please contact XMission support.

	SpamCatcher can be configured 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. . To set a custom discard score, please contact XMission support.

	== Easy DNS Handling ==		== Easy DNS Handling ==

John: smtp feed, smtp service, spam blocking, virus blocking, spam filter, mail server, zimbra, mail spool, mail queue, easy dns, etrn, attachment blocking

2015-02-04T22:08:56Z

smtp feed, smtp service, spam blocking, virus blocking, spam filter, mail server, zimbra, mail spool, mail queue, easy dns, etrn, attachment blocking

New page

== Overview ==

All mail servers require an SMTP service to send and receive email.

XMission [https://xmission.com/spamcatcher SpamCatcher] is an SMTP mail feed which provides spam filtering, virus blocking, and emergency mail spool services. Intended for our customers running their own mail servers, but don't have either the technical ability or resources to install and maintain their own copy of SpamAssassin.

XMission uses a combination of internal and external RBLs (IP and URI), a cluster of SpamAssassin servers running a large custom ruleset, and the ClamAV virus scanner to keep our customers safe. SpamCatcher “applies” these filters and processes to a customer's external mail server environment.

SpamCatcher covers you in the case of an unexpected outage by queuing your mail for up to 8 days. Providing ample time to repair your mail server without losing critical customer messaging.

== Sales Information ==

Product page for [http://xmission.com/spamcatcher SpamCatcher] - $15/mo per domain and can be ordered online or by contacting XMission sales.

== How XMission SpamCatcher Works ==

SpamCatcher service 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 [https://xmission.com/blog/2013/08/14/how-xmission-spam-and-virus-filtering-works RBLs, virus scanning, attachment blocking, 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.

== Pre-emptive Blocking ==

By default, any mail with a score of 25 or higher is rejected and thus not delivered to the customer mail server saving bandwidth and mail server load.

SpamCatcher can be configured 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. . To set a custom discard score, please contact XMission support.

== Easy DNS Handling ==

In addition to the filtering, this service provides customers the ability to change their mail server without having to deal with DNS updates. It also keeps the customer's mail server “hidden” from the world. Customer mail servers will only see SMTP conversations from XMission's network, and can apply appropriate firewall rules.

== Configuring SpamCatcher==

''Please note:'' You must first activate the SpamCatcher service with XMission ''before'' applying these settings to avoid missing any email.

To configure SpamCatcher the following steps are required:

# Point your domain MX record to “''mx.xmission.com''”
# Provide XMission support with the ''Static IP address'' of your mail server.

Once this information has been updated in the XMission mail system and to your DNS, it will begin working. Total time with XMission is approximately 15 minutes. Your domain name DNS propagation may take longer.

== Clearing Mail Queue ==

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 mail server at the specified IP address.

== 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: https://xmission.com/blog/2013/08/14/how-xmission-spam-and-virus-filtering-works