similar to: Dovecots header files not optimized for external plugins

On 19 Nov 2017, at 0.40, Jan Engelhardt <jengelh at inai.de> wrote: > > > Making third-party plugins for Dovecot is really hard and frustrating. > Using dovecot 2.2.33.2 and the following sources, the compile errors keep > coming. The use of g++ is mandated as the underlying backend this plugin > will access only has a C++ interface. See compile instructions for example

Hi, this commit https://github.com/dovecot/core/commit/c9d76e2baf653fa5504d6849e5c1aae32eff3c53 added code which can not be compiled with uclibc-ng 1.0.26 using buildroot: make[3]: Entering directory '/home/bernd/buildroot/br4/output/build/dovecot-2.2.33.2/src/lib-test' /bin/bash ../../libtool --tag=CC --mode=compile

On Mon, Nov 13, 2017 at 20:07:00 +0100, Bernd Kuhls wrote: > Hi, > > this commit > https://github.com/dovecot/core/commit/c9d76e2baf653fa5504d6849e5c1aae32eff3c53 > > added code which can not be compiled with uclibc-ng 1.0.26 using buildroot: Hrm... ok. It'll be probably faster for you to try a test build instead of me setting up buildroot... What happens if in

Am Mon, 13 Nov 2017 15:40:14 -0500 schrieb Josef 'Jeff' Sipek: > What happens if in dovecot's byteorder.h you add this before line 30: > > #undef bswap_8 > #undef bswap_16 > #undef bswap_32 > #undef bswap_64 > > Hopefully that does it. Hi Jeff, adding these four lines fixes the build error, thanks! Regards, Bernd

On Wed, Dec 02, 2015 at 02:00:57PM +0100, Pino Toscano wrote: > - add a flag to request chroot for the process, which is done only as > very last (before chdir) operation before exec'ing the process in the > child: this avoids using CHROOT_IN & CHROOT_OUT around command* > invocations, and reduces the code spent in chroot mode > - add failure checks for dup2 and open

- add a flag to request chroot for the process, which is done only as very last (before chdir) operation before exec'ing the process in the child: this avoids using CHROOT_IN & CHROOT_OUT around command* invocations, and reduces the code spent in chroot mode - add failure checks for dup2 and open done in child, not proceeding to executing the process if they fail - open /dev/null

Hi , I have posted DTrace script to snoop tcp traffic and also provided a wrapper script for it to filter out unwanted traffic. http://blogs.sun.com/roller/comments/raviswam/Weblog/tcp_snoop_using_dtrace Please let me know if you have any feedback/comments on this. Thanks Ravi

Hi guys, Just tested yesterday's stable build, when including SQL into the build I am getting an error on like 86 of passdb-sql.c (passdb_result = PASSDB_RESULT_OK;) It rightly says passdb_result is undeclared. Commenting out this line fixes it and build appears to work fine after that. Regards Andrew -- Andrew Hutchings Linux Guru Netserve Consultants Ltd. http://www.domaincity.co.uk/

If we compare the "common" subdirectory between nbdkit @ 6b4178d0fdfe ("ci: Temporarily disable perl in MacOS", 2023-02-27) and libnbd @ d05cd8f384a7 ("Version 1.15.11.", 2023-02-28), we find differences. We can categorize these differences along two (orthogonal) axes: - Intentional or unintentional. Intentional differences are for example when one of the libnbd

On Thu, Nov 19, 2015 at 05:38:25PM +0100, Pino Toscano wrote: > When running commands in the mounted guest (using the "command" API, and > APIs based on it), provide the /dev/null from the appliance as open fd > for stdin. Commands usually assume stdin is open if they didn't close > it explicitly, so this should avoid crashes or misbehavings due to that. > --- >

Hi there, Other auth modules (eg passwd-file) allow a username_format to be specified, but not the PAM module. The use-case, is where I want a static userdb configuration which takes the domain into account but still want to use PAM for authentication, eg: userdb { driver = static args = uid=8 gid=12 home=/mnt/storage/mail/vhosts/%d/%n } passdb { driver = pam args = username_format=%n

Hi everyone, since some time I got problems with dovecot & mysql. I got the problem with version 2.0.x and upgraded to 2.1.7 to check if its gone. But its not :( The logs just tell me this: dovecot: auth: Error: auth worker: Aborted request: Worker process died unexpectedly If I change to a sqlite setup, everything works fine. Here are some informations. I hope someone can tell me whats

Hello list I want to implement override_username = %variable for the "shadow" driver, so that the following works: passdb { driver = shadow args = override_username=%Ln } by "%variable", I mean "Variables" at http://wiki.dovecot.org/Variables. I've hacked up a solution with strtok(3C), but that's a hack and a possible security hole, and I'd rather

Hello, attached patch (1.0-test29) adds LOGIN authentication mechanism. Tested with KMail and seems working. Please consider applying. Best regards. P.S. I also have NTLM authentication working and plan to submit it RSN. -- Andrey Panin | Linux and UNIX system administrator pazke at donpac.ru | PGP key: wwwkeys.pgp.net -------------- next part -------------- diff -urpNX /usr/share/dontdiff

Hello, Trying to get my machine building up-to-date, and a nightly going, i ran into an assertion during the build of llvm-gcc 4.2: $ make -j2 <snip!> /home/chandlerc/code/compilers/build/llvm-gcc/./gcc/xgcc -B/home/chandlerc/code/compilers/build/llvm-gcc/./gcc/ -B/home/chandlerc/code/compilers/install/llvm-gcc/x86_64-pc-linux-gnu/bin/

Hi Aki, > Aki Tuomi <aki.tuomi at open-xchange.com> hat am 30. M?rz 2020 16:23 geschrieben: > > Can you install dovecot-dbg to get debug symbols, open the core in gdb and run > > bt full > Full backtrace: :~# gdb /usr/lib/dovecot/auth core.juu GNU gdb (Debian 7.12-6) 7.12.0.20161007-git Copyright (C) 2016 Free Software Foundation, Inc. License GPLv3+: GNU GPL version

Hello, attached is an hg export on top of the current dovecot-2.2 branch, which adds support for a SCRAM-SHA-1 password scheme. Ideally I'd want doveadm pw's rounds flag to apply to this, but that's currently specific to the crypt password scheme, so I left it out for now. Regards, Florian Zeitz -------------- next part -------------- # HG changeset patch # User Florian Zeitz

Hi Chandler, This looks like a FE error, so you probably won't be able to get an LLVM bitcode file for us. You could help by whittling the test case down to something managable. First get a preprocessed file. Then I would suggest following the instructions on this page to reduce the testcase: http://gcc.gnu.org/wiki/A_guide_to_testcase_reduction That will help us a lot with the bug

Hello, I am building a loop pass following these instructions: http://llvm.org/docs/WritingAnLLVMPass.html Everything works fine, I did it many times for Function Passes, but in the runOnLoopmethod, whenever I call a method of the loop L passed as argument, for example L->begin(), I get the following error: opt: symbol lookup error: /home/giacomo/llvmcsfv/Debug+Asserts/lib/Acsl.so: >

Thanks, Also, every method inherited by LoopBase causes the same error, while Loop methods go smooth. On 9 May 2013 01:05, Andrew Trick <atrick at apple.com> wrote: > > On May 8, 2013, at 7:43 PM, Giacomo Tagliabue <giacomo.tag at gmail.com> > wrote: > > Hello, > I am building a loop pass following these instructions: >