As previously mentioned I have configured two relatively new IMGate servers
which were initially configured as inbound gateways. This has been running
for about two weeks and with a little bit of fine tuning things are working
great for inbound email. Now that inbound email is now working well I
decided yesterday morning to take the next step and configured them as
outgoing smarthosts for our Exchange 2003 and Imail servers. In the
afternoon I received a call from one of our users stating that an email he
sent to our lawyers from an Outlook client was bounced with the following
error:
The following recipient(s) could not be reached:
R Henry Easingwood on 02/02/2005 3:44 PM
There was a SMTP communication problem with the recipient's
email server. Please contact your system administrator.
<charity.twu.ca #5.5.0 smtp;550 Error: ACL header_1>
John Cherrington on 02/02/2005 3:44 PM
There was a SMTP communication problem with the recipient's
email server. Please contact your system administrator.
<charity.twu.ca #5.5.0 smtp;550 Error: ACL header_1>
Hank Easingwood ([EMAIL PROTECTED]) on 02/02/2005 3:44 PM
There was a SMTP communication problem with the recipient's
email server. Please contact your system administrator.
<charity.twu.ca #5.5.0 smtp;550 Error: ACL header_1>
I checked the logs and here is the log entry for this email:
Feb 2 15:42:09 mx10 postfix/cleanup[3338]: 7813A17B438: hold: header
Received: from charity.twu.ca (charity.twu.ca [10.10.116.44])??by
mx10.twu.ca (Postfix) with ESMTP??id 7813A17B438; Wed, 2 Feb 2005 15:42:09
-0800 (PST) from charity.twu.ca[10.10.116.44]; from=<[EMAIL PROTECTED]>
to=<[EMAIL PROTECTED]> proto=ESMTP helo=<charity.twu.ca>
Feb 2 15:42:09 mx10 postfix/cleanup[3338]: 7813A17B438:
message-id=<[EMAIL PROTECTED]>
Feb 2 15:42:09 mx10 postfix/cleanup[3338]: 7813A17B438: reject: header
Content-Type: text/plain;??charset="iso-2022-jp" from
charity.twu.ca[10.10.116.44]; from=<[EMAIL PROTECTED]>
to=<[EMAIL PROTECTED]> proto=ESMTP helo=<charity.twu.ca>: ACL
header_1
This appears to have been blocked through the header_checks.regexp rule:
/^Content-Type:.*charset=.*(big5|euc-kr|gb2312|iso-.*-jp|ks_c_5601-1987)/
REJECT ACL header_1
It appears to have been caused by the MIME type charset="iso-2022-jp"
showing in the log as received from the header. Can anyone tell me why this
MIME type would show up in a message composed from an Outlook client to
produce this header information.
I should note that this users other email has gone out fine and I have not
heard from any of our other 900+ Outlook users regarding a similar problem.
I have left a message with this user to find out more about how he created
the message, but he is not in the office.
Richard Edge
Senior Systems Administrator | Technology Services
Trinity Western University | t: 604.513.2089
f: 604.513.2038 | e: [EMAIL PROTECTED] | www.twu.ca/technology
-- Binary/unsupported file stripped by Ecartis --
-- Type: application/x-pkcs7-signature
-- File: smime.p7s
