Messaging Gateway

Hello,

Our SMG says in the IP Reputation lookup that the IP address 164.132.99.87 is on the list of Global Bad Senders. But the test http://ipremoval.sms.symantec.com/lookup/ shows that there is not. The IP address you submitted, 164.132.99.87, does not have a negative reputation and therefore cannot be submitted for investigation.

The test http://www.symantec.com/security_response/landing/spam/ shows the neutral reputation for this IPaddress.

Why our SMG  see it that way?

We are not able to received   messages from this IP, the domain is vicomtrade.cz .  Verdict =Symantec Global Bad Sender .

I can put IP address to the Local Good Senders, but is not the solution I like.   

Thanks

Jan

Same issue here.

An address listed in Symantec Global Bad Senders but when I click on the request removal and visit

http://ipremoval.sms.symantec.com/lookup/

entering the IP address, then it shows message:

"The IP address you submitted, x.x.x.x does not have a negative reputation and therefore cannot be submitted for investigation."

I'm totally stuck here. Only work around is adding the IP to whitelist. But I'm not sure how much legit mail has been rejected due to this "BUG".

Any soluction to solve this?

Unfortunately so far I haven't found the solution , nobody answered.

We have the same issue with 46.21.145.98.

SMG blocks all the mail from this domain with verdict: Global bad sender.
In the IP reputation tool the global bad sender box is checked and you can go to the request removal page.

On the ip reputation page, you will get the message no negative reputation for that IP.

On the IP reputation lookup page on the SMG i see some strange behaviour:

I see the global bad sender box checked and the following local status:

MX2 - TC5 - Scanner Reject None 0% 9

MX1 - TC4 - Scanner and Contr... Reject None 0% 9

If i click find again the checkbox is not checked anymore and also the local status gives the filter normally action.
If i click find again then the above "wrong" info is showed again.

And so on

And so on
 

Hi, same incidence, ip : 212.129.11.230

http://imgur.com/a/r1We6

Hi, we have the same issue here with Symantec Global Bad Sender on IP 115.133.168.57.

It seems like this problem only happens since year 2017? What has Symantec change on this matters since year 2017?

Can anybody share how to manage this Global Bad Sender issue? As for my case, we just quarantine this IP and daily monitor it if any email is legitmate and let it pass. But I don't think this is a good way to do it.

-- Lawrence