similar to: Strange Login / Timeout Sessions

Hi, recently I checked our mailserver for some more tuning and optimizing and noticed, that currently I do have 487 imap-login processes and I'm asking myself if that's o.k. We do have about 1.000 user in total and not everybody is currently logged in. May be this is o.k. but if not, what might I check? We run the dovecot package provided by redhat EL 5.8 dovecot-1.0.7-7.el5_7.1

CentOS Errata and Security Advisory 2012:0060 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0060.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 2214b833b3e80773b1952f0f775b6636a61204978d1be70653d5c138a0d81fab openssl-0.9.8e-20.el5_7.1.i386.rpm

Just got this message after an autoupdate on my 5.x system.. should I be worried? Hi, This is the automatic update system on mail.<xxx>.com. There was a problem updating the system. The following error message was reported: ["[('file /usr/share/man/man1/ca.1ssl.gz from install of openssl-0.9.8e-20.el5_7.1.x86_64 conflicts with file from package openssl-0.9.8e-20.el5.i686',

I had a use lose 20 folders on their mail account. I was able to pull them back from a restore and dumped them all back on the server in her Maildir. The problem is she doesn't see them on her Thunderbird or Outlook client. I checked to make sure I put them back into the correct directory and I did as well as verify permissions aren't weird. I then noticed a file called

Am 2019-08-30 10:52, schrieb Gary Stainburn: > On Thursday 29 August 2019 18:10:19 Alexander Dalloz wrote: >> > 2019-08-29 17:23:18,117 exception: [Errno 14] curl#60 - "Peer's >> > Certificate issuer is not recognized." >> > 2019-08-29 17:23:18,117 retrycode (14) not in list [-1, 2, 4, 5, 6, >> > 7], re-raising >> >> [ ... ]

On Friday 30 August 2019 12:03:26 Alexander Dalloz wrote: > You are welcome Gary. And I am curious about what the cause of your repo > troubles is. I have looked back over what I have done, and cannot see what has caused the problem to occurr. I do not see anywhere where it could have been from any action that I have taken, including deleting the contents of the yum cache. > That's

Am 2019-08-29 18:26, schrieb Gary Stainburn: > On Thursday 29 August 2019 16:47:11 Alexander Dalloz wrote: >> rpm -Vv nss > > [root at stan2 ~]# rpm -Vv nss > ......... /etc/pki/nss-legacy > ......... c /etc/pki/nss-legacy/nss-rhel7.config > ......... /etc/pki/nssdb > ......... c /etc/pki/nssdb/cert8.db > ......... c /etc/pki/nssdb/cert9.db > ......... c

On 2019-06-19 04:01, Nicolas Kovacs wrote: > Hi, > > I have a working installation of Postfix and Dovecot that works nicely. > I've added SpamAssassin, which does a good job of flagging spam. Now I > wanted to add greylisting to my server. > > Here's what I did. > > $ sudo yum install postgrey > > Increase the greylisting delay. > > #

On 19/06/2019 09:01, Nicolas Kovacs wrote: > Hi, > > I have a working installation of Postfix and Dovecot that works nicely. > I've added SpamAssassin, which does a good job of flagging spam. Now I > wanted to add greylisting to my server. > > Here's what I did. > > $ sudo yum install postgrey > > Increase the greylisting delay. > > #

Hi, I have a working installation of Postfix and Dovecot that works nicely. I've added SpamAssassin, which does a good job of flagging spam. Now I wanted to add greylisting to my server. Here's what I did. $ sudo yum install postgrey Increase the greylisting delay. # /etc/sysconfig/postgrey POSTGREY_OPTS="--delay=300" Edit /etc/postfix/main.cf accordingly.

> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of Gabriele Pohl > Sent: Friday, April 22, 2016 11:53 AM > To: centos at centos.org > Subject: [CentOS] output of "ls" (was: Re: Postgrey on CentOS 6) > > On Sat, 23 Apr 2016 02:23:28 +1200 > Peter <peter at pajamian.dhs.org> wrote: >

On Sat, 23 Apr 2016 02:23:28 +1200 Peter <peter at pajamian.dhs.org> wrote: > On 23/04/16 02:13, Gabriele Pohl wrote: > > I administer a postfix mail server on CentOS 6. > > Now I want to setup another with similar configuration. > > > > But the postgrey package is no longer available in Epel > > for this CentOS release as I have seen now: > >

Hi Guys, Are you interested in a brief guide on how to set up postgrey (anti-spam greylisting) with postfix? I set it up today and it took me a while to get it working as the config is slightly different from that on many of the googled guides (many are debian/ubuntu based). The darn config file lives in /etc/sysconfig on RH/CentOS rather than /etc/default as mentioned in all the guides I

Sure, and thanks for trying to help! These are the two correct answers when SNI is included. The certificates are fully chained. Both certificates carry the same subject mail.cs.sbg.ac.at but differ in Subject Alternative Name (SAN). X509v3 Subject Alternative Name:? ? DNS:mail.cs.sbg.ac.at, DNS:smtp.cs.sbg.ac.at, DNS:imap.cs.sbg.ac.at, DNS:pop.cs.sbg.ac.at X509v3 Subject Alternative Name:? ?

Hi folks, I have installed postgrey from the rpmforge repo, but it does not work well with postfix from CentOS 5.2: I always get the error: warning: connect to postgrey/socket: Permission denied problem talking to server postgrey/socket: Permission denied But the permissions on the socket seem okay (postfix could write to it): srw-rw-rw- 1 postgrey postgrey 0 4. Okt 14:48 socket I

I installed postgrey from rpmforge and wanted to use sysconfig to change options instead of overwriting the init file. However, I get a weird warning from postgrey. I'm not sure if this is a postgrey quirk or I use sysconfig the wrong way. /etc/sysconfig/postgrey: OPTIONS="--unix=/var/spool/postfix/postgrey/socket --delay=660" /etc/rc.d/init.d/postgrey:

Hello, the RPM ca-certificates-2018.2.22-65.1.el6.noarch has a big problem ... many certificates were removed - my proxy uses this as source and isn't able to validate correct any more - most sites show this: /[No Error] (TLS code: X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN) /Self-signed SSL Certificate in chain: /C=SE/O=AddTrust AB/OU=AddTrust External TTP Network/CN=AddTrust External CA Root

On 07/04/2018 08:54 AM, Walter H. wrote: > Hello, > > the RPM > > ca-certificates-2018.2.22-65.1.el6.noarch > > has a big problem ... > many certificates were removed - my proxy uses this as source and isn't > able to validate correct any more - > most sites show this: > > /[No Error] (TLS code: X509_V_ERR_SELF_SIGNED_CERT_IN_CHAIN) > > /Self-signed

On 04.07.2018 18:37, Alice Wonder wrote: > On 07/04/2018 08:54 AM, Walter H. wrote: >> Hello, >> >> the RPM >> >> ca-certificates-2018.2.22-65.1.el6.noarch >> >> has a big problem ... >> many certificates were removed - my proxy uses this as source and isn't >> able to validate correct any more - >> most sites show this: >>

Am 2019-08-30 17:04, schrieb Gordon Messmer: > On 8/30/19 5:52 AM, Gary Stainburn wrote: >> Incidentally, the*good* server that I was referencing my broken >> server against has decided to start giving the curl certificate errors >> in the same way that the broken one did. Very strange. I ran > > > It's possible that the error is unrelated to the