Applies to: Live@edu
Topic Last Modified: 2011-10-06
If you have an on-premises messaging system, you can add the IP addresses of internal e-mail servers to a safelist to make sure that e-mail that comes from your on-premises messaging system isn't treated as spam. Safelists are also known as whitelists.
How do you add IP addresses to a safelist? It depends on whether your organization is using Microsoft Forefront Online Protection for Exchange (FOPE) or Outlook Live to manage safelists. Here’s how to tell:
In the Live@edu Service Management portal, on the Mail delivery page, look at the Safelist mail servers
-
If you see a link to “Outlook Live Control Panel”, your organization is using FOPE, and this topic doesn't apply to you. To learn how to manage safelists with FOPE, see Inbound Safe Listing Scenario.
-
If you see a link to Manage IP safelists, read the rest of this topic to learn how to manage Outlook Live safelists.
Outlook Live safelists
You submit IP addresses to be added to the Outlook Live safelist at the Live@edu Service Management Portal. You add the IP address to the internal mail servers list.
Internal mail servers generate e-mail messages that are sent to Outlook Live from your on-premises messaging system. An internal mail server IP address is always a statically assigned public IP address.
IP addresses on the internal mail servers list don't undergo any connection filtering or content filtering. Make sure that servers on this list are trusted to never send junk e-mail and that they don't relay Internet mail that hasn't already been filtered for spam to Outlook Live users.
If your server meets any of the following criteria, add the IP address to the internal mail servers list:
-
You have a gateway server, a server that relays e-mail from the Internet, that is dedicated to relaying e-mail messages from your on-premises mail servers.
-
Your internal mail servers have private IP addresses.
-
You have an on-premises e-mail server that relays e-mail to Outlook Live.
Important You can't add third-party SMTP IP addresses to the Outlook Live safelists on behalf of your organization. The most effective method to guarantee e-mail delivery into Outlook Live is to encourage third-parties to become a certified sender. For more information about the external service, see Sender Score Certified.
To maintain high quality service, Live@edu requires you have sole sending rights on the public IP addresses that you submit for safelisting on behalf of your organization. If your organization isn't listed as the sole owner in the public IP addresses, you must submit additional information from the ISP or sole owner of the IP address that verifies that your organization is the sole sender. An e-mail from the contact address in the IP Whois record is sufficient verification. The e-mail must state that your organization is the sole sender for the IP address.
To learn how to submit verification, see How to verify sole sending rights on your domain IP address.
Add IP addresses to IP safelists in Live@edu
To add your organization's IP addresses to Outlook Live safelists, after you enroll your organization with Microsoft Live@edu, follow these steps.
-
Verify that you have sole sending rights. To learn how to submit verification, see How to verify sole sending rights on your domain IP address.
-
In the Live@edu Service Management Portal, click Mail Delivery.
-
Click Manage IP safelists.
-
In the Add internal mail servers section, type the IP addresses of your internal mail servers.
-
Click Submit. You can submit up to five IP addresses per request.
Important It may take up to three business days to update the safelist. After you submit your request, you can view the status of the IP addresses you have submitted on the Mail Delivery page in the Live@edu Service Management Portal. If you don't see the status updated in the portal in three business days, contact Live@edu Partner Center.
You can add a total of 250 IP addresses to the Outlook Live safelists. To delete an IP address from the Outlook Live safelists, select it and then click 
.
