Unable to use "Reject based on RBL" in SMTP Policies

How can you confirm this situation, as i cannot reproduce someone sending me, who is on the RBL in the first place. 

How can you confirm this situation, as i cannot reproduce someone sending me, who is on the RBL in the first place. 

When trying to check the option "Reject based on RBL" after adding the SMTP policy, nothing happens. I cannot check it, no menu appears where I could add the RBL lists. My existing rule, where this is already enabled, it looks fine. However, when I uncheck it, I cannot check it again. So my assumption was, that this is a general problem and I was looking for a confirmation, whether someone else has the same problem.

Hi Saarbruecken  I have checked with my 3 LAB devices running in V19.5 MR-4, V20 MR-1, and V21 EAP but the issue was not observed for me, so I am trying to upgrade my V20 MR-1 LAB device to V20 MR-2 and will update you further.

Hi Saarbruecken I checked with V20 MR-2 as well in my LAB but it looks like it works for me, so maybe some specific conditions are triggering an issue or it is specific to your firewall configuration, so I would request you to log a support case to have an investigation on it and to validate it further, if the case is already open please share the case details with us to keep an eye on it.

I am no longer part of the firewall team at work, so I cannot open a ticket. It's also my home firewall that is affected.

Can you share a screenshot, where you are and how it looks for you? 

I basically try to check "Reject based on RBL". You nicely see that it tries to load something as the website is moving down 10 pixels, but nothing happens.

Did you delete the predefined URL Lists by any chance? 

I renamed them, because a few RBL providers have shut down in the past -- for a better overview. But I didn't touch them, as you can see, it's not possible (anymore?) to delete them.

I think, the renaming is causing this behavior to pop up. 

I can actually reproduce this.

Can you rename them back to: 
Standard RBL Services 

Premium RBL Services 

We can track this internally to fix it. 

Works again! You were right, the problem occurs after renaming the default RBL. 

Thank you!