尝试向aws count发送电子邮件时,电子邮件帐户不存在

时间:2019-08-09 08:27:25

标签: amazon-web-services amazon-route53 laravel-forge amazon-workmail amazon-simple-email-service

我正在设置aws电子邮件帐户(工作邮件),因此在接收邮件方面存在问题。 (我必须承认这是我第一次与aws接触,而且我对此服务知之甚少)

我正在使用AWS服务:

  • WorkMail
  • 简单的电子邮件服务
  • 53号公路
  • S3

要托管Web服务器,我们使用laravel forge(带有nginx文件配置和Wordpress)。 WordPress正在使用“ WP Mail SMTP”插件。

按照(tutorial),我已经完成了从头到尾的所有步骤。

当我为电子邮件服务配置Route53可以发送和接收(SES和WorkMail)时出现问题。好的,当我发送带有“ example@domain.es”的电子邮件时,效果很好。但是,当我尝试从gmail接收邮件时,他们会向我显示下一个:

550 5.1.1 The email account that you tried to reach does not exist. 

我从测试中创建了电子邮件,并且可以在工作邮件面板上看到它。但是没有收到任何电子邮件到收件箱。

我附上快照以说明问题。

enter image description here

enter image description here

我将nginx文件添加到:

        # FORGE CONFIG (DO NOT REMOVE!)
    include forge-conf/route.es/before/*;

    server {
        listen 443 ssl http2;
        listen [::]:443 ssl http2;
        server_name route.es;
        #server_name *.route.es;
        #server_name route.es;
        root /home/forge/route.es/;

        # FORGE SSL (DO NOT REMOVE!)
        ssl_certificate /etc/nginx/ssl/route.es/577719/server.crt;
        ssl_certificate_key /etc/nginx/ssl/route.es/577719/server.key;

        ssl_protocols TLSv1.2;
        ssl_ciphers ECDHE-RSA-AES256-GCM-SHA512:DHE-RSA-AES256-GCM-SHA512:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-SHA384;
        ssl_prefer_server_ciphers on;
        ssl_dhparam /etc/nginx/dhparams.pem;

        add_header X-Frame-Options "SAMEORIGIN";
        add_header X-XSS-Protection "1; mode=block";
        add_header X-Content-Type-Options "nosniff";

        index index.html index.htm index.php;

        charset utf-8;

        # FORGE CONFIG (DO NOT REMOVE!)
        include forge-conf/route.es/server/*;

        location / {
            try_files $uri $uri/ /index.php?$query_string;
        }

        location = /favicon.ico { access_log off; log_not_found off; }
        location = /robots.txt  { access_log off; log_not_found off; }

        access_log off;
        error_log  /var/log/nginx/route.es-error.log error;

        error_page 404 /index.php;

        location ~ \.php$ {
            fastcgi_split_path_info ^(.+\.php)(/.+)$;
            fastcgi_pass unix:/var/run/php/php7.2-fpm.sock;
            fastcgi_index index.php;
            include fastcgi_params;
        }

        location ~ /\.(?!well-known).* {
            deny all;
        }
    }
# FORGE CONFIG (DO NOT REMOVE!)
include forge-conf/route.es/after/*;

在这里,我显示在工作邮件中创建的邮件列表:

enter image description here

1 个答案:

答案 0 :(得分:1)

是“ 550 5.1.1您尝试访问的电子邮件帐户不存在。”来自SES还是Google?

您有多条MX记录,并且SES的优先级为10,它将无法到达SES接收端点。

dig pxxxxxxxxxxxx.es mx +short
1 aspmx.l.google.com.
10 alt3.aspmx.l.google.com.
10 alt4.aspmx.l.google.com.
10 inbound-smtp.eu-west-1.amazonaws.com.
5 alt1.aspmx.l.google.com.
5 alt2.aspmx.l.google.com.

SES is configured fine:
220 inbound-smtp.eu-west-1.amazonaws.com ESMTP Amazon SES 
mail from: admin@admin.com
250 Ok
rcpt to:info@pxxxxxxxxxxxxxxxx.es
250 Ok