similar to: managesieve-login and segfault

I am building dovecot-2.0-pigeonhole-0.2.1 (dovecot-2.0.5, but that does not matter) with dovecot-config in place (in /usr/lib64/dovecot) on a 64bit Linux (RHEL5): ./configure --with-dovecot=/usr/lib64/dovecot The libs needed for several executables in libexec such as /usr/libexec/dovecot/managesieve-login are not installed in /usr/lib64 but in /usr/lib64/dovecot. Therefore the executable

tonight dovecot 1.2beta4 crashed for the first time with an assertion failed. See attached log file. Around that time nobody was logged in into dovecot and there were no other mail deliveries going on. The mail in question should have been delivered to three recipients, one got the mail, the two others not. There is unfortunately no core dump file. I have attached the dovecot -n output as

I do have two questions related to the managesieve setup in dovecot 1) I did setup a global sieve filter, that is invoked if a user has no other sieve filter. If a user installs a sieve filter and activates it (PUTSCRIPT, SETACTIVE) then the sieve filter gets compiled (.sievec) and deliver does use it. If I want to deactivate the filter (SETACTIVE "") only the symlink (to the .sieve

In order to let users construct a sieve filter using a GUI I have taken websieve.pl from Alain Turbide (for use with Cyrus) and modified it to work with dovecot. In order to get it working quickly I have removed all the code I did not need (e.g. ldap support, password authentication) and coded Kerberos5 auth (via GSSAPI or SASL) in. I understand that this makes the work mostly useless to

Using dovecot 1.2beta (but earlier versions should behave similarly) we have a problem in conjunction with empty To: headers and the RT request tracker. RT sends mail out using Bcc: and no To: header at all. To make some mailers happy one can configure to send a dummy To: header, which we do. Our To header looks like: To: "AdminCc of rt Ticket #123456":; The message_address_parse

Hi Timo, we are currently running dovecot 2.1.10 using mdbox storage. Sometimes we get requests from users to restore accidentally deleted mails. If the mails got deleted before a backup was made, such mails could of course not be restored from backup. One option to help users in this respect would be to use the lazy expunge plugin. On the other hand I have seen, that the deleted mails stay

Hello, Thank you very much for quick response. I need only xapian-core. As I wrote on my case compilation with Visual Studio 2015 successful, just I have runtime errors, while the same code on LINUX runs fine. I'll try the hints from (https://trac.xapian.org/browser/git/xapian-core/INSTALL?rev=RELEASE/1.4#L54) and maybe to migrate my project to VS2017 and test it again. If I understand

Dear XAPIAN developers, I think your code is devoted also to be compiled on Windows with Microsoft compiler. I think so because 1. There are many #ifdef _MSC_VER like code 2. And if I remember correctly the xapian documentation, xapian has also C# bindings. I need the xapian library for Windows Microsoft compiler. I created visual studio 2015 project and included almost all source

Hello we are doing regular backups of the mdbox mail folders using dsync -u username backup mdbox:/somedir/BACKUPS/username (still with version 2.1.10, but 2.2.5 is in testing phase) We do observe that the directory size in the BACKUPS directory is growing with respect to the original mail folders. I believe this is due to deleted mails not being purged in the backup. We are doing regular

> Is there ? GUI for sieve. > > I don't have installed Squrielmail, but won't like to manage the > Rules per ssh

Hello, My first problem is compilation against Heimdal. It does not work because of the following: /products/source/heimdal/heimdal-0.5.1/i386_linux24/lib/roken/../../../lib/r oken/getprogname.c(.text+0xc): multiple definition of `get_progname' openbsd-compat//libopenbsd-compat.a(bsd-misc.o)(.text+0x0):/usr1/ahaupt/open ssh-3.6.1p1/openbsd-compat/bsd-misc.c: first defined here /usr/bin/ld:

http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz.sig http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz.sig Fixed lots of bugs in v1.2 related to shared mailboxes and virtual mailboxes. Keep on testing and sending bug reports and hopefully we'll get v1.2.0 release out

http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.14.tar.gz.sig http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz http://dovecot.org/releases/1.2/rc/dovecot-1.2.rc3.tar.gz.sig Fixed lots of bugs in v1.2 related to shared mailboxes and virtual mailboxes. Keep on testing and sending bug reports and hopefully we'll get v1.2.0 release out

Two of my users are reporting that their quota is not being recalculated ALTHOUGH they deleted lots and lots of mails. I'm using today's hg checkout of 1.2 beta 4 -- Ralf Hildebrandt Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.computerbeschimpfung.de Wen du nicht mit K?nnen beeindrucken kannst, den verwirre mit Schwachsinn! -------------- next

Hi all, storing e-mails (using postfix) via dovecot-lda fails and I assume this is related with a auth_socket configuration problem. But I am at a dead end, so perhaps anybody has got a hint for me: This is dovecot-2.0.8 on Solaris 10: 10-auth.conf and its include: ----------------------------- ... userdb { driver = static args = uid=104 gid=104 home=/some/path/%u } Relevant parts of

Hi all, I have a setup of some nodes running Dovecot 2.0.13 and Postfix 2.5.6 with storage in NFS and authentication happening with PAM. Poking around in the wiki, I tried out different possibilities but now I am stuck -- and are hoping for your (enlightening) comments and tips. My planned setup for IMAP and LMTP is like this: IMAP ==== 1. A loadbalancer directs new sessions to a

Dear all, I am trying to setup Dovecot with GSSAPI support. For testing purposes gssapi is the only method allowed for login. As I cannot login to my mailbox, I'vo got two questions about the following log entries: dovecot: Info: auth-worker(default): passwd-file /dovecot/store/db/test-userdb: Read 3 users dovecot: Info: auth(default): new auth connection: pid=3915 dovecot: Info:

Hello, I am seeing sporadic duplicate read requests from lpxelinux.0 (6.03 from kernel.org), which results in a failed PXE boot. This happens only sporadic, but happens often enough to be annoying. The TFTP server serving lpxelinux.0 is running CentOS 7.6 with all updates applied. The client machine initiates the PXE boot, receives the lpxelinux.0 binary, downloads ldlinux.c32 and proceeds to

Hello Dovecot users, Because there was a crash bug in the ManageSieve v0.10.4 login daemon, I made a new release of the ManageSieve service for Dovecot v1.1. This release includes two other small fixes as well. Changelog v0.10.5: - Fixed a segfault bug in the authentication time-out. Bug report and trace provided by Wolfgang Friebel. - Fixed maximum permissions for uploaded

Hello Dovecot users, Because there was a crash bug in the ManageSieve v0.10.4 login daemon, I made a new release of the ManageSieve service for Dovecot v1.1. This release includes two other small fixes as well. Changelog v0.10.5: - Fixed a segfault bug in the authentication time-out. Bug report and trace provided by Wolfgang Friebel. - Fixed maximum permissions for uploaded