-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 24/8/19 7:51 pm, Andrew McGlashan wrote:
> but most already email users won't have a clue.
... but most *ordinary* email users ...
And an Enigmail setting gives me the confirmation before sending (not
TB itself).
A.
-BEGIN PGP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 24/8/19 7:24 pm, Reco wrote:
> On Sat, Aug 24, 2019 at 03:27:09PM +1000, Andrew McGlashan wrote:
>> Okay, I've changed the the DKIM_SIGN_HEADERS ... let's see if
>> this is good, thanks
>
> This e-mail passed DKIM check for me, previous one
Hi.
On Sat, Aug 24, 2019 at 03:27:09PM +1000, Andrew McGlashan wrote:
> Okay, I've changed the the DKIM_SIGN_HEADERS ... let's see if this is
> good, thanks
This e-mail passed DKIM check for me, previous one failed it.
> > Also, "Autocrypt: prefer-encrypt=mutual" for a list mail?
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 22/8/19 7:52 pm, Reco wrote:
> On Thu, Aug 22, 2019 at 07:27:23PM +1000, Andrew McGlashan wrote: >> I have
> DKIM setup, however, it only signs messages that are being >>
delivered via SMTP to another server. > > Your DKIM policy is
Hi.
On Thu, Aug 22, 2019 at 07:27:23PM +1000, Andrew McGlashan wrote:
> I have DKIM setup, however, it only signs messages that are being
> delivered via SMTP to another server.
Your DKIM policy is somewhat unusual. You sign transport headers
(Resent-From et al), headers inserted by list
> Hi,
>
> I have DKIM setup, however, it only signs messages that are being
> delivered via SMTP to another server.
>
> Why is it not valid to sign to the same domain name and/or other
> domain names served by the same mail server and NOT having to make an
> SMTP outgoing connection?
>
> How
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
I have DKIM setup, however, it only signs messages that are being
delivered via SMTP to another server.
Why is it not valid to sign to the same domain name and/or other
domain names served by the same mail server and NOT having to make an
SMTP
7 matches
Mail list logo
