Zend_Mail 的 SMTP 协议问题

发布于 2024-08-13 14:14:22 字数 1861 浏览 4 评论 0原文

我正在尝试通过 GMail SMTP 发送一些电子邮件,但 CC 和 BCC 线路未收到电子邮件。我已经使用 Evolution(Linux 电子邮件客户端)测试了 GMail SMTP,它工作正常,但我无法获得通信的原始转储,因为它是通过 SSL 进行的。

这是来自 Zend_Mail 的通信日志:

220 mx.google.com ESMTP 22sm2669783yxe.39
EHLO localhost
250-mx.google.com at your service, [67.152.160.2]
250-SIZE 35651584
250-8BITMIME
250-AUTH LOGIN PLAIN
250-ENHANCEDSTATUSCODES
250 PIPELINING
AUTH LOGIN
334 VXNlcm5hbWU6
[removed]
334 UGFzc3dvcmQ6
[removed]
235 2.7.0 Accepted
MAIL FROM:[removed]
250 2.1.0 OK 22sm2669783yxe.39
RCPT TO:<[email protected]>
250 2.1.5 OK 22sm2669783yxe.39
RCPT TO:<[email protected]>
250 2.1.5 OK 22sm2669783yxe.39
RCPT TO:<[email protected]>
250 2.1.5 OK 22sm2669783yxe.39
DATA
354  Go ahead 22sm2669783yxe.39
From: [removed]
To: [email protected]
Cc: [email protected]
Subject: My Test Subject
Date: Mon, 07 Dec 2009 14:21:49 -0600
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
MIME-Version: 1.0

My test body
.
250 2.0.0 OK 1260217313 22sm2669783yxe.39

我对 SMTP 协议了解不够,无法弄清楚 Zend_Mail 没有做什么而 CC/BCC 线路需要做什么才能正常工作。

I'm trying to send some emails via GMail SMTP and the CC and BCC lines are not receiving the email. I've tested GMail SMTP with Evolution (Linux email client), which works fine, though I could not get a raw dump of the communication because it's via SSL.

Here's the communication log from Zend_Mail:

220 mx.google.com ESMTP 22sm2669783yxe.39
EHLO localhost
250-mx.google.com at your service, [67.152.160.2]
250-SIZE 35651584
250-8BITMIME
250-AUTH LOGIN PLAIN
250-ENHANCEDSTATUSCODES
250 PIPELINING
AUTH LOGIN
334 VXNlcm5hbWU6
[removed]
334 UGFzc3dvcmQ6
[removed]
235 2.7.0 Accepted
MAIL FROM:[removed]
250 2.1.0 OK 22sm2669783yxe.39
RCPT TO:<[email protected]>
250 2.1.5 OK 22sm2669783yxe.39
RCPT TO:<[email protected]>
250 2.1.5 OK 22sm2669783yxe.39
RCPT TO:<[email protected]>
250 2.1.5 OK 22sm2669783yxe.39
DATA
354  Go ahead 22sm2669783yxe.39
From: [removed]
To: [email protected]
Cc: [email protected]
Subject: My Test Subject
Date: Mon, 07 Dec 2009 14:21:49 -0600
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
MIME-Version: 1.0

My test body
.
250 2.0.0 OK 1260217313 22sm2669783yxe.39

I don't know enough about the SMTP protocol to figure out what Zend_Mail isn't doing that it needs to be doing for CC/BCC lines to work.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

明明#如月 2024-08-20 14:14:22

请参阅:http://forums.codewalkers .com/pear-packages-47/email-bcc-header-confusion-840705.html

特别是:

对于 SMTP,所有收件人都必须
在 send 中列为参数 1,并且
To/Cc/Bcc 标头的内容有
对发送的内容没有影响 - 它们是
只是接收者信息。

在我不久前做的一个项目中,我必须将电子邮件单独发送给每个密件抄送收件人。

Please see: http://forums.codewalkers.com/pear-packages-47/email-bcc-header-confusion-840705.html

In particular:

With SMTP, all recipients must be
listed as param 1 in send, and the
contents of the To/Cc/Bcc headers have
no effect on what gets sent - they are
just receiver information.

In a project that I did a while back, I had to send the email to each BCC recipient individually.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文