similar to: failed dovecot 1.2rc2 build Solaris 8, gcc 2.95.3

Heya, I am expiriencing compiling issues on Solaris 8 and Solaris 10 boxes with dovecot 1.2.6. On Solaris 8 the compiler is gcc 64bit 3.2.2, on Solaris 10 gcc 3.4.3. On both systems the compiling fails with: /bin/bash ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2

I'm having issues getting Dovecot 2.0.0 to compile - I get the following error: cc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-settings -I../../src/lib-master -DPKG_RUNDIR=\""/usr/local/var/run/dovecot"\" -DPKG_LIBEXECDIR=\""/usr/local/libexec/dovecot"\"

Heya, We are expiriencing issues with dovecot 2.1.1 on Linux with weird filenames in home directory of username. We are using mbox IMAP folders, with no special changes (mail_location = mbox:~/:INBOX=%h/.mailbox). Mar 6 13:37:17 machine dovecot: imap(username): Panic: file mail-storage.c: line 628 (mailbox_alloc): assertion failed: (uni_utf8_str_is_valid(vname)) Mar 6 13:37:17 machine dovecot:

Heya, we are seeing some strange issues with IMAP ID command using latest Roundcube builds on dovecot 2.2.10 responding "Input buffer full, aborting". Roundcube webmail connects to IMAP server and issues ID command first with some long arguments to ID command, however shorter than 1024 octets, which are specified in RFC2971 for ID IMAP extension. The situation is easily

Heya, we have two IMAP (UW-imap and dovecot) servers accessing the same mbox files for our users (don't ask why) and sometimes the UW-imap corrupts the mbox file. The mbox looks just like normal mbox except it does not have the proper 'From ' beginning of the file (usually there are some random tidbits in the begining of the file, which can be easily stripped to recover the working

Heya, We are in the process of migrating from qpopper to dovecot as POP3 server (and IMAP as well) and we hit the UIDL issue with dovecot. Qpopper uses its own algorithm to create UIDL values and if you set it up to write them down in the mbox file as X-UIDL, then dovecot can use them (pop_uidl_reuse = yes). But if you don't use that feature from qpopper, than X-UIDLs are missing and there

Hello, I've searched the documentation for IMAP/POP3 server with proxy feature, but wiki says that this is not fully implemented yet, but wiki page hasnt been updated for a while. So is there any change since then? Because we are looking for a solution to replace the perdition POP3/IMAP proxy in front of the current UW-IMAP servers and we would really appreciate this feature, since the

Hello, I am trying to migrate existing UW-IMAP installation to dovecot 1.1.14 and I am having troubles with namespaces. As you know UW-IMAP allows full system access to home directory of a user and you can set up dovecot to do that as well, but I would like to use namespaces. If I set my namespaces like this: namespace private { separator = / prefix = inbox = yes location =

Hey everyone, I am trying to migrate old UW-IMAP setup to dovecot 1.2.2 using namespaces as recommended for UW-IMAP backwards compatibility: http://wiki.dovecot.org/Namespaces I am trying to use these settings: mail_location = mbox:~/:INBOX=~/.mailbox # default namespace namespace private { separator = / prefix = inbox = yes } # for backwards compatibility: namespace private {

p/t_strdup_until wasn't returning a terminated string: Index: src/lib/strfuncs.c =================================================================== RCS file: /home/cvs/dovecot/src/lib/strfuncs.c,v retrieving revision 1.41 diff -u -p -r1.41 strfuncs.c --- src/lib/strfuncs.c 18 Jul 2004 01:44:59 -0000 1.41 +++ src/lib/strfuncs.c 31 Jul 2004 08:43:35 -0000 @@ -154,6 +154,7 @@ char

I think I stumbled upon a bug in the i_snprintf() function. In the case of vnsprintf() being available, it depends on vnsprintf() returning -1 when the string was longer than the passed-in limit (or it won't terminate the string.). But this isn't the C99-standardized behaviour, and newer glibc's don't do that anymore either, so you can end up with a non-terminated string. This

i saw two crashes in my syslog with dovecot, and google did not report any known problems. i have no problems using dovecot, thus bugreport is just for information. following information: ubuntu gutsy gibbon server amd64 ext3 outlook 2003 & 2007, just retrieving mails. mails have been migrated via imapsync 2 days before to this server. dovecot is imap-server and LDA. has been seen with

Hi, I have configured a public namespace ("#Shared"). Since dovecot 1.2rc2 (1.1.11 worked fine) I get a segfault, if I try to access a folder under this namespace when quota plugin is enabled. When the quota plugin is disabled, accessing those folders works. $ dovecot -n # 1.2.rc2: /opt/dovecot/etc/dovecot.conf # OS: Linux 2.6.26-1-686 i686 Debian 5.0 base_dir: /var/run/dovecot

Hello, alsa-plugins currently includes speex/speex_types.h, but that doesn't work with speexdsp versions >= 1.2rc2, since speex_types.h has been replaced with speexdsp_types.h. I made a patch for alsa-plugins, so that it includes speexdsp_types.h instead. I also bumped the speexdsp version check from "1.2" to "1.2rc2" in configure.ac, since speexdsp_types.h didn't

dovecot-2.0-piegonhole commit cac6acdc4d0e: Crash when USER is NULL. Backtrace is below. Perhaps, we should check for NULL and bail out early? Eray [...] (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. t_strcut (str=0x0, cutchar=64 '@') at strfuncs.c:277 277 for (p = str; *p != '\0'; p++) { (gdb) bt full #0 t_strcut (str=0x0,

Hello, since few days there are problems with the userdb lookup. The problem occur if the recipient user is unknown (here test at xtlv.cn) doveconf -n # 2.2.6 (f89e645cba90): /etc/dovecot/dovecot.conf # OS: Linux 3.2.45.stk32 i686 Debian jessie/sid ext3 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = digest-md5 cram-md5 auth_username_translation = %Lu auth_verbose = yes

Hi, I have to build dovecot-2.1.10 for SuSE SLES9. /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -no-undefined -Wl,--as-needed -o test-lib test_lib-test-lib.o test_lib-test-array.o test_lib-test-aqueue.o test_lib-test-base64.o

On 09/10/2016 21:48, Michael Felt wrote: > I finally decided it was really time to stop being lazy and really > move away from gmail. After I have a server in my basement using > power, etc. > > So I turned on the imap provided - and did not quite cry - it will > have to do for now, but imap2 is wanting. Next chapter in packaging. a) I have 'patched' several files to

Hi, I had successfully set up dovecot-1.0-test62 + ldap pass/user db, but now I'm encoutering a SIGSEV problem with a similar set up of a brand new dovecot-1.0-test65 installation. The auth process is killed by a SIGSEV as reported in the error log file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the

On 07/10/2019 10:17, Demonhost via dovecot wrote: > Hi Stephan, > > Here it is: > We still can't reproduce it here. First of all, did you update Pigeonhole along with Dovecot? This kind of weirdness can happen when Pigeonhole was compiled against a different version of Dovecot. You could compile Pigeonhole manually as well to make sure, which also gives you the opportunity to