AWS re:Postを使用することにより、以下に同意したことになります AWS re:Post 利用規約

AWS Lightsail - Ubuntu 16 Plesk - Mail Server/SMTP Blocked

0

Hi,

I have:

  1. Created Ubuntu 16.04 container.
  2. Created static IP.
  3. Attached static IP to the container.
  4. Installed Plesk on it.
  5. Moved content and data from current non-AWS hosting provider to the container.
  6. Configure entire data (hosting settings, certificates and so on), except emails, because Plesk says that it's been blocked, and I have to submit request AWS to release email features.

So, I made a request, explaining the cases of use (replaced sensitive data with uppercase general words)

We're migrating from COMPANY to AWS Lightsail. Server runs our applications that have to be able to use email to notify clients. Also, on the server configured email accounts of support and managers. During Plesk configuration noticed that port 25 is blocked by AWS, so I ask to remove any restriction from port 25 and setup rDNS for DOMAIN (at the moment it's point to old server IP, but today, when I finish the setup - I gonna change it to the static AWS IP).

and received

This account, or those linked to it, have been identified as having at least one of the following: * A history of violations of the AWS Acceptable Use Policy * A history of being not consistently in good standing with billing * Not provided a valid/clear use case to warrant sending mail from EC2

I just created account and haven't started using AWS service to have history of violations or of problems with billing. It's means that I provided unclear case of use, so I replied with additional information.

What exactly isn't clear?
1. We do not send spam.
At the moment our server at COMPANY and it's has 
perfect email configuration
LINK_TO_MXTOOLBOX_TEST
never blacklisted
LINK_TO_MXTOOLBOX_BLACKLIST
2. Our SaaS products use email server to send notifications to subscribed existing business clients.
3. Our staff also use the email server (support and management teams).

Result - same 'template' of response.

and one more request

Email server will be used in 2 cases: The first one is used by services on domains DOMAIN and DOMAIN to send notifications to the COMPANY active business clients. The second one is email accounts of support team and management of COMPANY .

Once again, result - same 'template' of response.

It's a bit confused me, so I asked "What exactly the problem?" and received

After a thorough review, we confirmed our original finding and cannot grant your request.

Please consider looking into the Simple Email Service (SES) https://aws.amazon.com/ses/.

We cannot assist you further with this issue and we may not respond to additional messages on this subject.

No answers, only 'templates'.

So, how can I resolve such situation when on each request receive 'template' with 'not answers' and forcing attempt sale me SES (which I don't want at all)?

1回答
0

Hello,

The team you contacted is the correct team to resolve this issue. If you need to utilize port 25, you will need to provide a justified use case to them. If you're looking for an alternative solution, SES is a great option. There are other 3rd party mail sending partners you could utilize as well. You could also use an SMTP solution that utilizes a different port such as 465 or 587.

While I do understand your frustration around blocking port 25, it is necessary to prevent abuse across AWS.

For others looking how to contact support to remove the block, here is the relevant documentation.

profile pictureAWS
エキスパート
回答済み 2年前

ログインしていません。 ログイン 回答を投稿する。

優れた回答とは、質問に明確に答え、建設的なフィードバックを提供し、質問者の専門分野におけるスキルの向上を促すものです。

質問に答えるためのガイドライン

関連するコンテンツ