Public IP Address Blocked by Spamhaus

[WilliamDalley]

Hello,

Recently I converted my homes broadband to a 4G mobile broadband package. 

Since moving over three weeks ago I have experienced on multiple occasions my public IP address being blocked by Spamhaus spam email filtering. This has meant I am unable to send emails on my network from Outlook. When trying to send an email I receive the bounce back

"Server error: '554 5.7.1 Service unavailable; Client host [---.---.---.---] blocked using sbl.spamhaus.org; https://www.spamhaus.org/sbl/query/SBLCSS'"

If I restart my 4G router to receive a new public IP address I am able to then able to successfully send emails.

Although I have this solution, having to restart my network to be able to send emails is very annoying! Why does it appear lots of EE public IP addresses are blocked by spam email protection services..? This nuisance is ruining the service and I am thinking of returning to traditional landline broadband. I did contact EE 'technical' support by phone but they told me they don't "offer all that dynamic IPs and addresses and stuff"... when I tried to explain the situation.

[XRaySpeX]

Previous users of that public IP have been suspected of spamming. All you can do is restart your router to hope to get a clean IP. 

[RogerZT]

Looking carefully at the wording by Spamhaus it appears that EE have placed all their address ranges in the Spamhaus filter as being unable to post direct to the internet.  This is not incorrect in itself and not unreasonable.

What appears to be happening is that rogue email systems are incorrectly applying the filter and blocking all emails from the address range not just those which are being sent direct.  I did persuade one organisation to sort themselves out but it took a lot of pressure by a personal acquaintance but this is now happening so often that the only practical solution is for EE to make some technical changes.

I've just spoken to someone from EE's first line support who didn't understand what I was saying and was unable to escalate the call.  I fear that this may have to be escalated as a formal complaint.

[Kirigaya_Kazuto]

Have you tried running through a VPN? See if that gets around this block. I mean a full VPN, not just a browser extension

[XRaySpeX]

---

@RogerZT wrote:

Looking carefully at the wording by Spamhaus it appears that EE have placed all their address ranges in the Spamhaus filter as being unable to post direct to the internet. 

---

Then explain how I, with an EE public IP, can always send emails & have never been blocked.

[RogerZT]

Because you are not sending your emails to a third party provider using SMTP.

[XRaySpeX]

Aren't I? Most of us do!

[grsdev]

Because you're not sending direct-to-MX but through your ISP or another e-mail delivery service, maybe?

[grsdev]

Are you sending direct-to-MX by any chance?

If so, that's your problem right there. An IP address assigned to a 4G router is a dynamic address "belonging" to an end-user who shouldn't be relaying mail directly to the recipient's MX.

[XRaySpeX]

@grsdev : Yes, that's what I do as I said.