similar to: dovecot-2.0.alpha2 doesn't compile on Mac OS X

dovecot-2.0.5 autoreconf is failing with: [1] $ autoreconf -f -i [...] src/plugins/acl/Makefile.am:11: `module_LTLIBRARIES' is used but `moduledir' is undefined [...] autoreconf-2.65: automake failed with exit status: 1 Also, $ ./configure --help | grep module --with-nss Build with NSS module support (auto) In other words, no moduledir output in configure --help. Looks

Hi, Running doveadm on Alpine Linux will show various underlinking errors: /usr/bin/doveadm: symbol 'acl_user_module': can't resolve symbol in lib '/usr/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so'. /usr/bin/doveadm: symbol 'acl_identifier_parse': can't resolve symbol in lib '/usr/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so'. ... (complete list is

The attached patch is an updated version of my quota-rquotad patch for the quota plugin. Like quota-fs, it only does quota reporting, not enforcing or changing. It also only works on FreeBSD, and possibly other *BSD's. It lacks any and all configure-time tests to see if RPC is even supported, and hardcodes the (Free)BSD way of getting at the NFS server of an NFS mount. I'm mostly mailing

Hi, I just took a look into the dovecot 2.1 sources and just saw a possible issue in array.h. This code snippet as an example: #static inline void * #array_get_modifiable_i(struct array *array, unsigned int *count_r) #{ # *count_r = array->buffer->used / array->element_size; # return buffer_get_modifiable_data(array->buffer, NULL); #} array->buffer->used and

1. My earlier patch to fix a typo in array.h was not good enough. Here's one that not only compiles, but also doesn't crash: --- dovecot-2.0.alpha2/src/lib/array.h 2009-10-08 10:04:35.000000000 -0500 +++ dovecot/src/lib/array.h 2009-10-29 20:47:47.000000000 -0500 @@ -72,8 +72,7 @@ (elem)++) # define array_foreach_modifiable(array, elem) \ for (elem =

The following case will make the incompat/compat flag of the super block be recovered. Task1 |Task2 flags = btrfs_super_incompat_flags(); | |flags = btrfs_super_incompat_flags(); flags |= new_flag1; | |flags |= new_flag2; btrfs_set_super_incompat_flags(flags); | |btrfs_set_super_incompat_flags(flags); the new_flag1 is recovered. In order to avoid this problem, we

Timo, I saw a couple of these cores over the weekend. The syslog says: May 21 19:04:48 emerald dovecot: [ID 107833 mail.error] IMAP(user): Corrupted index cache file /home/students/s/user/.imap/sent-mail-apr-2004/dovecot.index.cache: indexid changed With a resulting core file from imap at this time. I also discovered a remaining lock file on the person's imap file: -rw------- 1 user

Hi, As I use btrfs as root FS, I wanted fstype to be able to recognize it. The following patch add support for this FS. Regards, benjamin Signed-off-by: Benjamin Cama <benoar at free.fr> --- diff --git a/usr/kinit/fstype/btrfs_fs.h b/usr/kinit/fstype/btrfs_fs.h new file mode 100644 index 0000000..e1f933e --- /dev/null +++ b/usr/kinit/fstype/btrfs_fs.h @@ -0,0 +1,51 @@ +#ifndef

I setup new server with dovecot 2.1.12 and mboxes from backup (moboxes was used with dovecot 1.1.6). OS: FreeBSD 8.3-STABLE, amd64. All index files from dovecot 1.1.6 has been deleted. Some times dovecot processes aborted. E. g. Jan 25 03:01:52 ost dovecot: lda(user at example.ru): Panic: file mail-transaction-log-file.c: line 1694 (mail_transaction_log_file_map): assertion failed:

Dovecot 1.1.7 is running so smoothly that I gave up checking its log files daily. :) I've just had a look, and among the usual "IMAP(username): FETCH for mailbox Sent UID xx got too little data: xx vs xx" messages (that means that unfortunately sometimes some messages are still written truncated) I saw this assertion failure: file mbox-sync.c: line 1305

Log: Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): /home/v/i/virus-al/Maildir/dovecot-uidlist: next_uid was lowered (216 -> 2) Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Panic: file index-sync.c: line 25 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Raw backtrace: imap [0x80efdb1]

GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as

Hi, While running imaptest with "clients=50 seed=123 msgs=100000000 random secs=600", I got errors : "Error: user at domain.com[55]: Unexpected BYE: * BYE IMAP session state is inconsistent, please relogin.". dovecot.log : Apr 03 10:23:47 imap(user at domain.com): Panic: file index- transaction.c: line 145 (index_transaction_rollback): assertion failed:

It might not be a fault in dovecot, as the user is accessing the folder locally with alpine while also running imap-sessions. However it would have been nice with a more graceful action than panic? The panic is preceeded by Error: Next message unexpectedly corrupted in mbox file PATH Panic: file mbox-sync.c: line 152 (mbox_sync_read_next_mail): assertion failed:

Hello Dovecot community, Below please find a patch that adds support to dovecot-1.2.11 for: - RFC 4467 - IMAP URLAUTH Extension - RFC 4468 - Submission BURL - RFC 4469 - IMAP CATENATE Extension URLAUTH URLAUTH is added as a plugin so it can be disabled to satisfy site security requirements. Each user's URLAUTH keys for all mailboxes are stored in a file named

We upgraded from Dovecot 1.0.15 to 1.2.5 last night, on Solaris 10 using mboxes, mostly without issues. However I had to trash the index/cache files (too many folders were showing corruption issues which is especially bad for Prayer Webmail ".prayer" folders that store preferences; Prayer sees a disconnection as the folder being missing!). I've had one imap process panic in mailbox

Hi, The following patches add support for ext4 and btrfs to PV-GRUB. These patches are taken nearly verbatim from those provided by Fedora and Gentoo. We''ve been using these patches for the PV-GRUB images available in EC2 for some time now with no problems. Changes from v1: - Makefile has been changed to check the exit code from patch - The btrfs patch has been rebased to apply