MTA: If Exception is based on Source Host and saved, after editing the saved entry the Source Host disappears

In the meantime I could figure out, that this behaviour occurs only, when a Network Object (192.168.1.0/24) is used instead of a Host. So now there are two possibilities:

1. If it's not planed to use a Network object there, it should initially be impossible even to create such a Rule.

2. If it's planned to use a Network object there, it should be visible after editting :)

Kind Regards

Christian

In the meantime I could figure out, that this behaviour occurs only, when a Network Object (192.168.1.0/24) is used instead of a Host. So now there are two possibilities:

1. If it's not planed to use a Network object there, it should initially be impossible even to create such a Rule.

2. If it's planned to use a Network object there, it should be visible after editting :)

Kind Regards

Christian

Hello Christian,

As per my best understanding exceptions are allowed to use only with hosts and not with networks.

Have you created this exception policy in 17.1 ? Do you see the same issue when you try to create new exception policy ? 

I completely agree with you :) In that case it should not be possible to use a network object on that place at all... Unfortunatedly it currently is possible to initially use a Network and not a Host Object.

Hello Christian,

I tried to reproduce the issue on latest firmware and was not able to.

Could you pls provide below information ?

 1) Have you created your exception policy in prior firmware i.e. 17.1-MR ?

Ah, I managed to reproduce it now. It appears only when you create fresh exception policy with network host. Then further it wont allow network host. However it should not allow the network hosts since beginning. Engineering team has confirmed this fix in next release.     

That's exactly what I was meaning. Thanks :) 

We are tracking the issue with JIRA ID NC-39513

Thanks