search for: mailman3

...uot;"Tuesday April 8th, 7:00 am UTC time"""". You can convert to local time with $(date -d '2024-04-08 07:00 UTC') The expected "downtime" is estimated to ~60 minutes , time needed to : - take last mailman2 backup - reimport / convert mailman2 archives to mailman3 DB - DNS propagation for A/AAAA/MX records Here are also some important information about the mailman2 => mailman3 migration : # Renamed lists Worth knowing that, based on open discussion on the centos-devel list (see whole thread at https://lists.centos.org/pipermail/centos-devel/2024-Marc...

...uot;"Tuesday April 8th, 7:00 am UTC time"""". You can convert to local time with $(date -d '2024-04-08 07:00 UTC') The expected "downtime" is estimated to ~60 minutes , time needed to : - take last mailman2 backup - reimport / convert mailman2 archives to mailman3 DB - DNS propagation for A/AAAA/MX records Here are also some important information about the mailman2 => mailman3 migration : # Renamed lists Worth knowing that, based on open discussion on the centos-devel list (see whole thread at https://lists.centos.org/pipermail/centos-devel/2024-Marc...

Am 09.02.19 um 19:56 schrieb Aki Tuomi via dovecot: > I'll review the settings when we manage to upgrade to mailman3 Hello Aki, before updating to mailman3 consider an simpler update to latest mailman2. you're using 2.1.15, current mailman2 is 2.1.29 Your missing an /significant amount/ of DMARC fixes! and: more off-topic: while my messages *to* the dovecot list are sent using STARTTLS, messages *from* w...

...to either vault or have internal mirror but at least people would be aware that distro itself is EOL and that they shouldn't expect to receive any update anymore # CentOS mailing-lists Currently running on mailman2 stack, on top of CentOS 7 linux : there is WIP to port everything to up2date mailman3 stack, actually packaged for EPEL9. We have successfully imported archives into mailman3 and same for lists config but let's start a different/separate thread to discuss changes (like renaming lists, see next coming thread) Kind Regards, -- Fabian Arrotin The CentOS Project | https://www....

...s to have the working group established by the IETF 121 meeting in Dublin (very early November). Note: I'm sending this to both the new ssh list (ssh at ietf.org) and the old list. For those on the old list, if you are interested in participating please feel free to join the new list ( https://mailman3.ietf.org/mailman3/lists/ssh.ietf.org/ ) Deb Cooley Security Area Director _______________________________________________ Ssh mailing list -- ssh at ietf.org To unsubscribe send an email to ssh-leave at ietf.org ----- End forwarded message -----

On 09/02/2019 10:44, Aki Tuomi via dovecot wrote: > For some reason mailman failed to "munge from" for senders with dmarc policy ;( > > It's now configured to always munge to avoid this again. I'd say, let Mailman throw all people off the list that have enabled DMARC checking without using exceptions for the lists they are on. It's a known fact that DMARC does not

Hi, This implementation looks fine, but there is no specification for using SM3 in the SSH protocol. Could I suggest that you start by talking to the IETF to get the standardisation process started? https://mailman3.ietf.org/mailman3/lists/ssh.ietf.org/ is a good mailing list to start at. There have been recent conversations in the IETF about how best to handle national cryptographic standards like SM3. -d On Tue, 6 Aug 2024, Tianjia Zhang wrote: > Add OSCCA SM3 secure hash algorithm (OSCCA GM/T 0004-201...

...ult or have internal mirror but at least people would be aware that distro itself is EOL and that they shouldn't expect to receive any update anymore > > # CentOS mailing-lists > Currently running on mailman2 stack, on top of CentOS 7 linux : there is WIP to port everything to up2date mailman3 stack, actually packaged for EPEL9. > We have successfully imported archives into mailman3 and same for lists config but let's start a different/separate thread to discuss changes (like renaming lists, see next coming thread) > > Kind Regards, > > -- > Fabian Arrotin > T...

...f needed" - munging all messages </div> <div> leads to a really bad "user experience". </div> <div></div> </blockquote> <div> It does not seem to work correctly. I'll review the settings when we manage to upgrade to mailman3 </div> <blockquote type="cite"> <div> Thanks. </div> <div></div> </blockquote> <div> Hope you understand . </div> <div> <br> </div> <div> Aki </div> <blockquote...

Hi, This is what I tried : Y , how enter an answer in the thread ?) virsh -c qemu+ssh://127.0.0.1:22/system hostname root@127.0.0.1's<mailto:root@127.0.0.1's> password: error: End of file while reading data: : Input/output error error: failed to connect to the hypervisor In another hand ,as we have few information to share , I was thinking to use a virtio channel to

Hi all, I suppose this has been asked before, but I wasn’t able to find a discussion on the subject. Is there a reason for not using a web based interface instead of a mailing list?. It seems to me that a using a private Forum would bring a lot of advantages. John

On Mon, Nov 18, 2019 at 2:49 PM Robinson, Paul via llvm-dev < llvm-dev at lists.llvm.org> wrote: > | mailing lists for longer-form discussions are unfamiliar, difficult, > and often intimidating for newcomers > > > > Um… what? While I know (via my own children) that folks nowadays use > multiple avenues of communication, it’s **really** hard to imagine email > as a

Add OSCCA SM3 secure hash algorithm (OSCCA GM/T 0004-2012 SM3). --- Makefile.in | 2 +- configure.ac | 2 +- digest-libc.c | 11 ++ digest-openssl.c | 1 + digest.h | 3 +- mac.c | 1 + sm3.c | 320 +++++++++++++++++++++++++++++++++++++++++++++++ sm3.h | 51 ++++++++ 8 files changed, 388 insertions(+), 3 deletions(-) create mode