10-31-2013 01:00 AM
Hi
after power loss to the box I am getting the following messages indicating that the CASE is stopped and the email delayed for almost 10 min before delvered to reciptents.Once i disable spam,antivirus,outbreak filter and the emails starts receving without any issue
Processing Details
MAIL POLICY "DEFAULT" MATCHED THESE RECIPIENTS: mhashim@cma.gov.kw
31 Oct 2013 09:05:19 (GMT +03:00) Protocol SMTP interface PublicNet (IP 10.16.2.19) on incoming connection (ICID 46966) from sender IP 195.75.94.114. Reverse DNS host e06smtp18.uk.ibm.com verified yes.
31 Oct 2013 09:05:19 (GMT +03:00) (ICID 46966) ACCEPT sender group UNKNOWNLIST match sbrs[-1.0:10.0] SBRS 5.6
31 Oct 2013 09:05:20 (GMT +03:00) Incoming connection (ICID 46966) successfully accepted TLS protocol TLSv1 cipher DHE-RSA-AES256-SHA.
31 Oct 2013 09:05:20 (GMT +03:00) Start message 30881 on incoming connection (ICID 46966).
31 Oct 2013 09:05:20 (GMT +03:00) Message 30881 enqueued on incoming connection (ICID 46966) from asim@ae.gbm.ihost.com.
31 Oct 2013 09:05:20 (GMT +03:00) Message 30881 on incoming connection (ICID 46966) added recipient (mhashim@cma.gov.kw).
31 Oct 2013 09:05:20 (GMT +03:00) Message 30881 contains message ID header '<OF88307171.628FEB43-ON44257C15.002170A8-44257C15.0021797B@ae.gbm.ihost.com>'.
31 Oct 2013 09:05:20 (GMT +03:00) Message 30881 original subject on injection: test 31/10
31 Oct 2013 09:05:20 (GMT +03:00) Message 30881 (10991 bytes) from asim@ae.gbm.ihost.com ready.
31 Oct 2013 09:05:20 (GMT +03:00) Message 30881 matched per-recipient policy DEFAULT for inbound mail policies.
31 Oct 2013 09:05:20 (GMT +03:00) Message 30881 encountered CASE down (1/60). Retry scanning in 12 seconds.
31 Oct 2013 09:05:32 (GMT +03:00) Message 30881 encountered CASE down (2/60). Retry scanning in 12 seconds.
31 Oct 2013 09:05:44 (GMT +03:00) Message 30881 encountered CASE down (3/60). Retry scanning in 12 seconds.
31 Oct 2013 09:05:56 (GMT +03:00) Message 30881 encountered CASE down (4/60). Retry scanning in 12 seconds.
31 Oct 2013 09:06:08 (GMT +03:00) Message 30881 encountered CASE down (5/60). Retry scanning in 12 seconds.
31 Oct 2013 09:06:20 (GMT +03:00) Message 30881 encountered CASE down (6/60). Retry scanning in 12 seconds.
31 Oct 2013 09:06:32 (GMT +03:00) Message 30881 encountered CASE down (7/60). Retry scanning in 12 seconds.
31 Oct 2013 09:06:44 (GMT +03:00) Message 30881 encountered CASE down (8/60). Retry scanning in 12 seconds.
31 Oct 2013 09:06:57 (GMT +03:00) Message 30881 encountered CASE down (9/60). Retry scanning in 12 seconds.
31 Oct 2013 09:07:09 (GMT +03:00) Message 30881 encountered CASE down (10/60). Retry scanning in 12 seconds.
31 Oct 2013 09:07:21 (GMT +03:00) Message 30881 encountered CASE down (11/60). Retry scanning in 12 seconds.
31 Oct 2013 09:07:33 (GMT +03:00) Message 30881 encountered CASE down (12/60). Retry scanning in 12 seconds.
31 Oct 2013 09:07:45 (GMT +03:00) Message 30881 encountered CASE down (13/60). Retry scanning in 12 seconds.
31 Oct 2013 09:07:57 (GMT +03:00) Message 30881 encountered CASE down (14/60). Retry scanning in 12 seconds.
31 Oct 2013 09:08:09 (GMT +03:00) Message 30881 encountered CASE down (15/60). Retry scanning in 12 seconds.
31 Oct 2013 09:08:21 (GMT +03:00) Message 30881 encountered CASE down (16/60). Retry scanning in 12 seconds.
31 Oct 2013 09:08:33 (GMT +03:00) Message 30881 encountered CASE down (17/60). Retry scanning in 12 seconds.
Continue Searching? This message may have additional processing details. Extend the search timeframe to investigate more details.
3 weeks 1 month 2 months 3 months 6 months Entire Data Range
Message 30881 processing incomplete. CASE could not be reached
Key: Last Event
Any ideas how to correct this issue?
Thanks,
10-31-2013 06:12 AM
A hard reboot can cause inconsistencies with anti-spam.
If you have not, try to run the command "antispamupdate ironport force" in the CLI.
You can also get the status of anti-spam in the CLI with the "antispamstatus".
This will force an update of the anti-spam rules and can sometimes resolve issues like this.
~Blake
11-03-2013 09:55 PM
Issue solved by upgrade the firmware
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide