Planned for 11.34 Update IP Blocks in /etc/mailproviders/rim/ips [Case 52622]

[acenetgeorge]

This is a relatively minor request, but we've seen several Blackberry connectivity issues that are resolved by manually updating the IP ranges used by RIM for Blackberry devices. The existing file only has two small IP ranges.

If these could be added to the /etc/mailproviders/rim/ips file in future upcp updates, it may help others with Blackberry email issues.

-----------------------

KB11036-Firewall and connection requirements for the BlackBerry Internet Service

206.51.26.0/24
193.109.81.0/24
204.187.87.0/24
206.53.144.0/20
216.9.240.0/20
67.223.64.0/19
93.186.16.0/20
68.171.224.0/19
74.82.64.0/19
173.247.32.0/19
178.239.80.0/20
180.149.148.0/22
180.168.204.0/22

[cPanelDavidG]

I have spoken with our developers about this and thank you for providing an authoritative source for the IP ranges. This seems like a simple fix, and has been entered into our internal systems as case 52622.

[cPanelDavidG]

Update: we are currently targeting this to be accommodated in version 11.34.

[Kent Brockman]

Please make note that the upgrade by cPanel must check if any or all the described IP ranges are already set in the ips file, to avoid repeated data if anybody added it manually, like I did

[Infopro]

A related thread was updated recently on the topic of blackberry IP ranges. Adding link here so it can be found by others.

[Kent Brockman]

I've noticed that cPanel updates, update the /etc/mailproviders/rim/ips file with the same old 2 IP included by default, overwriting the changes suggested in this thread. What can be done to block updates over this file?
chattr +i /etc/mailproviders/rim/ips

[Kent Brockman]

Or should I add the ips file to /etc/cpanelsync.exclude?

[crazyaboutlinux]

hmmmmmmm, very interesting feature +1

[cPanelDavidG]

Or should I add the ips file to /etc/cpanelsync.exclude?

This is the preferred option. We have programmed our installer/updater to kinda freak out at immutable files in preparation for our migration to RPMs since RPMs and immutable files don't get along at all in our testing.