- iRedMail 版本号：0.9.5-1
- 使用哪个数据库存储用户帐号（OpenLDAP，MySQL，PostgreSQL）：MySQL
- 使用的 Linux/BSD 发行版名称及版本号：CentOS6.5 X64
- 与您的问题相关的日志信息：
Your message WAS SUCCESSFULLY RELAYED to:
<test@test.com
>

This delivery report was generated by the program amavisd-new at host
mx.test.com. Our internal reference code for your message is
01629-04/KkjEmKundSCF

INVALID HEADER: INVALID 8-BIT CHARACTERS IN HEADER SECTION

Non-encoded 8-bit data (char E9 hex): X-Mailer:
   \351\273\221\347\247\221\346\212\200SS\345\220\210\347\247\237

Return-Path: <info@test.cn>
From: =?utf-8?B?6buR56eR5oqAU1PlkIjnp58=?= <info@test.cn>
Message-ID: <37b72bb41431df8750621402701e4f0d@1>
X-Mailer: 黑科æŠ\200SS合租
Subject: 1111111

WHAT IS AN INVALID CHARACTER IN A MAIL HEADER SECTION?

The RFC 5322 document specifies rules for forming internet messages.
It does not allow the use of characters with codes above 127 to be
used directly (non-encoded) in a mail header section.

If such characters (e.g. with diacritics) from ISO Latin or other
alphabets need to be included in a header section, these characters
need to be properly encoded according to RFC 2047. Such encoding
is often done transparently by mail reader (MUA), but if automatic
encoding is not available (e.g. by some older MUA) it is a user's
responsibility to avoid using such characters in a header section,
or to encode them manually. Typically the offending header fields
in this category are 'Subject', 'Organization', and comment fields
or display names in e-mail addresses of 'From', 'To' or 'Cc'.

Sometimes such invalid header fields are inserted automatically
by some MUA, MTA, content filter, or other mail handling service.
If this is the case, such service needs to be fixed or properly
configured. Typically the offending header fields in this category
are 'Date', 'Received', 'X-Mailer', 'X-Priority', 'X-Scanned', etc.

If you don't know how to fix or avoid the problem, please report it
to _your_ postmaster or system manager.
Reporting-MTA: dns; mx.test.com
Received-From-MTA: smtp; mx.test.com ([127.0.0.1])
Arrival-Date: Sun, 16 Oct 2016 15:15:41 +0800 (CST)

Original-Recipient: rfc822;test@test.com

Final-Recipient: rfc822;test@test.com

Action: delayed
Status: 2.0.0
Diagnostic-Code: smtp; 250 2.6.0 Bad message, but will be delivered anyway
Last-Attempt-Date: Sun, 16 Oct 2016 15:15:41 +0800 (CST)
Final-Log-ID: 01629-04/KkjEmKundSCF
Return-Path: <info@test.cn>
Received: from 1 (unknown [45.248.87.217])
    by cn01.ss-link.cn (Postfix) with ESMTPSA id E28B1C120A
    for <test@test.com
>; Sun, 16 Oct 2016 15:15:40 +0800 (CST)
Date: Sun, 16 Oct 2016 15:15:32 +0800
To: =?utf-8?B?6Zeu5Y+35piv5oiR?= <test@test.com
>
From: =?utf-8?B?6buR56eR5oqAU1PlkIjnp58=?= <info@test.cn>
Subject: 1111111
Message-ID: <37b72bb41431df8750621402701e4f0d@1>
X-Priority: 3
X-Mailer: 
MIME-Version: 1.0
Content-Type: multipart/alternative;
    boundary="b1_37b72bb41431df8750621402701e4f0d"
Content-Transfer-Encoding: base64