On Thu, Sep 30, 2021 at 02:28:11AM -0400, Viktor Dukhovni
wrote:
> On Thu, Sep 30, 2021 at 03:50:41PM +1000, raf wrote:
>
> > > No, because you don't get to choose which CA signed your certificates.
>
> I meant to say "your *peer's* certificates".
>
> > This is what I was expecting to be the
Hi,
I am setting an archiving mail server using a sub-domain of a
relay_domains on the same server as a virtual_mailbox_domains, so every
message relayed to f...@example.tld (On Microsoft cloud) is also archived
on f...@sub.example.tld (my on-premise mail server) using some bcc trick.
rel
30.09.21, 16:29 +0200, Marcio Merlone:
I am setting an archiving mail server using a sub-domain of a
relay_domains on the same server as a virtual_mailbox_domains, so every
message relayed to f...@example.tld (On Microsoft cloud) is also archived
on f...@sub.example.tld (my on-premise mail serve
Em 30/09/2021 11:46, Markus Schönhaber escreveu:
30.09.21, 16:29 +0200, Marcio Merlone:
I am setting an archiving mail server using a sub-domain of a
relay_domains on the same server as a virtual_mailbox_domains, so every
message relayed to f...@example.tld (On Microsoft cloud) is also archived
The DANE survey continues to observe a "long tail" of MX hosts with TLSA
records that match the retired "X3" and/or "X4" Let's Encrypt issuer Cas.
If you're publishing TLSA records with Let's Encrypt issuer CA hashes,
the "X3" and "X4" CAs should no longer appear in your TLSA RRset. Also
be sure
Le 29.09.2021 à 06:33, Viktor Dukhovni a écrit :
On Wed, Sep 29, 2021 at 02:19:53PM +1000, raf wrote:
If you really have a problem that you think would be
solved by relocating the hold queue, you could mount
another file system over the hold queue directory.
That might work. But it might a ba
