Hi Appian Community,
Any cloud customers experienced this issue?
Our clients report not receiving our outbound emails that have been custom configured already in the Sender field (i.e. not Process, Process Designer, Process Model, or Process Initiator that will create different sender names) but a custom and consistent sender name.
We have verified that the DNS in the SPF records contain all of our Appian site names.
We also enabled DKIM to contain a verified email signature.
However, whenever our shared Appian mail server IPs get added to the Outlook/Microsoft global block list, our outbound emails get blocked.
Any resolution that anybody implemented to get around this issue?
Thanks in advance.
Discussion posts and replies are publicly visible
I suggest to open a support case to discuss this issue.
But, this makes me wonder. Isn't it the idea of a block list to block things?
dcao said:However, whenever our shared Appian mail server IPs get added to the Outlook/Microsoft global block list, our outbound emails get blocked.
Raise an Appian Support ticket with the blocked IP (from your bounce/NDR) and ask them to request Microsoft delisting.
We can actually request to delist it by ourselves. The issue is when another Appian customer generates spam emails and someone can add the shared Appian mail IPs to the block list again. causing collateral damage to my organization
Currently waiting for their response. The issue is as a cloud customer, the mail IPs are shared between multiple customers in the same region as my organization. So when another Appian cloud customer generates spam emails and gets reported to the Outlook block list, my organization gets the collateral damage
dcao said:when another Appian cloud customer generates spam emails
This is a pretty important allegation if true, and should probably be reported to Appian.
We can request Microsoft delisting ourselves, but since Appian Cloud uses shared outbound IPs, another customer’s spam can get the same IP re-blocked and cause collateral impact.