similar to: CESA-2019:3872 Important CentOS 7 kernel Security Update

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

I have managed to find out what happened in the yum update and it turns out it was a mess. It looks like the server ran out of memory in the middle and things then started to fail. Any advice on how to recover from this would be greatly appreciated The log below shows: [root at vps2 ~]# yum history info 22 Loaded plugins: fastestmirror, langpacks Repository mariadb is listed more than once in

> On 1/22/20 3:57 PM, Gary Stainburn wrote: >> I have managed to find out what happened in the yum update and it turns >> out it was a mess. It looks like the server ran out of memory in the >> middle and things then started to fail. Any advice on how to recover >> from this would be greatly appreciated >> >> The log below shows: >> >> [root at

On 1/22/20 3:57 PM, Gary Stainburn wrote: > I have managed to find out what happened in the yum update and it turns out it was a mess. It looks like the server ran out of memory in the middle and things then started to fail. Any advice on how to recover from this would be greatly appreciated > > The log below shows: > > [root at vps2 ~]# yum history info 22 > Loaded plugins:

Am 03.12.19 um 12:32 schrieb J. Echter via dovecot: > Hi, > > i've seen a strange behaviour in our system (centos 7, dovecot 2.2.36 > (1f10bfa63) today. > > We got a mail and it got delivered. > > Dec? 3 07:56:25 mail postfix/lmtp[4013]: 915B0CEF4C2: to=<user at domain>, > relay=mail[private/dovecot-lmtp], delay=1.5, delays=1.3/0.03/0.02/0.19, > dsn=2.0.0,

Hi, i've seen a strange behaviour in our system (centos 7, dovecot 2.2.36 (1f10bfa63) today. We got a mail and it got delivered. Dec? 3 07:56:25 mail postfix/lmtp[4013]: 915B0CEF4C2: to=<user at domain>, relay=mail[private/dovecot-lmtp], delay=1.5, delays=1.3/0.03/0.02/0.19, dsn=2.0.0, status=sent (250 2.0.0 <user at domain> AOhCNBgH5l2vDwAAtnFApQ:2 Saved) Dec? 3 07:56:25 mail

Hi, i did but it seems to contain garbage to me. here's the .in file: 1575450806.299222 2 COMPRESS DEFLATE 1575450806.300114 2V?tQ?P?K?MURP 1575450806.300114 ?(?KI-J?,J^A??R??3???,3^K=#=#%M^.^@^@^@^@??2Q(N?IM.QP??s??P??^B^@^@^@??2U^H^E^Z??Z???`h???????^^^LT 1575450806.304341 ^@^@^@??2^C^Z????^E^@^@^@??r??^C?^@^@^@^@??2W???/??^B^@^@^@???@Rnafibi??^G^@^@^@??d??^N?

Hi, please record IMAP rawlog from the client session to see what the client requests and what dovecot responds. https://wiki2.dovecot.org/Debugging/Rawlog <https://wiki2.dovecot.org/Debugging/Rawlog> Sami > On 4 Dec 2019, at 10.44, J. Echter via dovecot <dovecot at dovecot.org> wrote: > > > Am 03.12.19 um 12:32 schrieb J. Echter via dovecot: >> Hi, >>

Hi, did not notice that you have imap_zlib enabled for protocol imap, can you disable that temporarily and re-record the rawlog. Sami > On 4 Dec 2019, at 11.22, J. Echter via dovecot <dovecot at dovecot.org> wrote: > > Hi, > > i did but it seems to contain garbage to me. > > here's the .in file: > > 1575450806.299222 2 COMPRESS DEFLATE >

Before declaring it not ready for prime time, did you try setting tls_ca_cert_file = /etc/ssl/certs/ca-certificates.crt In the oauth2 configuration file as documented in https://doc.dovecot.org/configuration_manual/authentication/oauth2 ? Aki > On 05/12/2019 21:58 mizuki via dovecot <dovecot at dovecot.org> wrote: > > > Hi all, > > We'd like to enable OAuth with

I have a VPS running C7. I ran a 'yum update' which included a kernel update. The yum update wasn't a total success because mariadb updates failed. However everything else appeared to work. However, when I rebooted the server it did not restart. I have managed to get the ISP's support desk to boot the server by selecting the previous kernel, and I now have access to my box again.

Hi all, We'd like to enable OAuth with Keycloak in Dovecot, after enabling 'OAUTHBEARER XOAUTH2' in Dovecot based on online document, I can confirm Dovecot is ready for OAuth using openssl command, however when the auth request comes in, it failed in establishing a SSL connection with Keycloak server on port 443, shown as following in debug logs. I can confirming using commands

I changed some of the tls options following the document, now config is following: tokeninfo_url = https://keycloak.com/auth/realms/mail/protocol/openid-connect/token introspection_url = https://dovecot:7598e21b-ec34-481f-80d0-059bddae0923 at keycloak.com/auth/realms/demo/protocol/openid-connect/token/introspect introspection_mode = post debug = yes rawlog_dir = /tmp/oauth2 #force_introspection