Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I have had a real problem lately with spammers picking up legitimate hosting accounts in the United States. The strange part is that when I pull a message history in Ironport, I am seeing it make different decisions on the same single connection.
I...
Hello,
I am attempting to achieve faster faxing, while also allowing credit card machines (modem based) to work using the same equipment and configuration. Fax passthrough, T.38, etc seems to break the credit card machines. Modem passthrough works fo...
Cisco Prime Infrastructure is a damned nightmare of browser bugs (some features work in IE8, some in IE9, and some only in Firefox). And I am not sure if what I am experiencing is a browser bug - or a real bug - or something that I was able to do be...
I have an ASA 5520 with an ASA-SSM-10 module in it for IDS. It has (from what I can tell) never been used or configured. In fact, I only recently found that it existed! I would like to begin using it, starting with replacing the software image wit...
I believe that I have had this problem in the past, but I can't remember what I did to fix it.I have a user that while playing a voice mail message, will get disconnected. As in, Unity just hangs up on them. It doesn't seem to be related to any par...
@Libin Varghese wrote:
If you would like to block all connections coming to the ESA based on the sender IP or hostname you can certainly add them to the HAT Blacklist. As more spam is reported from an IP its emails reputation would drop globally.
...
I ended up figuring it out myself. I had upgraded from NCS up to Prime, and aparently my support was not upgraded along with it. So I received NO help from Cisco. And it took a few weeks to upgrade my support so that they would even talk to me about ...
After a lot of digging I found my old notes on a work order where this had happened before. Sure enough, just waiting cleared the problem. I am guessing that this is some sort of bug.
This may actually be related to my WCS / WLC environment. I was reviewing old work orders this morning and I noticed that every documented case has been on our wireless network.