El 2/2/19 a las 6:20, listacco...@starionline.com escribió:
I'll play the whack-a-mole game of changing the server's IP address,
but I'm thinking of taking some action on this end, such as delaying
incoming gmail to our server with a response that it's being delayed
because Google is a piss poor net citizen, and that their email will
be delayed from 1 to 72 hours. I know, small chance of it being seen,
but considering the lack of other alternatives.
At the very least, the end gmail user trying to send to us can open up
a ticket. They seem to pay more attention to end user problems than
service providers.
Delaying mail coming from google, IMHO, is not going to improve the
initial situation, that your emails are not being delivered to google
customers. I've been there, I know how you feel. We too thought about
doing that (to hotmail in this case), but at the end that would have
ended in having lots of customers complaining about not getting incoming
emails in time from hotmail.com users.
At the end, we decided to change IPs, have a fresh start, r*emove
one-and-for-all any non-encrypted communication* *(I've noticed your
company still accept passwords on clear channels)*, and protect
yourselves from hijacked accounts. One of the things we do here: most
hijacked accounts connect and send emails from different countries. We
geolocate successful logins and automatically block accounts if they
send emails from more than 4 countries in a 24-hour period. Check this
postfwd plugin: https://github.com/Vnet-as/postfwd-anti-geoip-spam-plugin
Good luck!
Ignacio
