As I mentioned in my previous message, there's no reverse DNS on
vps.qoid.us, which I could imagine some servers caring about.
Greetings,
Ørjan.
On Fri, 27 Dec 2019, omd via agora-official wrote:
On Sun, Dec 22, 2019 at 11:00 PM omd <c.ome...@gmail.com> wrote:
I think at this point there's nothing I can do but wait, and hope
Gmail starts trusting the new server more. Hopefully that doesn't
take long, or I'll have to do something silly like turn on
from-address rewriting.
Well, that didn't work so well. A lot of hosts have continued to
reject or at least throttle mail from the new server:
Dec 27 19:49:15 ec2 postfix/smtp[9751]: C6D7260DAC: host
mx3.mail.icloud.com[17.142.163.12] refused to talk to me: 550 5.7.0
Blocked - see https://support.proofpoint.com/dnsbl-lookup.cgi?ip=52.73.134.173
Dec 27 19:49:19 ec2 postfix/smtp[9753]: 324C160DF5: host
in1-smtp.messagingengine.com[66.111.4.70] refused to talk to me: 451
4.7.1 <ec2-52-73-134-173.compute-1.amazonaws.com[52.73.134.173]>:
Client host rejected: Host
52.73.134.173/ec2-52-73-134-173.compute-1.amazonaws.com has exceeded
the per-day email limit of 40, try again later -
helo=<ip-10-0-0-96.ec2.internal> - RLR001
Dec 27 19:49:30 ec2 postfix/smtp[9749]: 55A7C60E4F:
to=<redac...@gmail.com>,
relay=alt1.gmail-smtp-in.l.google.com[64.233.186.27]:25, delay=420346,
delays=420331/0.01/9.9/5.6, dsn=4.7.28, status=deferred (host
alt1.gmail-smtp-in.l.google.com[64.233.186.27] said: 421-4.7.28
[52.73.134.173 15] Our system has detected an unusual rate of
421-4.7.28 unsolicited mail originating from your IP address. To
protect our 421-4.7.28 users from spam, mail sent from your IP address
has been temporarily 421-4.7.28 rate limited. Please visit 421-4.7.28
https://support.google.com/mail/?p=UnsolicitedRateLimitError to 421
4.7.28 review our Bulk Email Senders Guidelines. x15si32376191pgk.593
- gsmtp (in reply to end of DATA command))
New plan:
- Go back to sending mail from the original server, which at least
didn't get throttled so much.
- *Temporarily* turn on from-address rewriting for all users, so
relayed list messages have headers like
From: So-and-so via agora-business <agora-busin...@agoranomic.org>
Note that several months ago, I enabled an option that performs the
same rewriting only when the original From domain has a strict DMARC
policy, instructing recipients to reject all mail from those domains
unless properly signed – which relayed list messages won't be, because
the list rewrites the subject line. In practice, this only affected
messages from Murphy. But now it's temporarily on for everyone.
- Configure DKIM signing and SPF so that recipients know that the
owner of agoranomic.org authorizes the outgoing messages. This should
avoid the errors that Gmail was returning for the original server.
When I tested by sending a message from an agoranomic.org address to
my Gmail account, it was accepted but sent to spam... *hopefully* the
list is treated no worse.
- Now that the mail server configuration has been fixed to prevent
backscatter, the original server's IP (71.19.146.223) should get off
the Backscatterer.org list in a few weeks, and Gmail's IP semi-block
(which is probably separate from Backscatterer.org, though who knows)
will hopefully expire in a similar time period.
- At that point, hopefully I'll be able turn from-address rewriting
back off and have things go back to normal.
Sorry, I still haven't explained things properly, but I'm a bit
stressed out at the moment. :/