使用 swift mailer (php) 发送邮件到 gforge 电子邮件网关,等号 (=) 在行尾
现在,我在 gForge 上遇到了另一个问题。
我的内联网中有一个表格,可以在我们的 gforge 系统中创建新的跟踪器。我们使用 Kohana 和 Swift Mailer 发送 smtp 电子邮件。
这就是我得到的(我将邮件作为密件抄送给自己):
Received: from 192.168.150.250 (192.168.150.250) by local
(192.168.50.10) with Microsoft SMTP Server id 15.1.280.1; Wed, 16 Mar 2011
08:51:40 +0100
Message-ID: <[email protected]>
Date: Wed, 16 Mar 2011 08:51:38 +0100
Subject: Test_Issue Jieha (tracker-17)
From: <[email protected]>
To: <[email protected]>
BCC: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Return-Path: [email protected]
X-MS-Exchange-Organization-AuthSource: local
X-MS-Exchange-Organization-AuthAs: Anonymous
MIME-Version: 1.0
priority:4
assignees: wollmannc
stardate: 03/16/2011
end date: 03/17/2011
Von user:
Name: Christian
email: [email protected]
Bemerkung:
mein bemerkungstext
testinput: mein input
所以一切看起来都很好。但 Gforge 告诉我:
Received: from local (192.168.200.19) by
local (192.168.50.10) with Microsoft SMTP Server id
15.1.280.1; Wed, 16 Mar 2011 08:51:42 +0100
Received: from gforge.local (centos5 [127.0.0.1]) by
gforge.local (Postfix) with ESMTP id 5DBDED48174 for
<[email protected]>; Wed, 16 Mar 2011 08:51:42 +0100 (CET)
Received: (from nobody@localhost) by gforge.local
(8.13.8/8.13.8/Submit) id p2G7pgvZ004723; Wed, 16 Mar 2011 08:51:42 +0100
Date: Wed, 16 Mar 2011 08:51:42 +0100
From: <[email protected]>
Message-ID: <[email protected]>
X-Authentication-Warning: gforge.local: nobody set sender to "GForge" <[email protected]> using -f
To: <[email protected]>
Reply-To: GForge <[email protected]>
Subject: =?utf-8?B?RmVobyIGJlaWgQmVhcmJlaXRlbiBkZXIgRW1haWw=?=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Return-Path: [email protected]
X-MS-Exchange-Organization-AuthSource: local
X-MS-Exchange-Organization-AuthAs: Anonymous
MIME-Version: 1.0
Ihre Email konnte nicht verarbeitet werden.
Die Anwendung sagte:
* Start Datum ist Erforderlich
* Schlieungs Datum ist Erforderlich
* Close Date must be > Open Date
Ihre Nachricht war:
priority:4
assignees: wollmannc
stardate: 03/16/2011
end d=
ate: 03/17/2011
Von user:
Name: Christian
email: meine@em=
ail.de
Bemerkung:
mein bemerkungstext
testinput: mei=
n input
它告诉我“无法处理电子邮件。应用程序说:需要开始日期,需要结束日期”。
请注意某些行末尾的等号。我认为这是“引用的可打印”的最大行长度,还是 smtp 也限制了行数?但为什么我能通过密件抄送收到正确的邮件?这应该和 gforge 收到的邮件一样吧?! Gforge 对收到的邮件做了什么吗?
我很困惑:-(我希望你能帮忙。
Now, i have another problem with gForge.
I have a form in our intranet to create new trackers in our gforge system. We use Kohana and the Swift Mailer to send smtp emails.
This is what i get (i send the mail as bcc to myself):
Received: from 192.168.150.250 (192.168.150.250) by local
(192.168.50.10) with Microsoft SMTP Server id 15.1.280.1; Wed, 16 Mar 2011
08:51:40 +0100
Message-ID: <[email protected]>
Date: Wed, 16 Mar 2011 08:51:38 +0100
Subject: Test_Issue Jieha (tracker-17)
From: <[email protected]>
To: <[email protected]>
BCC: <[email protected]>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Return-Path: [email protected]
X-MS-Exchange-Organization-AuthSource: local
X-MS-Exchange-Organization-AuthAs: Anonymous
MIME-Version: 1.0
priority:4
assignees: wollmannc
stardate: 03/16/2011
end date: 03/17/2011
Von user:
Name: Christian
email: [email protected]
Bemerkung:
mein bemerkungstext
testinput: mein input
So everything looks fine. But Gforge is telling me:
Received: from local (192.168.200.19) by
local (192.168.50.10) with Microsoft SMTP Server id
15.1.280.1; Wed, 16 Mar 2011 08:51:42 +0100
Received: from gforge.local (centos5 [127.0.0.1]) by
gforge.local (Postfix) with ESMTP id 5DBDED48174 for
<[email protected]>; Wed, 16 Mar 2011 08:51:42 +0100 (CET)
Received: (from nobody@localhost) by gforge.local
(8.13.8/8.13.8/Submit) id p2G7pgvZ004723; Wed, 16 Mar 2011 08:51:42 +0100
Date: Wed, 16 Mar 2011 08:51:42 +0100
From: <[email protected]>
Message-ID: <[email protected]>
X-Authentication-Warning: gforge.local: nobody set sender to "GForge" <[email protected]> using -f
To: <[email protected]>
Reply-To: GForge <[email protected]>
Subject: =?utf-8?B?RmVobyIGJlaWgQmVhcmJlaXRlbiBkZXIgRW1haWw=?=
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Return-Path: [email protected]
X-MS-Exchange-Organization-AuthSource: local
X-MS-Exchange-Organization-AuthAs: Anonymous
MIME-Version: 1.0
Ihre Email konnte nicht verarbeitet werden.
Die Anwendung sagte:
* Start Datum ist Erforderlich
* Schlieungs Datum ist Erforderlich
* Close Date must be > Open Date
Ihre Nachricht war:
priority:4
assignees: wollmannc
stardate: 03/16/2011
end d=
ate: 03/17/2011
Von user:
Name: Christian
email: meine@em=
ail.de
Bemerkung:
mein bemerkungstext
testinput: mei=
n input
It tells "the email could not be processed. The application says: a start date is required, a close date is required".
Note the equal signs at the end of some lines. I think that is the maximum line length of "quoted printable" or does the smtp also limit the lines? But why do i get the right mail through BCC? That should be the same mail that gforge gets, right?! Is Gforge doing something with incoming mails?
I'm confused :-( I hope you can help.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(2)
看起来您可能会遇到GForge 中的此错误< /a> 阻止正确解析发送的引用打印的邮件。
你最好的选择是告诉 Swift 不要使用引用打印,但我不知道该怎么做。 (我实际上想在我自己使用 Swift 时做到这一点......)
It looks like you might be hitting this bug in GForge that prevents mails sent quoted-printable from being parsed correctly.
Your best bet is going to be telling Swift to not use quoted-printable, but I'm not sure how to do that. (I actually want to do this in my own use of Swift...)
GForge 人在这里。 FWIW,从 GForge 6.3 您可以创建自定义电子邮件地址,用于将新跟踪器项目直接提交到特定项目和跟踪器。不再向主题行添加特殊信息。
我们还改进了电子邮件的后端处理,使其更兼容各种电子邮件客户端和交换器的特性。
GForge guy here. FWIW, starting in GForge 6.3 you can create a custom email address for submitting new Tracker Items directly to a specific project and tracker. No more adding special info to the subject line.
We've also made improvements to our back-end handling of email, to make it more compatible with the quirks of various email clients and exchangers.