How to Whitelist Expiration Reminder Emails

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 (without the @ symbol) to your email system’s safe-sender list or allow list. Use the format expirationemail.com when entering it into your mail gateway or spam filter.
• 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 Important: These are example IPs only. Always allow-list every sending IP address supplied to you for your specific account configuration, as Expiration Reminder may use multiple IP addresses 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 configure a custom FROM address for notifications, the emails will still originate from Expiration Reminder's sending IP addresses. Ensure all provided sending IPs and the sending domain (expirationemail.com) remain on your allow list, even though the displayed FROM address may show your internal or custom 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 — such as vendors, suppliers, and team members — a brief notification that identifies the sending address (expirationemail.com) and asks them to add it to their safe-sender lists before the first reminder is sent. This reduces the chance that automated reminders will be flagged as spam.

Testing and verification

• After adding the provided IP addresses and domain to your allow lists, send test messages to one or more recipient addresses and confirm the messages arrive in the inbox (not in spam or quarantine).
• 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.