Merge branch 'alternate-submission-port' of https://github.com/embusalacchi/docker-postfix into alternate-submission-port

.github/workflows/master.yml

@@ -84,7 +84,7 @@ jobs:
           update-binfmts --enable
 
       - name: Build and push Alpine
-        uses: docker/build-push-action@v5
+        uses: docker/build-push-action@v6
         with:
           context: .
           push: true
@@ -132,7 +132,7 @@ jobs:
             ${{ runner.os }}-ubuntu-
 
       - name: Build and push Ubuntu
-        uses: docker/build-push-action@v5
+        uses: docker/build-push-action@v6
         with:
           context: .
           push: true
@@ -176,7 +176,7 @@ jobs:
             ${{ runner.os }}-debian-
 
       - name: Build and push Debian
-        uses: docker/build-push-action@v5
+        uses: docker/build-push-action@v6
         with:
           context: .
           push: true

.github/workflows/pull_request.yml

@@ -65,7 +65,7 @@ jobs:
           update-binfmts --enable
 
       - name: Build Alpine
-        uses: docker/build-push-action@v5
+        uses: docker/build-push-action@v6
         with:
           context: .
           push: false

.github/workflows/tags.yml

@@ -89,7 +89,7 @@ jobs:
           update-binfmts --enable
 
       - name: Build and push Alpine
-        uses: docker/build-push-action@v5
+        uses: docker/build-push-action@v6
         with:
           context: .
           push: true
@@ -141,7 +141,7 @@ jobs:
             ${{ runner.os }}-ubuntu-
 
       - name: Build and push Ubuntu
-        uses: docker/build-push-action@v5
+        uses: docker/build-push-action@v6
         with:
           context: .
           push: true
@@ -191,7 +191,7 @@ jobs:
             ${{ runner.os }}-debian-
 
       - name: Build and push Debian
-        uses: docker/build-push-action@v5
+        uses: docker/build-push-action@v6
         with:
           context: .
           push: true

README.md

@@ -755,10 +755,16 @@ There's no need to configure DKIM or SPF, as Gmail will add these headers automa
 
 If your application runs in Amazon Elastic Compute Cloud (Amazon EC2), you can use Amazon SES to send up to 62,000 emails
 every month at no additional charge. You'll need an AWS account and SMTP credentials. The SMTP settings are available
-on the SES page. For example, for `eu-central-1`:
+on the SES page. 
 
-- see the [SES page for details](https://eu-central-1.console.aws.amazon.com/ses/home?region=eu-central-1#smtp-settings),
-- [create the user credentials](https://console.aws.amazon.com/iam/home?#s=SESHomeV4/eu-central-1)
+For example, for `eu-central-1`:
+
+- Please See the [SES Page for Details](https://eu-central-1.console.aws.amazon.com/ses/home?region=eu-central-1#smtp)
+
+You need Amazon SES SMTP credentials to access the SES SMTP interface.
+**NOTE:** Your SMTP password is different from your AWS secret access key.  Additionally, the credentials that you use to send email through the SES SMTP interface are unique to each _AWS Region_. If you use the SES SMTP interface to send email in more than one Region, you must generate a set of SMTP credentials for each Region that you plan to use.
+
+- [Create or Obtain the User Credentials](https://docs.aws.amazon.com/ses/latest/dg/smtp-credentials.html)
 
 **Make sure you write the user credentials down, as you will only see them once.**