similar to: Updated Dovecot 2.3.0 now getting 2 strange log errors

Op 12/30/2017 om 6:47 AM schreef tony: > On 2017-12-29 18:35, tony wrote: >> I did some more digging around and found this is reproducible on >> multiple hosts running the same version of Dovecot/Pigeonhole/Postfix. >> The problem resurfaces on any host to an account with enabled >> Vacation/OOO response. The Vacation/OOO reply filter was created in >>

On 2017-12-29 18:35, tony wrote: > I did some more digging around and found this is reproducible on > multiple hosts running the same version of Dovecot/Pigeonhole/Postfix. > The problem resurfaces on any host to an account with enabled > Vacation/OOO response. The Vacation/OOO reply filter was created in > Roundcubemail, but has been fine for years. One thing to note is in >

On 2018-01-01 17:26, Peter wrote: > On 02/01/18 14:07, Stephan Bosch wrote: >>> I can see 21:21:38 is when the below errors showed up with the above >>> 21:21:38 timestamps: >>> >>> Dec 29 21:21:38 >>> lmtp(recipient at domain.net)<17187><UA2fMEQiR1ojQwAAUXb6+w>: Error: >>> program `/usr/sbin/sendmail' was forcibly

Hello, Today I started noticing a very odd Dovecot error in the mail logs across 2 replicated Dovecot hosts via dsync. I have searched the Dovecot archives, Google, back tracked, downgraded Dovecot to earlier versions from earlier this year and ruled everything out I could think of to no avail. There really are not any helpful reports with what I am specifically seeing. The strange thing is only

Hello, Absolutely. Here is the output of doveconf -n: # doveconf -n # 2.2.31 (65cde28): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.19 (e5c7051) # OS: Linux 4.9.36-x86_64-linodexx x86_64 Arch Linux auth_mechanisms = plain login base_dir = /var/run/dovecot/ dict { expire = ldap:/etc/dovecot/dovecot-ldap.conf.ext quota = ldap:/etc/dovecot/dovecot-ldap.conf.ext } doveadm_password = #

On 2018-01-02 17:21, tony wrote: > On 2018-01-02 16:37, tony wrote: >> On 2018-01-01 17:26, Peter wrote: >>> On 02/01/18 14:07, Stephan Bosch wrote: >>>>> I can see 21:21:38 is when the below errors showed up with the >>>>> above >>>>> 21:21:38 timestamps: >>>>> >>>>> Dec 29 21:21:38 >>>>>

On 02/01/18 14:07, Stephan Bosch wrote: >> I can see 21:21:38 is when the below errors showed up with the above >> 21:21:38 timestamps: >> >> Dec 29 21:21:38 >> lmtp(recipient at domain.net)<17187><UA2fMEQiR1ojQwAAUXb6+w>: Error: >> program `/usr/sbin/sendmail' was forcibly terminated with signal 15 >> Dec 29 21:21:38 >>

On 2018-01-02 16:37, tony wrote: > On 2018-01-01 17:26, Peter wrote: >> On 02/01/18 14:07, Stephan Bosch wrote: >>>> I can see 21:21:38 is when the below errors showed up with the above >>>> 21:21:38 timestamps: >>>> >>>> Dec 29 21:21:38 >>>> lmtp(recipient at domain.net)<17187><UA2fMEQiR1ojQwAAUXb6+w>: Error:

Hey Edgar, Thanks for catching that! Missed it earlier! Got it changed but I?m still having the same error updated postconf -n: [ec2-user at ip-172-31-24-2 conf.d]$ postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level =

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.

Hi, 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: https://admin.fedoraproject.org/pkgdb/package/rpms/postgrey/ 1. Will I have to make an upgrade of the existing mail server to get security patches again or is it not critical to use

hi, one customer told us, that he has performance problem in his Thunderbird 3.1.9, while open his sent folder, which has round about 4000 mails in it, and 20k in his Inbox. For example TB, tries to sync the sent-folder list (over SSL) from the sent folder for now over 15min. In the log, I can't see any strange things, so for me, Dovecot works ok. Maybe, I should use better cache options?

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: > >

I'm experimenting with Wine under Kubuntu Hardy Heron, on a former Vista laptop (boy, does it run noticeably faster on Linux). The deal is that my son wants to move to Linux on his desktop, but still have access to particular games that he plays. The laptop is the testbed. Before trying to install any of the games, I tried out three applications that I find useful, Orbitron, Country Codes and

Le 19/06/2019 ? 22:05, Phil Perry a ?crit?: > Try following the Postgrey guide on the Wiki: > > https://wiki.centos.org/HowTos/postgrey#head-314ceecc5ece27e0f0a4bf1abcd8ee9356cd1a5e > > > Works for me (allowing for the switch to systemd) I've followed this document, and still no joy. Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730

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

Hello all, I am looking for the correct way to add postgrey to my system but whitelist everything except for com, org, and net domains. Most of my spam is from .info domains. There seems to be no way to only go after certain domains, instead postgrey wants to go after everything except what you whitelist. So my idea was to whitelist .com, .net, .org, .gov, and a few others while greylisting

Hi, We have implemented postgrey (postgrey-1.24, compiled from source package) on a centos 4.3 server. It works except for the whitelistings, in file postgrey_whitelist_clients, no matter what domain we enter, their incoming mails gets greylisted. I have posted this question to postgrey list but have not received anything yet. I works OK on a centos 4.1 server. Has anyone experienced similar

Package: logcheck-database Version: 1.2.35 Severity: minor logcheck-database contain postgrey ignore file, but postgrey first attempt is listed in logcheck report $ dpkg -l postgrey ii postgrey 1.18-1 -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.4.29-C3EZRA Locale: LANG=it_IT,

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