On 26.10.24 09:41, Pete Long via mailop wrote:
The issue still exists even after the changes I've made as a result of
reading your replies to my original post. The spaces in the DKIM record
were indeed present (I think I counted five altogether in the main string
of characters in the record) but they've now been removed. I've matched
up forward and reverse DNS hostnames for my mail server.
It seems I missed the part of RFC that allows whitespace in DKIM key and
this was not the problem.
[...]
Embarrassingly, I think this issue with GMail is partly down to myself. I
use the GMail account the most for sending test emails and in doing so I
think I've hurt my reputation as far as these servers are concerned. This
wasn't always the case as there seems to have been an update of some kind
at some point in time for Google's mail servers where they are now taking
a more aggressive stance toward incoming email; even if it is totally
legitimate but consists of simple subject lines like the unforgettable
'Testing 123' and of course the classic 'Testing 456', with exactly the
same text in the body.
Are you sure no (spf/dkim) authorized messages from your domain reach google
servers from other sources (users, servers etc)?
If this is indeed the case, how do I contact a human being at Google and
ask them if they will whitelist my static IPv4 address and/or email
address? I can stop using this GMail account for testing but still cannot
email any entity that uses Google's servers.
According to my experience sending IP doesn't change much if your domain
sends spam.
Do I just wait it out?
what do your domain/IP reputations in gmail postmaster tools say?
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
It's now safe to throw off your computer.
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
