Zimbra FAQ - White Label - Revision history

John at 22:40, 10 July 2020

2020-07-10T22:40:04Z

← Older revision		Revision as of 16:40, 10 July 2020
Line 1:		Line 1:
	XMission provides a number of services oriented to resellers, channel partners, and organizations with ~~white~~ label requirements.		XMission provides a number of services oriented to resellers, channel partners, and organizations with private label requirements.

	The following FAQ provides answers to the most common questions. If we are missing anything please send requests to zimbrasales@xmission.com and we will get it added.		The following FAQ provides answers to the most common questions. If we are missing anything please send requests to zimbrasales@xmission.com and we will get it added.
Line 10:		Line 10:
	==Available Mailboxes==		==Available Mailboxes==

	XMission provides two service levels for resellers and ~~white~~ label environments: Basic and Professional. Zimbra Infrastructure customers with a dedicated environment may have additional mailbox levels available based on needs.		XMission provides two service levels for resellers and private label environments: Basic and Professional. Zimbra Infrastructure customers with a dedicated environment may have additional mailbox levels available based on needs.


	==Differences between the Basic and Professional mailboxes?==		==Differences between the Basic and Professional mailboxes?==

	Link a chart or ~~white~~ paper here.		Link a chart or private label paper here.


	==~~White~~ Label Billing & Support==		==Private Label Billing & Support==

	XMission bills the ~~White Label~~ or reseller customer of record. We do not bill the customer.		XMission bills the private label or reseller customer of record. We do not bill the customer.

	A minimum billing amount of $100 p/mo required on ~~white~~ label services. ~~White Label~~ clients are required to maintain one billable email box and one Static IP address.		A minimum billing amount of $100 p/mo required on private label services. Private label clients are required to maintain one billable email box and one Static IP address.

	XMission bills in advance for all services. Mailbox billing for all accounts is added or removed from billing during the first week of each calendar month.		XMission bills in advance for all services. Mailbox billing for all accounts is added or removed from billing during the first week of each calendar month.

	XMission supports the ~~White Label~~ customer or record. XMission does not provide direct support to ~~White Label~~ end user ~~mailboxes~~.		XMission supports the private label customer or record. XMission does not provide direct support to private label end user mailbox holders.

	~~White Label~~ clients can call, email, or use livesupport to contact XMission support services. https://xmission.com/support		Private label clients can call, email, or use livesupport to contact XMission support services. https://xmission.com/support

	==Portable Device Support==		==Portable Device Support==
Line 109:		Line 109:
	== Add New Mail Domain==		== Add New Mail Domain==

	Simply contact zimbrasales@xmission.com with the request to add a new Zimbra domain to your service. Please reference that you are a reseller or ~~white~~ label customer in the email.		Simply contact zimbrasales@xmission.com with the request to add a new Zimbra domain to your service. Please reference that you are a reseller or private label customer in the email.


Line 124:		Line 124:
	==Limit Domain Mailbox Provisioning==		==Limit Domain Mailbox Provisioning==

	XMission can set a hard limit on the number of mailboxes that can be provisioned to a domain. Please contact support@xmission.com with this request. Be sure to indicate that you are a ~~white~~ label customer inside the correspondence.		XMission can set a hard limit on the number of mailboxes that can be provisioned to a domain. Please contact support@xmission.com with this request. Be sure to indicate that you are a private label customer inside the correspondence.

Jab at 22:26, 25 September 2018

2018-09-25T22:26:37Z

← Older revision		Revision as of 16:26, 25 September 2018
Line 201:		Line 201:

	Any sensitive information you need to provide XMission should only be shared using https://secrets.xmission.com. You enter the note information on the ecrets page, create a custom url, and then share that URL with your XMission agent.		Any sensitive information you need to provide XMission should only be shared using https://secrets.xmission.com. You enter the note information on the ecrets page, create a custom url, and then share that URL with your XMission agent.


			[[Category: Zimbra]]

John: /* Migration Assistance */

2018-04-12T17:28:02Z

Migration Assistance

← Older revision		Revision as of 11:28, 12 April 2018
Line 133:		Line 133:
	Depending on the situation XMission may be able to perform migration services for large customers on a consulting basis. Fees will apply.		Depending on the situation XMission may be able to perform migration services for large customers on a consulting basis. Fees will apply.

	~~There are a number of~~ migration ~~methods outlined~~ on ~~the XMission Blog~~: https://xmission.com/blog		Please read the migration articles on our blog: https://xmission.com/blog/?s=migration


	==Delete Mailboxes==		==Delete Mailboxes==

John: /* SPF Record */

2018-04-11T23:02:52Z

SPF Record

← Older revision		Revision as of 17:02, 11 April 2018
Line 105:		Line 105:
	== SPF Record ==		== SPF Record ==

	Point SPF record to "v=spf1 a mx include:_spf.xmission.com ~all"		Point SPF record to "v=spf1 a mx include:_spf.xmission.com ~all" Proper SPF will help prevent your outbound email landing in the recipient's Junk folder.


	== Add New Mail Domain==		== Add New Mail Domain==

John at 22:59, 11 April 2018

2018-04-11T22:59:44Z

← Older revision		Revision as of 16:59, 11 April 2018
Line 90:		Line 90:

	Some clients prefer to use external Spam filtering services or appliances. In this case, you can use the Static IP address provided to you for your gateway (ie mail.example.com) as en entry point. Just configure your spam filtering service to relay mail to your gateway IP, and XMission's internal spam filtering will be bypassed in favor of your external spam filter. Your client's mx records should point to your external spam filtering service.		Some clients prefer to use external Spam filtering services or appliances. In this case, you can use the Static IP address provided to you for your gateway (ie mail.example.com) as en entry point. Just configure your spam filtering service to relay mail to your gateway IP, and XMission's internal spam filtering will be bypassed in favor of your external spam filter. Your client's mx records should point to your external spam filtering service.

			* SMTP:

			It is highly advisable for customers to set incoming/outgoing servers as your custom URL (mail.example.com). However, we understand that some customers require smtp.example.com to replace their existing records and make transition easier. In this case create the A record pointing to the unique url (mail.example.com) or to your static IP. If you require your incoming / outgoing servers to have different hostnames than mail.example.com you must notify XMission in advance before migration.

	Note: Where "example.com" is used in the above instructions please replace with your specific mail domain.		Note: Where "example.com" is used in the above instructions please replace with your specific mail domain.


	==Point MX Records==		==Point MX Records==

	As noted above, you can point your MX records to mx.xmission.com or if you are using an A record point them to mx.example.com.		As noted above, you can point your MX records to mx.xmission.com or if you are using an A record point them to mx.example.com (where example.com is your domain).


			== SPF Record ==

			Point SPF record to "v=spf1 a mx include:_spf.xmission.com ~all"

John: /* White Label Billing & Support */

2016-10-31T18:49:22Z

White Label Billing & Support

← Older revision		Revision as of 12:49, 31 October 2016
Line 22:		Line 22:
	XMission bills the White Label or reseller customer of record. We do not bill the customer.		XMission bills the White Label or reseller customer of record. We do not bill the customer.

	A minimum billing amount of $100 p/mo required on white label services.		A minimum billing amount of $100 p/mo required on white label services. White Label clients are required to maintain one billable email box and one Static IP address.

			XMission bills in advance for all services. Mailbox billing for all accounts is added or removed from billing during the first week of each calendar month.

	XMission supports the White Label customer or record. XMission does not provide direct support to White Label end user mailboxes.		XMission supports the White Label customer or record. XMission does not provide direct support to White Label end user mailboxes.

John: /* White Label Billing & Support */

2016-10-31T18:43:06Z

White Label Billing & Support

← Older revision		Revision as of 12:43, 31 October 2016
Line 26:		Line 26:
	XMission supports the White Label customer or record. XMission does not provide direct support to White Label end user mailboxes.		XMission supports the White Label customer or record. XMission does not provide direct support to White Label end user mailboxes.

			White Label clients can call, email, or use livesupport to contact XMission support services. https://xmission.com/support

	==Portable Device Support==		==Portable Device Support==

John at 18:41, 31 October 2016

2016-10-31T18:41:56Z

← Older revision		Revision as of 12:41, 31 October 2016
Line 16:		Line 16:

	Link a chart or white paper here.		Link a chart or white paper here.


			==White Label Billing & Support==

			XMission bills the White Label or reseller customer of record. We do not bill the customer.

			A minimum billing amount of $100 p/mo required on white label services.

			XMission supports the White Label customer or record. XMission does not provide direct support to White Label end user mailboxes.

John: /* Suggested A Records */

2016-09-14T18:32:09Z

Suggested A Records

← Older revision		Revision as of 12:32, 14 September 2016
Line 67:		Line 67:
	It is advisable to create an A record entry for the following:		It is advisable to create an A record entry for the following:

	Email Gateway:		* Email Gateway:

	The A record for your email gateway domain, mail.example.com, will point to the Static IP address XMission provides you.		The A record for your email gateway domain, mail.example.com, will point to the Static IP address XMission provides you.

	MX with XMission Spam Filtering:		* MX with XMission Spam Filtering:

	Create an A record for mx.example.com and point it to 166.70.12.20, IP address for mx.xmission.com. You then will point all your customer domains to mx.example.com. (Point your domain there as well.) This makes sure that your customer emails go through XMission spam filtering service. It is important to remove the mx setting for the previous mail provider on your domains.		Create an A record for mx.example.com and point it to 166.70.12.20, IP address for mx.xmission.com. You then will point all your customer domains to mx.example.com. (Point your domain there as well.) This makes sure that your customer emails go through XMission spam filtering service. It is important to remove the mx setting for the previous mail provider on your domains.

	MX with External Spam Filtering:		* MX with External Spam Filtering:

	Some clients prefer to use external Spam filtering services or appliances. In this case, you can use the Static IP address provided to you for your gateway (ie mail.example.com) as en entry point. Just configure your spam filtering service to relay mail to your gateway IP, and XMission's internal spam filtering will be bypassed in favor of your external spam filter. Your client's mx records should point to your external spam filtering service.		Some clients prefer to use external Spam filtering services or appliances. In this case, you can use the Static IP address provided to you for your gateway (ie mail.example.com) as en entry point. Just configure your spam filtering service to relay mail to your gateway IP, and XMission's internal spam filtering will be bypassed in favor of your external spam filter. Your client's mx records should point to your external spam filtering service.

Secretions: /* Suggested A Records */

2016-09-14T16:47:55Z

Suggested A Records

← Older revision		Revision as of 10:47, 14 September 2016
Line 69:		Line 69:
	Email Gateway:		Email Gateway:

	The A record for your email gateway domain, ~~email~~.example.com, will point to the Static IP address XMission provides you.		The A record for your email gateway domain, mail.example.com, will point to the Static IP address XMission provides you.

	MX with XMission Spam Filtering:		MX with XMission Spam Filtering:
Line 75:		Line 75:
	Create an A record for mx.example.com and point it to 166.70.12.20, IP address for mx.xmission.com. You then will point all your customer domains to mx.example.com. (Point your domain there as well.) This makes sure that your customer emails go through XMission spam filtering service. It is important to remove the mx setting for the previous mail provider on your domains.		Create an A record for mx.example.com and point it to 166.70.12.20, IP address for mx.xmission.com. You then will point all your customer domains to mx.example.com. (Point your domain there as well.) This makes sure that your customer emails go through XMission spam filtering service. It is important to remove the mx setting for the previous mail provider on your domains.

	MX ~~without XMission~~ Spam Filtering:		MX with External Spam Filtering:

	Some clients prefer to use external Spam filtering services or appliances. In this case you ~~will create an A record~~ for mx.example.com ~~and~~ point it to your ~~Static~~ IP ~~address~~. ~~You then~~ point ~~all your customer domains to this mx entry. It is important~~ to ~~remove the mx setting for the previous mail provider on~~ your ~~domains~~.		Some clients prefer to use external Spam filtering services or appliances. In this case, you can use the Static IP address provided to you for your gateway (ie mail.example.com) as en entry point. Just configure your spam filtering service to relay mail to your gateway IP, and XMission's internal spam filtering will be bypassed in favor of your external spam filter. Your client's mx records should point to your external spam filtering service.

	Note: Where "example.com" is used in the above instructions please replace with your specific mail domain.		Note: Where "example.com" is used in the above instructions please replace with your specific mail domain.