search for: mail_indexes

Hi welcome I want to set some virtual users with sdbox mail_location so I return in password_query and user_query extra field mail which contains sdbox:/var/mail/example.com/user:INDEX=/var/mail_indexes/example.com/user:ALT=/var/mail_altstorage/example.com/user and then when i send email to user at example.com I see all sdbox dirs created but when i login with thunderbird IMAP - Maildir structure is always created with an empty INBOX I tried to override namespace inbox with mail AS "namespa...

Originally reported here - https://marc.info/?l=openbsd-ports&m=159731598419071&w=2 OpenBSD's printf functions have a (mostly annoying but occasionally useful) feature where they generate a syslog entry if printf %s format is called with a null pointer. It is tripped in lmtp/lda deliveries with 2.3.11.3: lmtp: vfprintf %s NULL in "Cache %s: " dovecot-lda: vfprintf %s NULL

We are just trying to bring up a new server and chose to use Dovecot rather than the uw-imap from our previous servers. At this point I am just testing with some throw away accounts using squirrelmail. I can load my inbox, but then the imap connection is lost. I presume you need some real information to get your teeth into, so this is going to get a little long. I'll give you three things

Hello everyone, please keep my CC'd, I'm not on the list. I've been using dovecot happily via an ssh tunnel. My mutt is configured to use IMAP, and the tunnel is as follows in my muttrc: set tunnel="ssh -q mymailhost 'MBOX_LOCKS=fcntl MAIL=/home/jlbec/mail /usr/libexec/dovecot/imap'" It should be pretty obvious that this logs into mymailhost as me (via SSH

Hi Timo, Awhile back I'd written about making changes to some of the log levels that dovecot writes to to stop the process from writing these to monitor. I wanted to run a few changes by you for this, just to make sure these won't cause problems somewhere else. And to send this to the list, in case anyone else wants to make similar changes in the future. In the file

Hello, First, thanks for this great piece of software. I'm new to dovecot and i've just converted my old courier configuration on pop/imap server side, everithing is working just fine on this side and speed gain expected was found (not enough for our busy servers :). Setup is done with 3 dovecot virtual servers load balanced with a Hardware load balancer (this part is a big point of the

Hi! I've now seen this assertion failure from lmtp (most frequent), pop3 (next frequent), and imap (rarely). It didn't start happening until the number of accounts on the server was increased into the 10k-25k range. It happens when index->file_lock is a read lock and mail_index_lock is called asking for a write lock. Dovecot 2.x dies at the assertion on line 62 of mail-index-lock.c

...bexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_greeting: Dovecot ready. verbose_proctitle: yes first_valid_uid: 102 mail_extra_groups: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u:INDEX=/var/mail_indexes/%d/%n mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/...

Part of our migration plan takes our users from one endianness to another (big to little). Will the index and mail cache files survive? I'm seeing some new core dumps as the first test user is migrated, which makes me think... not. What about if we want to build dovecot 64 bit in the future? Will that cause problems too? Stack trace is below the log messages. I've edited the

mbox-index.c uses a zero content length as a flag for an invalid Content-Length: header. Unfortunately zero is also a valid value for Content-Length. The patch below attempts to address the problem. *** mbox-index.h.orig Tue Apr 15 09:04:02 2003 --- mbox-index.h Sun Apr 20 11:42:12 2003 *************** *** 19,24 **** --- 19,25 ---- struct istream *input; uoff_t

I now have default_mail_env = mbox:~/mail:INBOX=:/var/spool/mail/%u I now getting: Apr 26 15:55:32 jedrik imap(mclay): open() failed with mbox file : No such file or directory I tracked down where the error message is getting generated and added some more printing: In mbox-index.c I added: int mbox_set_syscall_error(struct mail_index *index, const char *function) { i_assert(function !=

On 27/03/2019 16:12, Timo Sirainen wrote: > On 27 Mar 2019, at 14.58, Timo Sirainen via dovecot <dovecot at dovecot.org > <mailto:dovecot at dovecot.org>> wrote: >> >>> dovecot isn't able to auto fix the indexes and manual deletion is >>> required in all such cases >> >> So if it keeps repeating, it's very strange. Could you send me

Hi Just u/g to RH FC3 from RH8.0 which seemed to work fine with quotas. I have quotas for usernames set up as /home/domain/domainX/username/ for web space 50MB say 48MB used so 2MB free and /var/mail/spool/username for email. 100MB (60MB used so 40MB is available). /var/mail/username is symbolic linked via to spool/mail under /var dovecot seems to be using the quota for /home/.. and sees

2 backtraces: 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

On 27 Mar 2019, at 14.58, Timo Sirainen via dovecot <dovecot at dovecot.org> wrote: > >> dovecot isn't able to auto fix the indexes and manual deletion is >> required in all such cases > > So if it keeps repeating, it's very strange. Could you send me such broken dovecot.index and dovecot.index.log files (without dovecot.index.cache)? They shouldn't contain

Hi- I was able to get a coredump out of the new pop3 (from 0.99.9-test4) by attempting to simulate the execution environment and simply running the pop3 program. Running the older pop3 from 0.99.8.1 works fine, repeatedly: % /usr/local/libexec/dovecot/pop3 quit +OK Logging out. However running the new one: % /usr/local/libexec/dovecot/pop3.new pop3(user9): Error: Corrupted index file

I am getting some panics after upgrading from 2.2.13 to 2.2.14 This panic happens for one user only, he is subscribed to 86 folders, on two of them this panic happens quite often - several times a day. The mbox folders seems OK, less than 30M with 30 and 200 messages. Panic: file mail-index-sync-update.c: line 250 (sync_expunge_range): assertion failed: (count > 0) hmk GNU gdb 6.8

I've attached a few assertion errors in imap. Any fixes or advice on where to look are appreciated. This is with the CVS version, current as of April 27. Todd Burroughs -------------- next part -------------- dovecot: Apr 27 00:00:45 Error: 5714 IMAP(chairman): file mail-index-transaction.c: line 808 (mail_index_update_ext): assertion failed: (seq > 0 && (seq <=

Today morning I had an idea how to make indexes more scalable with multiple concurrent writers. As a side effect it also made the locking issues much more simpler. So I thought I'd go and rewrite all the indexing code, it had gotten way too ugly and difficult to understand and maintain. I also thought to separate the index handling completely from mailbox handling. So there would be lib-index

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