AWS SES 将休假响应者视为退回
AWS SES is treating vacation responder as bounce
我们使用 aws 服务器，我们的应用程序通过亚马逊的简单电子邮件服务 (SES) 向客户发送电子邮件。
当收件人打开外出回复时，SES 将他们视为退回并在发送几次后阻止该电子邮件 ID。
这是 SES 的标准问题还是我遗漏了什么？任何帮助将不胜感激。
这就是我的 PHP 代码通过 ses
发送电子邮件的方式
define( 'AWSAccessKeyId', $this->SNS_Access_Key_Id );
define( 'AWSSecretKey', $this->SNS_Secret_Key_Id );
$transport = Swift_AWSTransport::newInstance( AWSAccessKeyId, AWSSecretKey );
$transport->setDebug( true );
$mailer = Swift_Mailer::newInstance( $transport );
$message = Swift_Message::newInstance()
->setSubject( $email_subject )
->setFrom( array( $from_email_id ) )
->setTo( $to_email_id_array )
->setBody( $email_body, 'text/html' );
$response = $mailer->send( $message );
我的谷歌搜索为您提供了一些相关资源：
You are notified of out-of-the-office (OOTO) messages through the same method as bounces, although they don't count toward your bounce statistics. To see an example of an OOTO bounce notification, you can use the Amazon SES mailbox simulator.
Using Notifications with Amazon SES
Bounce — The recipient's ISP rejects your email with an SMTP 550 5.1.1 response code ("Unknown User"). Amazon SES generates a bounce notification and sends it to you via email or by using an Amazon SNS notification, depending on how you set up your system. This mailbox simulator email address will not be placed on the Amazon SES suppression list as one normally would when an email hard bounces. The bounce response that you receive from the mailbox simulator is compliant with RFC 3464.
Testing Amazon SES Email Sending
Amazon SES has an understanding of the different reasons messages bounce. If SES detects a hard bounce, it will add the address to a temporary "blacklist". I believe "out of office" messages will not be counted as bounces. They will be forwarded to you but not show up as a bounce.
我们使用 aws 服务器，我们的应用程序通过亚马逊的简单电子邮件服务 (SES) 向客户发送电子邮件。
当收件人打开外出回复时，SES 将他们视为退回并在发送几次后阻止该电子邮件 ID。
这是 SES 的标准问题还是我遗漏了什么？任何帮助将不胜感激。
这就是我的 PHP 代码通过 ses
发送电子邮件的方式define( 'AWSAccessKeyId', $this->SNS_Access_Key_Id );
define( 'AWSSecretKey', $this->SNS_Secret_Key_Id );
$transport = Swift_AWSTransport::newInstance( AWSAccessKeyId, AWSSecretKey );
$transport->setDebug( true );
$mailer = Swift_Mailer::newInstance( $transport );
$message = Swift_Message::newInstance()
->setSubject( $email_subject )
->setFrom( array( $from_email_id ) )
->setTo( $to_email_id_array )
->setBody( $email_body, 'text/html' );
$response = $mailer->send( $message );
我的谷歌搜索为您提供了一些相关资源：
You are notified of out-of-the-office (OOTO) messages through the same method as bounces, although they don't count toward your bounce statistics. To see an example of an OOTO bounce notification, you can use the Amazon SES mailbox simulator.
Using Notifications with Amazon SES
Bounce — The recipient's ISP rejects your email with an SMTP 550 5.1.1 response code ("Unknown User"). Amazon SES generates a bounce notification and sends it to you via email or by using an Amazon SNS notification, depending on how you set up your system. This mailbox simulator email address will not be placed on the Amazon SES suppression list as one normally would when an email hard bounces. The bounce response that you receive from the mailbox simulator is compliant with RFC 3464.
Testing Amazon SES Email Sending
Amazon SES has an understanding of the different reasons messages bounce. If SES detects a hard bounce, it will add the address to a temporary "blacklist". I believe "out of office" messages will not be counted as bounces. They will be forwarded to you but not show up as a bounce.