Hello misc@,
I'm currently working on adding ed25519 support to filter-dkimsign, but
I'm getting some mixed results with the different validators.
gmail: permfail => claims the key is missing
outlook: fail (signature syntax error)
protonmail: 2 headers
1st: permerror (0-bit key)
2nd: pa
Eric Faurot wrote:
> On Fri, May 07, 2021 at 01:42:52AM +0200, Markus Julen wrote:
> > Hi all!
> >
> > Having just moved a small "outgoing only" mailserver to 6.9, I started to
> > receive error messages:
> >
> > > 80008bb60b9428ed smtp connected address=X.X.X.X host=z.z.z
> > > 80008bb60b9428e
I was pondering a message Gille Chehade commented on
(https://narkive.com/2puCGKoq.4) a very long time ago.
He said:
> The cert verification happens at the transport level, not the SMTP level
> and an invalid certificate will cause TLS to abort and close connection.
>
> You can use this for exam
Hi folks,
I am a big fan of IPv6, so I wonder why smtpctl spf walk omits
all the IPv6 addresses?
# echo spf.protection.outlook.com | smtpctl spf walk
40.92.0.0/15
40.107.0.0/16
52.100.0.0/14
104.47.0.0/17
51.4.72.0/24
51.5.72.0/24
5
Harald Dunkel wrote:
> Hi folks,
>
> I am a big fan of IPv6, so I wonder why smtpctl spf walk omits
> all the IPv6 addresses?
>
> # echo spf.protection.outlook.com | smtpctl spf walk
> 40.92.0.0/15
> 40.107.0.0/16
> 52.100.0.0/14
> 104.47.0.0/17
> 51.4.72.0/24