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 am receiving TONS of complaints since upgrading to 9.6.0-051 that SPAM is being allowed through dramatically. I am lowering the SPAM thresholds for our clients (MAIL POLICIES) all the time now (and we have hundreds of clients). Has anything happene...
Can someone explain what TCP Listen Queue Size actually does for my listener? My issue is we are having a few (maybe 10 out of 10,000) TLS failures from Exchange to the ESA's which are relayed outside the ORG. The TLS error in the logs from Exchange ...
We have a client that would like to delay outbound emails for 5 minutes. I have no idea why they would request this when 99.99% of the time they complain about speed of delivery but regardless I am looking for an IronPort solution (if possible). Is ...
I recently migrated from the physical SMA (M170) to the new virtual appliance which went smooth. The one thing I would like to do is to (if possible) is to merge or migrate the message tracking from the old device into the new virtual SMA so I have ...
I know this is a super old thread, but I get them ALL the time on AsyncOS 9.6.0-051 (which is the latest release). This was never fixed so don't fool yourself into thinking Cisco fixed it:
The Critical message is:
An application fault occurred: ('na...
Thanks for the info but my problem is not related to the PVO central settings. It turns out to be a bug in the older software and hasn't returned since updating to the later versions of AsyncOS.
TAC escalation did indeed find the SPAM CORE definitions were not in date EVEN though they show current in the GUI. Apparently they broke at point of upgrade and never actually applied since the upgrade even though they were going out to Cisco's site...
