Email Anti-Spam tools - Domain-based Message Authentication, Reporting & Conformance (DMARC)
Applicable Product:
All
Summary:
Many of the LTG/PeopleFluent SaaS applications may be configured to send using your company’s domain as the originator (FROM field). The PF Hosting team makes every effort to reduce SPAM, improve the delivery of messages from our email systems on your behalf, and maintain a solid email reputation for our mail servers. If your company has configured your SaaS product to use your domain name, we need to partner with your IT team to ensure the highest level of delivery and greatest level of anti-spam protection.
Detailed Information:
Anti-Spam Protocol Configuration
Email sent from LTG/PeopleFluent SaaS applications with a FROM address using your company’s domain may not be successfully delivered or may be marked as SPAM by both your company’s email systems and/or a third party’s email system.
The best way to solve this is to designate all LTG/PeopleFluent email servers as authorized to send email on your company’s behalf.
A number of email anti-spam protocols have been defined to help address this problem. Details below are for the Domain-based Message Authentication, Reporting & Conformance (DMARC) method.
AntiSpam Technologies used at LTG
LTG utilizes SPF, DKIM and DMARC Anti-SPAM standards for most of our products. The steps on this page will ensure that mail from our SaaS systems are seen as SPF/DKIM/DMARC compliant. Configuring your systems to validate email via these technologies is highly recommended and the preferred method to ensure email delivery.
Please check your email system configuration to ensure your company is leveraging our most recent practices.
You may also set up an automated DNS TXT query to obtain the date of our most recent best practice changes:
nslookup -type=txt last-updated.ltg.email.
OR
host -t txt last-updated.ltg.email.
Domain-based Message Authentication, Reporting & Conformance (DMARC)
Domain-based Message Authentication, Reporting & Conformance (DMARC) policies allow domains to publish a policy for accepting mail from their domain. The policy allows recipient mail systems to decide what to do when emails are not passing SPF or DKIM but still originates from a known system.
SaaS customers wishing to have emails originated from LTG/PeopleFluent systems sent as DMARC compliant should first complete SPF and DKIM setup. Please let us know you would like to complete DMARC configuration when submitting your DKIM support ticket.
For more information on DMARC, please visit https://dmarc.org/
Please note that while LTG/PeopleFluent can provide guidance on email configurations, we cannot guarantee that email will always be delivered in a timely manner. Email standards are designed to use multiple delivery techniques, redundant or intermediate email servers, and may result in delays when reattempting message delivery. In some circumstances, systems outside our control may outright refuse delivery based on SPAM policies, system configurations or temporary server issues.
Note: If you are unable to utilize one of these standards, our secondary recommendation is to whitelist our servers. Recipients outside your organization may not have mail delivered successfully from our SaaS services if you rely on whitelisting alone.
Also, while we may use a specific group of servers in most circumstances, our disaster recovery and load balancing practices may send mail using any of our email systems listed on this page. Whitelisting will only be successful if it includes all our current email system addresses.
Additional information can be found at: https://info.ltg.email/