Reach out to Mailfence to delist our sending IPs

[kewisch]

We've had some trouble sending email to Mailfence users. I've contacted their support and asked for our IP range to be delisted, and to figure out what service they are using that might list us in the first place.

gz#6712

(related to Zendesk ticket #6712)

[kewisch]

I heard back from them, and realized I made the wrong request. Our Thundermail IPs are not blocked, but what is likely actually going on is that the account mails we send via Amazon SES are being dropped.

I think we need to investigate on our end:

• Which IPs is Amazon SES using in our configuration? If a dynamic pool can we narrow it down?
• Is it possible for SES to use one of our dedicated IPs, though not one currently configured for customers?
• Do we have all the dmarc/dkim/spf configured correctly for these email sends?

Then we can get back to Mailfence on if they are blocking our account mails, and what range they may need to unblock.

[flamingspaz]

Which IPs is Amazon SES using in our configuration? If a dynamic pool can we narrow it down?

We use dyanmic IPs

Is it possible for SES to use one of our dedicated IPs, though not one currently configured for customers?

Yes, this is the only way to do it. SES has it's own dedicated IP leases. It's additional cost so @kewisch or @mzeier can approve and I can make the switch

Do we have all the dmarc/dkim/spf configured correctly for these email sends?

They are all incorrectly configured. Fixing now

[mzeier]

@flamingspaz Let's do it. Cost is minimal for the value.