It appears that Renaud Allard via mailop said:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>
>
>On 2/1/24 10:32, Eduardo Díaz Comellas via mailop wrote:
>> Hi,
>>
>> I've got a customer complaining that they don't receive emails from Meta
>> for password reset. We have tracked down this to see that a lot of thi
It would be helpful if Meta used a better PTR naming convention for
these servers.. ;)
host 66.220.155.136
136.155.220.66.in-addr.arpa domain name pointer
66-220-155-136.mail-mail.facebook.com.
Not sure who dreamed up that one..
On 2/1/24 02:18, Philip Paeps via mailop wrote:
On 2024-02-01
On 2024-02-01 17:32:14 (+0800), Eduardo Díaz Comellas via mailop wrote:
I've got a customer complaining that they don't receive emails from
Meta for password reset. We have tracked down this to see that a lot
of this servers are blacklisted in popular blacklists.
[...]
I usually don't care wh
On 2/1/24 10:32, Eduardo Díaz Comellas via mailop wrote:
Hi,
I've got a customer complaining that they don't receive emails from Meta
for password reset. We have tracked down this to see that a lot of this
servers are blacklisted in popular blacklists.
Let's face it, if you are using 0sp
On Thu, Feb 01, 2024 at 10:32:14AM +0100, Eduardo Díaz Comellas via mailop
wrote:
>
> Btw, how do you deal with this big players' blacklist problems?
One (possibly naive) option is to extract from SPF the outbound MXes for
domains you want to receive mail from,
such as what I describe in
http
Hi,
I've got a customer complaining that they don't receive emails from Meta for
password reset. We have tracked down this to see that a lot of this servers are
blacklisted in popular blacklists.
A small subset of blacklisted addresses are:
66.220.155.136
66.220.155.140
66.220.155.142
66.220.1