On Tuesday, April 09, 2019 08:50:52 AM Bill Cole wrote:
> On 9 Apr 2019, at 5:36, Ntek, SIA Janis wrote:
> > What's your key-size?
> > My DNS provider does not support 2048, I found it out the hard way.
>
> Note that this is usually due to a 255-character limit on a single
> string in a TXT record
On 9 Apr 2019, at 5:36, Ntek, SIA Janis wrote:
What's your key-size?
My DNS provider does not support 2048, I found it out the hard way.
Note that this is usually due to a 255-character limit on a single
string in a TXT record. This is because the character-string type in DNS
is defined as a
* SIA Janis Ntek:
> Why do use
> > inet:localhost:8891
> Instead of a socket?
Probably because the above stream socket is, unfortunately, what is to
this day used in both opendkim.conf.simple and opendkim.conf.sample in
the source code, although a domain socket would be safer in terms of
access r
-Original Message-
From: owner-postfix-us...@postfix.org On
Behalf Of Laura Smith
Sent: Tuesday, April 9, 2019 5:43 AM
To: Jim P.
Cc: postfix-users@postfix.org
Subject: Re: OpenDKIM not signing
‐‐‐ Original Message ‐‐‐
On Tuesday, April 9, 2019 9:40 AM, Jim P. wrote:
> On Tue, 2019
Apr 9 09:40:14 rx200 mail.info opendkim[4396]: C03DE1014429:
foobar.example.com [192.0.2.10] not internal
It seems that the domain you want to sign is not in the KeyTable or
SigningTable! Note that if you put "refile:" before config file path in
/etc/opendkim.conf the syntax changes!
If
Si
‐‐‐ Original Message ‐‐‐
On Tuesday, April 9, 2019 9:40 AM, Jim P. wrote:
> On Tue, 2019-04-09 at 08:22 +, Laura Smith wrote:
>
> > OpenDKIM is not signing my mails.
>
> .
>
> > KeyTable /etc/opendkim/KeyTable
>
> I think this should be:
>
> KeyTable refile:/etc/ope
What's your key-size?
My DNS provider does not support 2048, I found it out the hard way. 1024
seems to be the most popular size and google demands at least 1024.
Ounce you get the signing working you can regen a 2048 and check if you
can feed it in DNS TXT, but for first testing stick to 1024
.
And just a question, the DNS is already updated?
Greetz,
Louis
> -Oorspronkelijk bericht-
> Van: i...@ntek.lv [mailto:owner-postfix-us...@postfix.org]
> Namens Ntek, SIA Janis
> Verzonden: dinsdag 9 april 2019 11:19
> Aan: postfix-users@postfix.org
> Onderwerp
Why do use
inet:localhost:8891
Instead of a socket?
I conf'ed it using this tutorial:
https://www.linode.com/docs/email/postfix/configure-spf-and-dkim-in-postfix-on-debian-8/
smtpd_milters = local:opendkim/opendkim.sock
non_smtpd_milters = local:opendkim/opendkim.sock
The sockets are relative p
On Tue, 9 Apr 2019 at 09:41, Jim P. wrote:
> On Tue, 2019-04-09 at 08:22 +, Laura Smith wrote:
> > OpenDKIM is not signing my mails.
> .
> > KeyTable/etc/opendkim/KeyTable
>
> I think this should be:
>
> KeyTablerefile:/etc/opendkim/KeyTable
>
>
> > Interna
On Tue, 2019-04-09 at 08:22 +, Laura Smith wrote:
> OpenDKIM is not signing my mails.
.
> KeyTable /etc/opendkim/KeyTable
I think this should be:
KeyTablerefile:/etc/opendkim/KeyTable
> InternalHosts refile:/etc/opendkim/TrustedHosts
Try using E
Based on the responses to my previous question about using OpenDKIM (quite what
"standards have not changed" has to do with software bugs makes no sense to me
!). However, having been told I'm stupid not to continue using software many
years old I thought I would suck it up and continue with Ope
12 matches
Mail list logo
