fat*_*tic 33 smtp amazon-ec2 amazon-web-services amazon-ses
尝试使用SMTP从我的EC2实例发送电子邮件到SES时出现问题.出于某种原因,我遇到零星的超时问题,我无法再联系SMTP主机.值得注意的是,通过SES发送可能有75%的时间.
我将从一些细节开始.我的SES帐户大部分时间都在工作.发件人电子邮件已经过验证,我的限制已增加到10k /天,每封5封电子邮件.我的印象是,如果这与我的限制有关,我会得到一个限制特定的错误.对于我的SMTP配置,我使用posfix w/TLS.我在官方AWS SES论坛上发布了一篇非常类似的帖子,但还没有取得任何成功.该帖子的信息位于此帖的底部.
这是今天早上失败的一个例子.我在下面运行的所有命令都是从我尝试发送邮件的EC2实例运行的.对不起这本小说大小的帖子,我只想确保包含所有内容.
我发给自己的电子邮件没有送达:
Jun 25 06:16:36 intranet01 postfix/smtp18832: 9E00C230DA: to=<myemailaddress>, relay=none, delay=150, delays=0.02/0.01/150/0, dsn=4.4.1, status=deferred (connect to email-smtp.us-east-1.amazonaws.comhttp://107.22.187.122:25: Connection timed out)
Run Code Online (Sandbox Code Playgroud)
当我看到失败时,我尝试通过端口25连接到电子邮件主机.我无法连接:
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 174.129.28.151...
^C
Run Code Online (Sandbox Code Playgroud)
几分钟后,我的延期电子邮件终于通过了:
Jun 25 06:23:14 intranet01 postfix/smtp18861: 9E00C230DA: to=<myemailaddress>, relay=email-smtp.us-east-1.amazonaws.comhttp://184.73.218.23:25, delay=548, delays=548/0.02/0.21/0.36, dsn=2.0.0, status=sent (250 Ok 0000013823cf7441-83710873-e946-4c80-8a54-0dd72bae6f30-000000)
Jun 25 06:23:14 intranet01 postfix/qmgr3972: 9E00C230DA: removed
Run Code Online (Sandbox Code Playgroud)
现在我可以连接到端口25:
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 107.20.152.208...
Connected to email-smtp.us-east-1.amazonaws.com.
Escape character is '^]'.
220 email-smtp.amazonaws.com ESMTP SimpleEmailService-222567251
^]
Run Code Online (Sandbox Code Playgroud)
对于踢,我决定查看SES主机端点.事实证明它只是一个ELB cname,A记录指向多个AZ中的接口.
root@intranet01 sbin# dig email-smtp.us-east-1.amazonaws.com
; <<>> DiG 9.7.3-P3-RedHat-9.7.3-8.P3.17.amzn1 <<>> email-smtp.us-east-1.amazonaws.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8592
;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;email-smtp.us-east-1.amazonaws.com. IN A
;; ANSWER SECTION:
email-smtp.us-east-1.amazonaws.com. 54 IN CNAME ses-smtp-prod-335357831.us-east-1.elb.amazonaws.com.
ses-smtp-prod-335357831.us-east-1.elb.amazonaws.com. 60 IN A 174.129.200.82
ses-smtp-prod-335357831.us-east-1.elb.amazonaws.com. 60 IN A 184.73.219.75
ses-smtp-prod-335357831.us-east-1.elb.amazonaws.com. 60 IN A 107.20.152.208
ses-smtp-prod-335357831.us-east-1.elb.amazonaws.com. 60 IN A 107.20.160.81
ses-smtp-prod-335357831.us-east-1.elb.amazonaws.com. 60 IN A 107.20.203.50
ses-smtp-prod-335357831.us-east-1.elb.amazonaws.com. 60 IN A 107.22.229.233
ses-smtp-prod-335357831.us-east-1.elb.amazonaws.com. 60 IN A 174.129.6.189
ses-smtp-prod-335357831.us-east-1.elb.amazonaws.com. 60 IN A 174.129.28.151
Run Code Online (Sandbox Code Playgroud)
我尝试发送另一条消息,但失败了.这次我遍历了SES cname返回的每个A记录地址.我无法连接到他们中的任何一个.在这段时间里,我也尝试从我的本地机器(不是我的EC2实例)连接,它工作得很好.
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 174.129.28.151...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 174.129.6.189...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 107.22.229.233...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 107.20.203.50...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 107.20.160.81...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 107.20.152.208...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 184.73.219.75...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 174.129.200.82...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 174.129.28.151...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 174.129.6.189...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 107.22.229.233...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 107.20.203.50...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 107.20.179.13...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 107.20.160.81...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 184.73.219.75...
^C
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 174.129.200.82...
^C
Run Code Online (Sandbox Code Playgroud)
等了大约30秒后我再次尝试,这次它起作用了.
root@intranet01 sbin# telnet email-smtp.us-east-1.amazonaws.com 25
Trying 174.129.28.151...
Connected to email-smtp.us-east-1.amazonaws.com.
Escape character is '^]'.
220 email-smtp.amazonaws.com ESMTP SimpleEmailService-222567251
^C^[
^]
telnet>
Run Code Online (Sandbox Code Playgroud)
正如我之前所说,我在AWS SES论坛上发布了一篇非常类似的帖子.这篇文章可以在下面找到.
https://forums.aws.amazon.com/thread.jspa?threadID=97736&tstart=0
此外,似乎我并不孤单,因为我在SES论坛上发现了这个其他帖子,看起来像是同样的问题.
https://forums.aws.amazon.com/thread.jspa?threadID=91260&tstart=0
我认为可能存在某种EC2 SMTP限制,所以我填写了"从EC2发送电子邮件"请求表单,但由于我使用亚马逊的服务而不是第三方,因此对我来说似乎很愚蠢.到目前为止,我在填写表格后没有收到亚马逊的回复.
有没有人有任何想法?提前致谢.
fat*_*tic 48
显然EC2有它自己的极限.我假设(错误地)对SES进行生产访问也意味着放宽了对EC2的SMTP限制,但由于它们是两个完全独立的产品,我想情况并非如此.
但正如我在帖子的最后一段中所述,您可以请求删除电子邮件发送限制以提高这些限制.我这样做了,问题就停止了(他们花了大约5个小时才取消限制).
EC2限制记录在连接到Amazon SES SMTP端点并实际约束到端口25,因此另一种直接解决方案是使用端口587(有些不幸的是,几个官方SES示例确实使用端口25):
重要
默认情况下,弹性计算云(EC2)会限制端口25上的电子邮件流量.为避免从EC2通过SMTP端点发送电子邮件时出现超时,请使用其他端口(587或2587)或填写" 删除电子邮件发送限制请求"以删除限制.
请注意,这可能会稍微过时,因为AWS管理控制台和Amazon SES SMTP问题部分仅涉及更常见的备用端口465和587:
您是通过端口25从Amazon EC2实例发送到Amazon SES而您无法达到您的Amazon SES发送限制或者您正在接收超时 - Amazon SES EC2对通过端口25发送的电子邮件施加默认发送限制,并且如果您尝试,则限制出站连接超过这些限制.要删除这些限制,请提交删除电子邮件发送限制的 请求.您还可以通过端口465或端口587连接到Amazon SES,这两个端口都不受限制.
| 归档时间: |
|
| 查看次数: |
23603 次 |
| 最近记录: |