On 2022-07-31 at 13:07:43 UTC-0400 (Sun, 31 Jul 2022 12:07:43 -0500)
John Gateley via mailop <[email protected]>
is rumored to have said:
On 7/31/22 11:38 AM, Michael Rathbun via mailop wrote:
Since you have included none of the information that might have been
used by
the receiving system (your IP? Your HELO string? The domain in the
envelope?
Any domains referenced in the body?) ...
Fair point:
The sending domain is annbauer.com, mx is hosted by
mx.oustrencats.com.
IP addresses:
root@giraffe:~# host mx.oustrencats.com
mx.oustrencats.com has address 50.116.29.164
mx.oustrencats.com has IPv6 address 2600:3c00:e000:323::1
I am not positive on the HELO string, as postfix isn't logging that,
but I would guess it is mx.oustrencats.com with envelope from
[email protected]
I would bet that with the error message you cited, there was no HELO or
envelope sender, because the *connection* was refused.
Again, DKIM, SPF, DMARC and reverse DNS are set up properly enough to
get mail delivered to google.
Google does what Google does. Sympatico clearly does elsewise. Their
servers, their rules.
My guess is that Sympatico got tired of seeing misbehaving Linode IPs in
their logs and you're just collateral damage.
Not sure what you mean about domains referenced in the body, someone
contacted my wife and she was replying.
Some spam filters (e.g. SpamAssassin) parse any URIs out of message
bodies and score based on the reputation of their domains.
Likely not relevant in this case, especially since there was probably no
SMTP traffic sent at all.
--
Bill Cole
[email protected] or [email protected]
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
_______________________________________________
mailop mailing list
[email protected]
https://list.mailop.org/listinfo/mailop
