Re: [exim] NFSv4: failed to set ownership on spool file

2019-01-29 Thread Phil Pennock via Exim-users
On 2019-01-29 at 10:30 +0100, Heiko Schlittermann via Exim-users wrote: > - The tcpdump show a V4 SETATTR, but only for the owner (I'd have > expected the group too), AND the owner is numerical, not user@domain, > as I would have expected. The pcap file is attached. It's showing a GETATTR,

Re: [exim] Expiriences with TLS 1.3

2019-01-29 Thread Phil Pennock via Exim-users
On 2019-01-28 at 15:09 +, Andrew C Aitchison via Exim-users wrote: > I see many header lines like: > > Received: from smtp.spodhuis.org ([2a02:898:31:0:48:4558:736d:7470]:34422 > helo=mx.spodhuis.org) > by hummus.csx.cam.ac.uk with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) > (Exim 4.91)

Re: [exim] Expiriences with TLS 1.3

2019-01-29 Thread Max Kostikov via Exim-users
Viktor Dukhovni via Exim-users писал 2019-01-29 19:18: On Tue, Jan 29, 2019 at 06:53:33PM +0200, Max Kostikov via Exim-users wrote: Jeremy Harris via Exim-users писал 2019-01-28 13:56: > I've not seen any such connections in production yet. FreeBSD 12 have OpenSSL 1.1.1 in base system so I

Re: [exim] Expiriences with TLS 1.3

2019-01-29 Thread Viktor Dukhovni via Exim-users
On Tue, Jan 29, 2019 at 06:53:33PM +0200, Max Kostikov via Exim-users wrote: > Jeremy Harris via Exim-users писал 2019-01-28 13:56: > > I've not seen any such connections in production yet. > > FreeBSD 12 have OpenSSL 1.1.1 in base system so I see entries in the > Exim log. For the record, not

Re: [exim] Expiriences with TLS 1.3

2019-01-29 Thread Max Kostikov via Exim-users
Jeremy Harris via Exim-users писал 2019-01-28 13:56: I've not seen any such connections in production yet. FreeBSD 12 have OpenSSL 1.1.1 in base system so I see entries in the Exim log. Jan 29 08:30:44 beta exim[2522]: 1goMux-eg-Dq <= bugzilla-nore...@freebsd.org H=mx2.freebsd.org

Re: [exim] NFSv4: failed to set ownership on spool file

2019-01-29 Thread Heiko Schlittermann via Exim-users
Graeme Fowler via Exim-users (Di 29 Jan 2019 11:03:19 CET): > Have you got ‘superuser’ mapping switched on so root maps to UID 0 on the NFS > server? Processes with uid=0 can create and chown files on the share. So I'd say, root_squash is not enabled. > This is referred to as no_root_squash

Re: [exim] Expiriences with TLS 1.3

2019-01-29 Thread Jeremy Harris via Exim-users
On 28/01/2019 10:50, Cyborg via Exim-users wrote: > is anyone of you running TLS 1.3 already ? In other related news, iOS 12.2 (just out for developers) enables TLS 1.3 by default. -- Cheers, Jeremy -- ## List details at https://lists.exim.org/mailman/listinfo/exim-users ## Exim details at

Re: [exim] NFSv4: failed to set ownership on spool file

2019-01-29 Thread Graeme Fowler via Exim-users
On 29 Jan 2019, at 09:30, Heiko Schlittermann via Exim-users wrote: > - How did you solve it? Have you got ‘superuser’ mapping switched on so root maps to UID 0 on the NFS server? This is referred to as no_root_squash in the client mount options; I suspect you need to permit the NFS client

[exim] NFSv4: failed to set ownership on spool file

2019-01-29 Thread Heiko Schlittermann via Exim-users
Hi, we run Exim with $spool_directory on a NFSv4 Share. I do not know the gory details of NFSv4 and what operations are expected to work and which operations are expected to break. - UID mapping seems to be enabled (the files have the right owner, if the id-mapping domains on both sides