[exim] route to smarthost only emails that would be send to …

Top Page
Delete this message
Reply to this message
Author: krzf83@gmail.com
Date:  
To: exim-users
Subject: [exim] route to smarthost only emails that would be send to MX dns ending with .google.com
Is there any way to route outgoing emails via smarhost but only if
target MX has specific string in its dns name?

reason:
google/gmail blocked some wide range of IPs recently and in it there
is one of my servers. I got another IP from datacenter (which did cost
me) and it is also blocked (its very similar, diffrent with only last
segment). I want to route emails via my other server (smarthost). I'm
doing this now for recipients @gmail.com but google hosts many
domains, user domains (google apps) and there is no published list of
those. Only way to find out if mail at domain is hosted at google is
by looking at the MX records (for example gmail-smtp-in.l.google.com).
So can I route to smathost only emails that would be sent to MX that
ends with .google.com somehow?
And yes, I tried contacting google at postmaster (this time and in the
past) - they never ever reply.

Connecting to gmail-smtp-in.l.google.com [74.125.136.27]:25 from
148.251.x.x ... failed: Connection refused
LOG: MAIN
gmail-smtp-in.l.google.com [74.125.136.27] Connection refused
Connecting to alt1.gmail-smtp-in.l.google.com [74.125.200.27]:25 from
148.251.x.x ... failed: Connection refused
LOG: MAIN
alt1.gmail-smtp-in.l.google.com [74.125.200.27] Connection refused
Connecting to alt2.gmail-smtp-in.l.google.com [74.125.23.27]:25 from
148.251.x.x ... failed: Connection refused
LOG: MAIN
alt2.gmail-smtp-in.l.google.com [74.125.23.27] Connection refused
Connecting to alt3.gmail-smtp-in.l.google.com [173.194.72.27]:25 from
148.251.x.x ... failed: Connection refused
LOG: MAIN
alt3.gmail-smtp-in.l.google.com [173.194.72.27] Connection refused
Connecting to alt4.gmail-smtp-in.l.google.com [74.125.25.27]:25 from
148.251.x.x ... failed: Connection refused
LOG: MAIN
alt4.gmail-smtp-in.l.google.com [74.125.25.27] Connection refused