I don’t quite understand what you are saying but I guess this is a translation issue
If you honestly believe that you have done everything required by “gmail” to allow email to pass through their servers?
There is nothing more you can do at this point. The fact that you are even able to pass through to the junk folder should be be a positive. You have no control over the entire block of IP’s that may have onetime or another been flagged for SPAM.
It’s all about “IP Reputation” now. In order for this to work, every IP on the block has to behave.
- lack of information
- lack of logs
- lack of advanced diagnostics
It looks like the OP has to do more to fix this issue himself. The community here has provided many suggestions, let see if the OP follows them.
Its not only blacklist, the IP might have a bad reputation. Test for that.
1 Like
caps seem like your shouting, normally 80’s olds do it.
1 Like
that’s too close for comfort
more often just careless use of CAPS LOCK key - easily done - and easily corrected/edited when the OP re-reads what they posted
1 Like
Well, I got finally 10/10 - and mails to google still bounce due to some PTR issues (according to the bounce)
The only thing I didn’t setup yet (but working on it) is MTA-STS
Google seems to be quite special.
I don’t want to hijack the topic, but is there any PTR related setting in Virtualmin? Seems not, or?
people have different opinions on whether this has a bearing on email delivery, i know it does 
My hostname for my server matches the rDNS/PTR record for the IP it sits on.
This made a difference for my mail not going into the SPAM but going into the inbox.
Mileage may vary
Whoever gave you the IP for the server needs to add the reverse or you may have access to a portal where you can add it. Google will reject if no PTR.
My server management panels has an options to enter reverse DNS. I get all green in mxtoolbox for PTR.
But I found a, well, stupid problem in my SPF record. I wanted to make really good and entered ip6:####… - which I looked up - but didn’t think of Cloudflare, so the ip6 was Cloudflare’s and not mine. After removing ip6:####… from the SPF I can send mails to gmail.
PTR issue is when the mail servers talk to each other, not sure how a cloudflare IP is getting in there. And PTR is not SPF related as far as I know. Maybe google was reject on an other issue.
Maybe that was the tiny bit that burst it. For now it works.
I fully understand pukah’s frustration, or generally for people that don’t do it every day.
is this Google email header tool of any help:
Jeez! Just use mailgun for your SMTP. They monitor all of their sending IPs to ensure they are clean. Just make sure you, too, are sending clean emails, or they will boot you off the platform—that’s another way they keep their deliverability high.
+90% of emails I’ve sent through them go through without a hitch (nothing is 100%).