IT Resource for Email Deliverability and Application Specific Information

Jonas Oppedal

Updated June 17, 2019 19:17

This documentation is intended for someone with a technical background (e.g. an IT professional). It covers two important topics to ensure optimal performance and reliability of Meltwater’s Media Intelligence products. These topics are Email Deliverability and Application Specific Information.

Email Troubleshooting

Spam filters are the most common reason causing email delivery issues. Spam filter settings are commonly defined by a company’s IT department, and default settings vary by email provider. Both the size of the email and/or certain words can trigger the spam detection filter and prevent emails from being delivered.

Whitelisting

Confirm with the Meltwater user on your company’s account that they have registered a valid email address and also have them check their spam folder before proceeding with a whitelisting process.

Whitelisting emails from Meltwater can be done by registering our mail server names and corresponding IP addresses. We currently use two vendors (Oracle Dyn and BaseFarm) for email. Below is a complete list of the information you need for whitelisting:

Mail server name

Mail server IP

Provider

mtaout-161-pao.meltwaterpress.com

216.146.32.161

Oracle Dyn (US)

mtaout-188-pao.meltwaterpress.com

216.146.32.188

Oracle Dyn (US)

mtaout-187-pao.meltwaterpress.com

216.146.32.187

Oracle Dyn (US)

mtaout-186-pao.meltwaterpress.com

216.146.32.186

Oracle Dyn (US)

mtaout-185-pao.meltwaterpress.com

216.146.32.185

Oracle Dyn (US)

mag-mail03.osl.basefarm.net

81.93.173.201

Basefarm (Norway)

mag-mail04.osl.basefarm.net

81.93.164.103

Basefarm (Norway)

Note: If you have regional restrictions set up on your email server, please be aware that our emails are coming from email servers in the US and Norway (see details in the table above).

Email Authentication: DMARC, SPF, and DKIM

DMARC ensures that legitimate email is properly authenticating against established DKIM and SPF standards and that fraudulent activity appearing to come from domains under the organization’s control.

SPF and DKIM are key components to implement a DMARC policy. They help validate a third-party domain and prevent email spoofing. These records can be obtained through Meltwater’s Support team. See “How to Proceed” section below.

Email spoofing is the forgery of an email header so that the message appears to have originated from someone or somewhere other than the actual source. Email spoofing is a tactic used in phishing and spam campaigns because people are more likely to open an email when they think it has been sent by a legitimate source. Learn more about email authentication here.

In order to improve email deliverability (reduce soft bounces) a validation process is required. Meltwater can support this through Dyn (owned by Oracle), our trusted email partner.

A description of the issue the Meltwater user is experiencing (e.g. “Email john.doe@companyname.com is not being delivered”)

Meltwater Support will provide you with SPF and DKIM validation keys via Dyn

Ensure proper configuration of the SPF and DKIM keys on your public DNS record

Provide confirmation to your Meltwater user that the implementation has been completed and ask them to send a test email to ensure that the email is received. The test email should include:

one recipient with your organization’s email domain (internal) and

one recipient with a different domain (external)

If the emails were not received, or if you are having trouble configuring the SPF and DKIM records, please contact Meltwater Support by replying to the original support ticket.

Application Specific Information

Protocols

Underlying security around HTTPS used the Media Intelligence Platform

Protocol

Supported

TLS 1.2

YES

TLS 1.1

YES

TLS 1.0

YES

Content Delivery Network

Meltwater uses Akamai.

Cookies

The user’s browser must have the cookies enabled. The Media Intelligence Platform will not function correctly without cookies enabled.

Browser Support

We support the current and previous major releases of Chrome, Firefox, Safari, Edge and Internet Explorer (IE) on a rolling basis. Each time a new major version is released, we begin supporting that version and we stop supporting the third-most recent version.

By 'major', we mean the leftmost number in the version numbering scheme. Click here for more details.