SMTP Error (state 12): 557
Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=5392
Printed Date: 22 January 2025 at 8:05am
Topic: SMTP Error (state 12): 557
Posted By: Guests
Subject: SMTP Error (state 12): 557
Date Posted: 28 November 2005 at 10:12am
We have been evaluating SpamFilter ISP for a few months, and have been
waiting for the new budget to be approved so we can purchase two
licenses.
Our current configuration is we have SpamFilter running on two seperate
machines (one is primary, one is secondary) with MySQL running on the
primary server for quarantine purposes. The secondary server
isn't as beefy and it uses the database on the primary server.
SMTP records point to the primary first, then the secondary server.
This weekend we discovered that SpamServer was 'hung' or appeared to
have stopped filtering/forwarding mail to our Exchange server. I
sent a test message from gmail to my work mail, and received the
following error back:
"This is an automatically generated Delivery Status Notification
Delivery to the following recipient failed permanently:
my e-mail address
Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 12): 557 The server encountered an error while processing this message. Please retry later."
Typically, our failover system works somewhat well, in that if the
primary server should crash, or be powered off, mail will still
continue to come in on our secondary server. However, since this
message was rejected - it didn't fail over to our second server (via
smtp priority) and it wasn't sent back to be requeued in the
originator's mail queue.
I checked the log file from yesterday, and I don't see any error messages prior to the log not receiving entries.
Normally if Spamfilter should hang, it wouldn't receive any
connections, and wouldn't send back a rejection, but that doesn't
appear to be the case here. If it had stopped receiving
connections - I wouldn't have received the 557 rejection code, correct?
Any thoughts on what might have caused this?
Sincerely,
Dave Montgomery
|
Replies:
Posted By: LogSat
Date Posted: 28 November 2005 at 10:27am
Dave,
You are correct in your assumption that is SpamFilter crashes/hangs,
then the server would not accept anymore connections, and your
secondary MX server would be receiving the traffic.
From the error you describe however, it seems that SpamFilter did *not*
fully crash, but rather was outputting a 557 rejection code to your
test messages. The error you describe is sent in case of generic errors
during reception of emails, and SpamFilter's activity logfiles should
provide clues asa to what happened. If you can please zip and email us
to support@logsat.com SpamFilter's activity logfile for the day this
happen we'll try to take a look to see what happened.
As a side note, this is the first time we had a report (that we can
remember) of the exact error message you describe, and is the first
case we've had to troubleshoot it. We may change the error code from a
"permanent" error code of 5xx to a "temporary" error code of "4xx",
which will tell the remote server to retry sending the message at a
later time.
-------------
Roberto Franceschetti
http://www.logsat.com" rel="nofollow - LogSat Software
http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP
|
|