ALERT! The community will be read-only on April 19, 8am Pacific as the migration begins. Read more for important details.
ALERT! The community will be read-only on April 19, 8am Pacific as the migration begins.Read more for important details.
Captain
Captain
284 views

Does IP Reputation accept address ranges?

I have not been able to find any information on this.

We have a new EAP provider that uses an external email service.

They have provided whitelisting information that includes 3 IP address subnets.

Has anyone tried entering a range instead of just single addresses?

Will it work with a range?

Thanks.

0 Likes
9 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

So do you want to set exceptions for ip reputation?

Diethmar Rimser
This community is more powerful if you use Likes and Solutions
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Unfortunately I do not have ranges to except. But I checked one of my customers. I checked especially some parts which have been migrated from old GWAVA. Yes, there we used ranges - and if you migrate to Gwava7/SMG then these exceptions should work in the same way!

So my conclusion - yes, it should work!

Diethmar Rimser
This community is more powerful if you use Likes and Solutions
Captain
Captain

Hi Diethmar,

I do have some existing exceptions to the inbound policy IP reputation filter, but they are just single addresses.

I think that there have been some changes in the way that IP reputation worked between GWAVA 7 on SLES, SMG on Ubuntu and SMG on SLES ( which is where we are now). If you have those migrated and appear to be working, then I'll go with that!

 

Thanks, Chris

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

@frickc 

IP reputation can be specified at the SMTP Interface under Connection Drop Services. It will affect all connections to SMG and the only way to exclude some IP addresses is to use the slider.

SMTP IP reputation 1.PNG

IP reputation can also be specified in a policy by using an IP Reputation filter:

SMTP IP reputation.PNG

The IP Reputation filter works the same way but you can attach an Address Exception to exclude specific IP addresses.

I don't know if the Address Exception will accept ranges. It may accept subnets e.g. 10.0.2.0/30.

 

 

_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
0 Likes
Captain
Captain

Thanks Kevin.

I used to use connection drop, but had to switch to policy to make some very specific exceptions.

Just wondering if the exceptions to the filter would work with subnets such as your example?

I can certainly add them, but may never know if it actually works.

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

If you go for exceptions then take care to use single filters instead of filter groups. You will find some more information in this forum because of exceptions. Handling can be tricky ...

Diethmar Rimser
This community is more powerful if you use Likes and Solutions
Captain
Captain

Hi Diethmar,

I looked at using filter groups once. It only looks simpler. In reality it is a lot simpler to use single filters when you need to link to different services and exceptions.

Regards,

Chris

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner


@frickc wrote:

Thanks Kevin.

I used to use connection drop, but had to switch to policy to make some very specific exceptions.

Hi Chris,

When the SLES appliance was changed to use Bitdefender, IP reputation was assessed differently. For one thing, the concept of a temporary failure no longer applies. SMG still can assess some IP reputations as deserving of a temporary fail but Bitdefender has no way to dynamically adjust an IP addresses reputation. Each time a message is received from that IP address it will be processed exactly the same way and get a another temporary fail. The only way to circumvent this is to avoid temporary failures altogether and use IP address exceptions for messages from IP addresses whose IP reputation is not good enough.

Just wondering if the exceptions to the filter would work with subnets such as your example?

I can certainly add them, but may never know if it actually works.


You can always test it.

  • Create a test filter policy.
  • Add the specific filter components you want to test.
  • Go to Systems Management / Scanner Diagnostic
  • Choose a simple email to test
  • Add applicable message envelope information (i.e. source IP address)
  • Select your test scan policy
  • Run the scan and check the results.
_____
Kevin Boyle - Knowledge Partner - Calgary, Alberta, Canada
Who are the Knowledge Partners?
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
Captain
Captain

Hi Kevin,

I've been so crazy busy it could be while before I get a chance to try the test.

Thanks for the suggestion.

Regards,

Chris

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.