☰

552 此訊息不符合 RFC 2822

tag-icon • tag-icon email smtp email-bounces
552 此訊息不符合 RFC 2822

我已經設定自動回覆電子郵件有一段時間了，突然我收到以下未送達訊息。我只遇到過一次，所以這似乎不是一個普遍問題。我快速檢查了 RFC 2822，看看問題是否顯而易見，但事實並非如此。

未送達的訊息也不表示出了什麼問題。我什至不知道從哪裡開始，谷歌也沒有關於這個錯誤代碼的結果。

錯誤訊息:

This is the mail system at host example.com.

I'm sorry to have to inform you that your message could not
be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to <postmaster>

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

                   The mail system

<[email protected]>: host mx.blow.com[123.123.123.123] said: 552 This
    message is not RFC 2822 compliant [smtp-07.iol.local; LIB_670] (in reply to
    end of DATA command)

電子郵件來源：

Received: from localhost (mailsvr [127.0.0.1])
    by example.com (Postfix) with ESMTP id 79B9638792F0
    for <[email protected]>; Thu, 22 Jan 2015 11:01:38 +0100 (CET)
X-Virus-Scanned: amavisd-new at example.com
Received: from example.com ([127.0.0.1])
    by localhost (mailsvr.example.com [127.0.0.1]) (amavisd-new, port 10024)
    with LMTP id PBe6jEv1vZEb for <[email protected]>;
    Thu, 22 Jan 2015 11:01:32 +0100 (CET)
Received: by example.com (Postfix, from userid 0)
    id D000B38792FC; Thu, 22 Jan 2015 11:01:29 +0100 (CET)
To: [email protected]
Subject: =?UTF-8?B?123456789==?=
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary = cb686159096ae4feaf2a23845e82dce0
From: Me <[email protected]>
Reply-To: [email protected]
Message-Id: <[email protected]>
Date: Thu, 22 Jan 2015 11:01:29 +0100 (CET)

--cb686159096ae4feaf2a23845e82dce0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64


123456789123
--cb686159096ae4feaf2a23845e82dce0
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: base64


12349678945313
--cb686159096ae4feaf2a23845e82dce0--

答案1

從 1 月 21 日開始，我在 libero.it (Italia OnLine) 上也遇到了同樣的問題。我在這裡看到您的電子郵件也存在同樣的問題。

目前你有boundary = cb686159096ae4feaf2a23845e82dce0.嘗試在它周圍加上引號，刪除等號前面和後面的空格，然後添加類似“=_”的內容，以獲得類似這樣的內容boundary="cb686159096ae4feaf2a23845e82dce0"。希望人工晶體植入後情況會恢復正常。

在查看了 RFC 2822、RFC 2045 和 RFC 2046（以及連結和更新文件）之後，我敢說This message is not RFC 2822 compliant 是不正確的。 RFC 2046 僅建議「將邊界參數值括在引號中永遠不會有什麼壞處」。比這更有趣的是 RFC 2045 中的註解告訴我們在邊界內使用像「=_」這樣的字元序列（見下文）。

希望這可以幫助！

RFC 2045 http://www.rfc-editor.org/rfc/rfc2045.txt

Since the hyphen character ("-") may be represented as itself in the
Quoted-Printable encoding, care must be taken, when encapsulating a
quoted-printable encoded body inside one or more multipart entities,
to ensure that the boundary delimiter does not appear anywhere in the
encoded body.  (A good strategy is to choose a boundary that includes
a character sequence such as "=_" which can never appear in a
quoted-printable body.  See the definition of multipart messages in
RFC 2046.)

RFC 2046 http://www.rfc-editor.org/rfc/rfc2046.txt

WARNING TO IMPLEMENTORS:  The grammar for parameters on the Content-
type field is such that it is often necessary to enclose the boundary
parameter values in quotes on the Content-type line.  This is not
always necessary, but never hurts.

相關內容