Den 04-03-2024 kl. 01:17 skrev Gareth Evans via mailop:
Given:
Received: from atlas.bondproducts.com (unknown [23.24.6.165])
by mx6.messagingengine.com (Postfix) with ESMTP id ...
[...]
Received: from users.shellworld.net (users.shellworld.net [50.116.47.71])
by atlas.bondproduct
On Mon 04/03/2024 at 01:41, Gareth Evans wrote:
> ...
> It seems FCrDNS (aka iprev) requires that
>
> "a given IP address has both forward (name-to-address) and reverse
> (address-to-name) [DNS] entries that match each other ... the forward
> and reverse lookup for the sending relay have to matc
From
https://www.mailop.org/best-practices
"Having SPF for your own domains is usually considered a weak signal ..."
Eh?
"... as is filtering on them"
Such as DNS filtering per
https://www.ionos.co.uk/digitalguide/server/security/dns-filtering ?
Can anyone add a little more background/meani
On Mon 04/03/2024 at 01:05, Benny Pedersen via mailop wrote:
> Gareth Evans via mailop skrev den 2024-03-04 01:17:
>
>> Received: from atlas.bondproducts.com (unknown [23.24.6.165])
>> by mx6.messagingengine.com (Postfix) with ESMTP id ...
>
> https://multirbl.valli.org/fcrdns-test/23.24.6.16
Gareth Evans via mailop skrev den 2024-03-04 01:17:
Received: from atlas.bondproducts.com (unknown [23.24.6.165])
by mx6.messagingengine.com (Postfix) with ESMTP id ...
https://multirbl.valli.org/fcrdns-test/23.24.6.165.html one red means
fails
[...]
Received: from users.shellworld
On Sun 03/03/2024 at 18:55, Andy Smith via mailop wrote:
> Hi,
>
> On Sun, Mar 03, 2024 at 05:23:22PM +, Gareth Evans via mailop wrote:
>> (Error NOERROR looking up 23.24.6.165 PTR,Error Error NXDOMAIN looking
>> up 23-24-6-165-static.hfc.comcastbusiness.net. A looking up
>> 23-24-6-16
On Mon 04/03/2024 at 00:17, Gareth Evans wrote:
> if the IP actually resolved.
If the host/domain actually resolved.
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
Once upon a time, Cyril - ImprovMX said:
> Just to clarify, I'm not trying to pin some issue on a company (Google) but
> I'm trying to understand why aiosmtpd seems to follow an RFC that
> appears to be clear on the behavior, that GMail doesn't do but doesn't
> appear to be the only one (as my use
Am Sun, 03 Mar 2024 17:23:22 +
schrieb Gareth Evans via mailop :
> I am curious about the exact mechanism of PTR checks, and couldn't
> find it in RFC5321 so presume it's not actually part of SMTP.
Most server require that the PTR points to a domain name like
mail.example.org and that has the
Hi,
On Sun, Mar 03, 2024 at 05:23:22PM +, Gareth Evans via mailop wrote:
> (Error NOERROR looking up 23.24.6.165 PTR,Error Error NXDOMAIN looking
> up 23-24-6-165-static.hfc.comcastbusiness.net. A looking up
> 23-24-6-165-static.hfc.comcastbusiness.net. A,Error Error NXDOMAIN looking u
I am dealing with a correspondent whose "ultimate" sending mail server's PTR
record contains a non-existent host. This is preventing delivery to gmail.
In this case (headers from a message received elsewhere):
--
Authentication-Results: mx6.messagingengine.com;
[...]
iprev=fail smtp.remote-ip=
11 matches
Mail list logo
