From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on
	ip-172-31-74-118.ec2.internal
X-Spam-Level: *
X-Spam-Status: No, score=1.8 required=3.0 tests=BAYES_50,FREEMAIL_FROM,
	PDS_FROM_2_EMAILS autolearn=no autolearn_force=no version=3.4.6
X-Received: by 2002:a37:a4c5:: with SMTP id n188mr13773244qke.273.1630981228205;
        Mon, 06 Sep 2021 19:20:28 -0700 (PDT)
X-Received: by 2002:a25:5444:: with SMTP id i65mr19840687ybb.277.1630981227455;
 Mon, 06 Sep 2021 19:20:27 -0700 (PDT)
Path: eternal-september.org!reader02.eternal-september.org!news.misty.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Mon, 6 Sep 2021 19:20:27 -0700 (PDT)
In-Reply-To: <sh4ms3$ubs$1@dont-email.me>
Injection-Info: google-groups.googlegroups.com; posting-host=216.215.19.89; posting-account=XGCYegoAAADY19DGgU_zTfTSbVlfUJ_a
NNTP-Posting-Host: 216.215.19.89
References: <30267029-4433-4f45-a409-debf68fb27ccn@googlegroups.com> <sh4ms3$ubs$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <eaac8f2d-ab6e-4c55-b0df-6d873e2a4f9dn@googlegroups.com>
Subject: Re: AWS.SMTP.Client secure mode
From: "philip...@gmail.com" <philip.munts@gmail.com>
Injection-Date: Tue, 07 Sep 2021 02:20:28 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: reader02.eternal-september.org comp.lang.ada:62662
List-Id: <comp.lang.ada>

On Monday, September 6, 2021 at 2:26:30 AM UTC-7, bj=C3=B6rn lundin wrote:
> Den 2021-09-05 kl. 05:20, skrev philip...@gmail.com:=20
>=20
> >=20
> > Has anyone ever got secure and authenticated AWS.SMTP.Client working? A=
nd if so, how did you do it?=20
> >
> Yes.=20
> I use Amazon as mailer - like this. Shortened version so it might not=20
> compile. I think you need the Ada.Directories.Set_Directory statement=20
> just as I need it.=20
>=20
> in the directory I set , I have the cert.pem I'd like to use=20

Is cert.pem a client certificate that will be passed to the server, or is i=
t a server certificate the client uses to validate the server?

As far as I know, none of the mail servers I am dealing with have any mecha=
nism to register client certificates.