Menu
Reply
  • 4
  • 0
  • 0
gormanm
Joining in
155 Views
Message 1 of 7
Flag for a moderator

Virgin Media IP block listed in RBL causing gmail to flag mail as spam

I've verified that mail sent from a third-party domain to gmail is getting flagged as spam as a Virgin Media IP is listed in the headers as the originator. My mail provider has confirmed that the sending IP address from Virgin Media has been flagged as having a poor reputation for sending spam and this can be confirmed at https://mxtoolbox.com/SuperTool.aspx?action=blacklist%3a37.228.229.96&run=emailheaders . The source IP block definitely belongs to Virgin Media according to the WHOIS database, specifically the block 37.228.224.0 - 37.228.255.255. Can this be checked out please to establish why the IP block has a poor reputation and get it removed please? I've opened a ticket with gmail itself to see can my sending domain be whitelisted regardless of the source IP but the response rate from their support is variable. My mail provider also has a ticket open to ensure that their own IPs are not similarly listed.

Thanks

0 Kudos
Reply
  • 2.75K
  • 302
  • 897
Superuser
Superuser
150 Views
Message 2 of 7
Flag for a moderator

Re: Virgin Media IP block listed in RBL causing gmail to flag mail as spam

Might be better directed to Virgin Media, Ireland.

0 Kudos
Reply
  • 4
  • 0
  • 0
gormanm
Joining in
144 Views
Message 3 of 7
Flag for a moderator

Re: Virgin Media IP block listed in RBL causing gmail to flag mail as spam

Done, their forum appears to be on boards.ie, I was not aware there was geographic-specific forums. Thanks for the prompt response!

0 Kudos
Reply
  • 15.88K
  • 881
  • 5.99K
Superuser
Superuser
127 Views
Message 4 of 7
Flag for a moderator

Re: Virgin Media IP block listed in RBL causing gmail to flag mail as spam

I just wanted to share my thoughts on this.

1. Tell your mail provider to learn how black lists work.
2. Consider having a read of my post here https://community.virginmedia.com/t5/Email/Ravenstar-s-Email-FAQ-s/m-p/2420093/highlight/true#M12965...

Once you've read that you'll understand that Virgin Media Ireland will NOT get that block delisted.

The IP block is in Spamhaus' Policy Block List (PBL)

These are addresses that are allocated by DHCP or otherwise do not run MAIL SERVERS.

I note you said you are using a third party mail provider.  Any good provider should know that what matters is whether their mail servers are blacklisted, NOT the original client IP - In fact I spent a few months on these forums getting Virgin Media to acknowledge that fact myself.

While this Forum is for Virgin Media UK customers, I'm willing to help anyone with email issues myself.  It might be handy if you post your email headers of a mail that's reached Gmail - Remove the leading parts of any email addresses but leave the domains in.  I should be able to give you an independent view of why it's ended up in the Gmail spam folder.

Tim

P.S.  I have a reasonable understanding of email and factors that can affect deliverability such as DMARC DKIM and SPF.as well as my own mail server (who needs third parties ROFL)

________________________________________


Only use Helpful answer if your problems been solved.

0 Kudos
Reply
  • 4
  • 0
  • 0
gormanm
Joining in
118 Views
Message 5 of 7
Flag for a moderator

Re: Virgin Media IP block listed in RBL causing gmail to flag mail as spam

My mail provider is aware of the RBLs and in fact it was them that pointed out the source IP may be problematic but acknowledged that some of their own internal IPs had been similarly listed and that has since been rectified as part of a ticket I opened with them. It'll remain to be seen if gmail pays attention to the originating IP or the IPs of the mail provider. I imagine not for the reasons you point out (e.g. IPs fronting as NAT for home internet is unlikely to be a legit SMTP server) but gmails policies are a bit of a black hole and this is not the first time I've heard of mailing list users ending up in spam folders.

Thanks for taking a look!

Delivered-To: xxxxxx@gmail.com
Received: by 2002:a2e:2d12:0:0:0:0:0 with SMTP id t18-v6csp1072733ljt;
        Wed, 9 Jan 2019 11:42:45 -0800 (PST)
X-Google-Smtp-Source: ALg8bN5sJAHLLg7Hd9VOLm7WJCXg5DChGxwcWepS255IW460VMGanYdc4ZNCqED/HU5r3/pihS/d
X-Received: by 2002:a17:906:881:: with SMTP id n1-v6mr5600432eje.7.1547062965694;
        Wed, 09 Jan 2019 11:42:45 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1547062965; cv=none;
        d=google.com; s=arc-20160816;
        b=O69LUR2uxvLciOkO4C4xVy4bOf4pebQyFgOq/qgK78PzVo24XGwZ/BpxT9cgni/RHA
         aVHiy+xKDpYBbnN48otweR2shElnL6gPHTVids7C2BKOY2qJRG8U/EIirPaUyC+Qzqv/
         K2RnuqNdZjY72+CPWSR3Px+86QhHuJle2tZBRiWsfWId19DuHGHqtXa0ddPM/+iTk+2P
         406pD7nnckUiDUjfqcaglPpIUXUd/Ey1uE0JwomssDlUlWLz6672VKJezWXTByGUxJfe
         Ty++0Mml5s/txAJkDwR0uihG9W5yUq9LifLA67eYw0HcO8fFNR+0YZId+NenpxrOKfDw
         6TCQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=user-agent:content-disposition:mime-version:message-id:subject:to
         :from:date;
        bh=uDhm+jYcGdmsOUKIAXmt8UXFm0/zPoM7JxosCp+BIrE=;
        b=GteuGVzgnzTYuvzBtisypd75OiMPFZ3v7O8wnFLISftRTkZOV979jXohRrJIJPKMSl
         MmpyGgIGMTvb65I/kBbl5rKozCGpg76rfUkN2li89LZYWZ0HJ3ybUABIzyZFUeOQbQLQ
         pKaPiS5L/4oICTYb+Qv2+6GWMpTwxwYTB6TTm3ea/Bm6EIYsEeBKVhUHWJtacK3Exx/3
         OxpjvvZiVupV2bxFriok6v1TQ0c76X0fMKIiGAG7B00M4k3JBRZAjOyHNdV0iIC4RZhj
         aTPQYm7F//XePNvVHsun1V6KNObUTKM8JNTCNRKWJLjBaFWDRN7DGOjuwjzMZ7a+3KGc
         LRxg==
ARC-Authentication-Results: i=1; mx.google.com;
       spf=pass (google.com: domain of xxx@techsingularity.net designates 46.22.139.230 as permitted sender) smtp.mailfrom=xxx@techsingularity.net
Return-Path: <xxx@techsingularity.net>
Received: from outbound-smtp13.blacknight.com (outbound-smtp13.blacknight.com. [46.22.139.230])
        by mx.google.com with ESMTPS id 34si319051edj.156.2019.01.09.11.42.45
        for <xxxxxx@gmail.com>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 09 Jan 2019 11:42:45 -0800 (PST)
Received-SPF: pass (google.com: domain of xxx@techsingularity.net designates 46.22.139.230 as permitted sender) client-ip=46.22.139.230;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of xxx@techsingularity.net designates 46.22.139.230 as permitted sender) smtp.mailfrom=xxx@techsingularity.net
Received: from mail.blacknight.com (unknown [81.17.254.26])
        by outbound-smtp13.blacknight.com (Postfix) with ESMTPS id 346671C188E
        for <xxxxxx@gmail.com>; Wed,  9 Jan 2019 19:42:45 +0000 (GMT)
Received: (qmail 20492 invoked from network); 9 Jan 2019 19:42:45 -0000
Received: from unknown (HELO techsingularity.net) (xxx@techsingularity.net@[37.228.229.96])
  by 81.17.254.9 with ESMTPSA (AES256-SHA encrypted, authenticated); 9 Jan 2019 19:42:45 -0000

0 Kudos
Reply
  • 15.88K
  • 881
  • 5.99K
Superuser
Superuser
102 Views
Message 6 of 7
Flag for a moderator
Helpful Answer

Re: Virgin Media IP block listed in RBL causing gmail to flag mail as spam

Fom an IP address point of view the only IP that matters to Google is this one here:

Received: from outbound-smtp13.blacknight.com (outbound-smtp13.blacknight.com. [46.22.139.230])
        by mx.google.com with ESMTPS id 34si319051edj.156.2019.01.09.11.42.45
        for <xxxxxx@gmail.com>
        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);

Which is one of the outbound IP's for your mail provider.

Currently it isn't blacklisted.on any blacklists that I can see.  Google doesn't care about the original mail clients IP nor does it care about the IP of the intermediate server.

Your SPF record is good, however I see that you don't use either DMARC or DKIM (SPF on it's own fails if mail is forwarded).  I'm not sure if Google will penalise you for that, but I'd certainly look into adding it if possible.

As noted the origin address is on Spamhaus' PBL (Zen is the master zone, if your IP is on any of Spamhaus' zones then the IP address will also appear in Zen).  Being on the PBL does not indicate an IP address that has been seen delivering spam, instead it indicates an IP address that is allocated by DHCP.

Google might be marking the mail as spam for other reasons, but the IP address won't be the cause.

Tim

 

________________________________________


Only use Helpful answer if your problems been solved.

0 Kudos
Reply
  • 4
  • 0
  • 0
gormanm
Joining in
78 Views
Message 7 of 7
Flag for a moderator

Re: Virgin Media IP block listed in RBL causing gmail to flag mail as spam

It's possible it was blacklisted at the time of the failure given that the mail provider did say they needed to get removed from some blacklists. I'll double check if this happens again and if I find evidence that gmail is frowning on a lack of DMARC or DKIM then I'll bring it up with them. Thanks a lot ravenstar68, much appreciated.

0 Kudos
Reply