Skip to content
English
Customer portal
  • There are no suggestions because the search field is empty.

How to Whitelist Expiration Reminder Emails

Whitelist @expirationemail.com and all provided sending IPs, test delivery, and ask recipients to mark reminders as "Not Spam".

This article explains what to whitelist so Expiration Reminder messages reach recipients reliably and steps you can take to improve deliverability.

Summary

  • Add our sending IP(s) and sending domain to your allow lists and safe-sender lists.
  • Encourage recipients to mark messages as “Not Spam” (or equivalent).
  • When using a custom FROM address, expect messages may originate from more than one sending IP; whitelist all provided IPs and the domain.

What to whitelist

  • Sending domain: @expirationemail.com — add this domain to your email system’s safe-sender list or allow list.
  • Sending IP addresses: add the service IPs provided to your mail server/ firewall/ spam filter allow list. Example IPs that may be used include:
    • 134.128.115.33
    • 149.72.210.175 (Whitelist every sending IP supplied to you for your configuration — multiple IPs can be used for delivery.)

Recommended steps for IT administrators

  1. Add sending IP(s) to allow list
    • Insert each provided sending IP into your mail gateway, firewall, or spam filter allow/whitelist so messages from those addresses are accepted.
  2. Add sending domain to safe senders
    • Add @expirationemail.com to your spam filter or email system’s safe-sender or allow list to reduce filtering based on domain reputation.
  3. Permit emails that use a custom FROM address
    • If you enable a custom FROM address for notifications, ensure the above sending IPs and the sending domain are whitelisted — messages may still come from the service’s sending IPs even when the displayed FROM address is your internal address.
  4. Train mail filters by marking valid messages as safe
    • Ask users to mark quarantined or filtered messages from the sending domain as “Not Spam” or “Safe.” This helps the system learn and improves future deliverability.
  5. Notify recipients before enabling notifications
    • Send recipients (vendors, suppliers, team members) a short notice naming the sending address or domain and asking them to add it to their safe-sender lists. This reduces confusion and the likelihood that reminders will be treated as spam.

Testing and verification

  • After whitelisting the provided IP(s) and domain, send test messages and confirm delivery to recipients’ inboxes.
  • If test messages arrive from more than one IP, ensure all observed sending IPs are added to your allow list.

Best practices

  • Whitelist both domain and any sending IPs provided to you rather than relying on only one method.
  • When requesting IPs to whitelist, use the full list of IPs provided for your configuration and update allow lists if additional IPs are supplied later.
  • Combine technical whitelisting with user education (safe-sender markings and prior notice) for the most reliable delivery.

Conclusion To ensure reliable delivery of Expiration Reminder notifications: whitelist the sending domain @expirationemail.com, add all provided sending IP addresses to your allow list, verify delivery with tests, and ask recipients to mark messages as “Not Spam.” When using a custom FROM address, whitelist the service’s sending IPs as messages may originate from multiple IP addresses.