similar to: freebsd log process problem

hi, anyone test freebsd as guest on kvm with virtio drivers? any expirience?

I am trying to add a signature to all messages and it should be possible via vnd.dovecot.filter, the problem is that any script I try to filter through just hangs. I am running on FreeBSD 11.2 and I tried with dovecot 2.2.32 & pigeonhole 0.4.19 and with dovecot 2.3.2 && pigeonhole 0.5.2. In both cases, the output from dovecot is the same: Feb 19 18:24:22 mx13 dovecot: lda(user1):

after morning update of librsvg2 Feb 04 09:39:15 Updated: librsvg2-2.26.0-6.el6_5.2.x86_64 nautilus crashed with nautilus[3419]: segfault at 21 ip 00007f68b2d2733c sp 00007fffe2ce04f0 error 4 in librsvg-2.so.2.26.0[7f68b2d01000+37000] temporary solution yum downgrade librsvg2 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type:

Hi. Does someone make update for `Multiple IP(or Host) listen in dovecot.conf'? I made trivial patch so. But this patch doesn't solve `Support listening in multiple sockets' in TODO. It appends only the capability as multiple listen in dovecot.conf. So, `login_processes_count' becomes ambiguous. In CASE1, login_processes_count = 2, forked imap-login processes are 8. -- samples

I'd like to modify pthread library ( e.g. manipulating some functions ) in glibc, so I want to compile and install modified glibc. However, I failed to compile glibc and need some help. How can I fix the problem? Here is the process that I've tried. 1. download glibc-2.3.4.tar.tar from http://ftp.gnu.org/gnu/glibc/ 2. unzip glibc-2.3.4.tar.tar 3. make build-folder [root at localhost /]#

The following patch is need to correctly align the default_settings structure with gcc 2.95, which doesn't recognise C99 style struct initializers. --- src/master/master-settings.c~ 2006-04-25 04:00:07.000000000 +0200 +++ src/master/master-settings.c 2006-05-18 11:14:08.949376000 +0200 @@ -367,6 +367,7 @@ /* .. */ MEMBER(login_uid) 0, + MEMBER(imap_generated_capability) NULL,

> On 21/03/2023 00:26 EET Benoit Branciard <benoit.branciard at univ-paris1.fr> wrote: > > > Hello, > > I have some trouble using "doveadm altmove -r". > > Regular "doveadm altmove" is OK, selected mails were moved to alternate > storage as expected. But I can't manage to get them back to original > location, "doveadm altmove

If I can squeeze a message between the discussions on security (:-)) I have been trying to compile a kernel on an x86_64 box under CentOS4.1 and now 4.2. The problem is that neither make xconfig or make gconfig work: make gconfig * * Unable to find the GTK+ installation. Please make sure that * the GTK+ 2.0 development package is correctly installed... * You need gtk+-2.0, glib-2.0 and

I'm running Dovecot 2.3.4 with Single Instance Storage (SIS) and zlib and I am frequently seeing errors where files are missing in the attachments directory even though the zipped file in the hash directory is actually there.? This appears not to have been an issue in Dovecot 2.3.1 Requested output of the server below. The error looks like this in the log Dec 18 08:58:58 dovecot01

Hi everyone, I need some insight into a problem I just started having. I''m running ruby 1.8.6 on an ubuntu box with the following gems installed: $ sudo gem list --local *** LOCAL GEMS *** actionmailer (2.3.5, 2.3.4, 2.3.2, 2.2.2) actionpack (2.3.5, 2.3.4, 2.3.2, 2.2.2) activerecord (2.3.5, 2.3.4, 2.3.2, 2.2.2) activeresource (2.3.5, 2.3.4, 2.3.2, 2.2.2) activesupport (2.3.5, 2.3.4,

After upgrading our application from Rails 2.3.2 to 2.3.4 all our error messages appeared as "{{attribute}} {{message}}" (literally). Since we noticed this problem short before a release and hadn''t enough time to look deeper into it we fixed it by using the "old" full_messages method that was present in 2.3.2 So today I started reading up on what exactly has changed,

==> /var/log/dovecot/dovecot.log <== Jun 9 09:58:26 spectre dovecot: lmtp: Fatal: master: service(lmtp): child 12635 killed with signal 11 (core dumped) This is another segmentation fault introduced in the current code. Please also look into fixing the other Core Dump I reported: http://www.dovecot.org/list/dovecot/2013-June/090795.html (gdb) bt full #0 0x00007f305d3df646 in

Hello, I have some trouble using "doveadm altmove -r". Regular "doveadm altmove" is OK, selected mails were moved to alternate storage as expected. But I can't manage to get them back to original location, "doveadm altmove -r" has no effect. We are using Dovecot 2.3.4 (Debian Buster package). mail_location =

On Wed, Mar 20, 2019 at 2:13 PM Mark Moseley <moseleymark at gmail.com> wrote: > Just hoping to get some dev eyes on this. I'm incredibly reluctant to > throw the word 'bug' around > (since 99 times out of 100, it's not -- it's almost always the config), > but I can't think of any way > that this could be a config issue, esp when the pre-2.2.34 version

I briefly got some mails delivered, but not anymore. Attached are dovecot-info.log, dovecot-debug.log, dovecot.log, maillog, /etc/mail/passwd smtpd.conf, vaddr, vusers, vdomains Thanks for any help. Chris Bennett -------------- next part -------------- May 15 12:54:25 master: Error: service(config): pipe() failed: Too many open files May 15 12:54:25 master: Error: service(auth): pipe() failed:

Hi all, Wishing you and your families a Happy New Year 2019. I am currently struggling with an odd sieve issue after upgrading dovecot from 2.2.32 to the latest 2.3.4 version. OS is Ubuntu 18.04. For one of our users I have a sieve rule in place which should copy (keep + fileinto) incoming mails from the INBOX to a public namespace folder. Unfortunately this does not work anymore. In the sieve

Having had a week with the system I'm now inclined to believe that the issues I've seen are not necessarily related to SIS and zlib but may be due to replication instead. After experiencing these issues and looking at historical mailing list posts I wrote a basic script (as was suggested as a possible diagnostic approach for SIS before SIS was even implemented!) which pulled all the

Hi, Your problem might be similar to mine a long time ago. IMO behavior of "doveadm altmove -r" command with mdbox format is different to sdbox format: - With sdbox format, when you move back a message to primary storage (aka default storage), only the message and the file containing it are affected. There is nothing impacted. - With mdbox format, a file in storage contains

Bueno. I don't even remember well. Wasn't that issue about mysql-8.0.12 to 8.0.13?? On Tue, 5 Feb 2019 at 23:46, Larry Rosenman <larryrtx at gmail.com> wrote: > 2.3.4 had the same compile issues.... > > > On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington <odhiambo at gmail.com> > wrote: > >> Noted. >> >> I will wait for dovecot-2.3.4.2

Op 11-1-2019 om 10:53 schreef Marc Weustink: > Hi all, > > Andrzej A. Filip wrote: >> Timo Sirainen <tss at iki.fi> wrote: >>> On 9 Jul 2018, at 16.49, Andrzej A. Filip <andrzej.filip at gmail.com> >>> wrote: >>>> >>>> Is it intended behavior? >>> >>> No. >>> >>>> It seems to be caused by