similar to: Plugin help, number of messages in mailbox

Hello, in addition to our mail system, we have some other systems which needs to know how many messages, and how many unread messages, a user has in his/her inbox (maildir). Currently, we have a mod_perl script which takes a mail address as input, and then traverses the maildir, and outputs the number of unread messages. Our challenge is that the maildirs are located on a SAN, and traversing a

Hi, I have a few questions regarding copy and save_finish methods. How can I get a filename or processing mail from the parameters you get in that methods? How could I use the logger you use for dovecot inside my plugin? Thanks, Sebastjan -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hello! I have port-built dovecot-1.1.1 on freebsd 6.3 i386 box. There is signal 11 on imap child occurs every time when i'm trying to send email. In fact, email is sending to MTA correctly, but when message moving to Sent folder segmentation error appears. I built dovecot and antispam plugin with -g3 -O0 -pipe With GDB I recieve next: GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software

Hi everyone, I am writing a dovecot statistic plugin, which calls mailbox_get_metadata() to get the virtual size of the mailbox, if a mail is copied. I have noticed that mailbox_get_metadata() calls mailbox_sync(), and mailbox_sync() will fail for the mailboxes with open transactions. But if a mail is copied, there must be at least one transaction opened for the mailbox. So I can not get the

Hi, We have a Ubuntu 14.04 server with dovecot 2.2.9 If I try to run /usr/bin/doveadm search -u email at exmaple.com mailbox Junk savedbefore 30d It will dump a core file. We have a similar config on an other server and there is no problem there. Any ideas how to prevent the core dump? root at triws2:~# gdb --args doveadm search -u email at example.com mailbox Junk savedbefore 30d Reading

The EC2 instance that I run Dovecot on (personal mail server) was forcibly "retired" yesterday, and as a result I ended up rebuilding from backups. In the process I switched from Ubuntu Precise to Ubuntu Xenial (12.04 to 16.04), and this in turn caused me to upgrade Dovecot from 2.0.19 to 2.0.22. Now, although accessing mail seems to work OK using my various clients, I am seeing

Hello, I am running dovecot 2.2.34 (874deae), on Debian stable, from backports. I just tried the master account, and although everything worked in the email client, I had logs in the error logs: > imap(mirina): Panic: file mail-index-sync.c: line 413 > (mail_index_sync_begin_to2): assertion failed: (!index->syncing) > Nov 08 22:06:24 osaka dovecot[1450]: imap(mirina): Error: Raw

Hello, I am working on fixing dovecot-antispam to work with dovecot 2.0. I am down to three errors/warnigns that concern me. The one I need help from those more familiar with dovecot internals is in the subject. What happened to mailbox_open? Did it disappear? Did it get renamed? It appears that I am needing to override some methods: if (need_folder_hook) { /* override

To some users happens this assertion failure while deleting a message. dovecot: Mar 10 08:40:44 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists (&ibox->recent_flags, uid)) dovecot: Mar 10 08:40:44 Error: IMAP(user): Raw backtrace: [see bleow] dovecot: Mar 10 08:40:44 Error: child 17683 (imap) killed with signal 6 And the

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

On 2018-11-09 05:25, Aki Tuomi wrote: > This seems to have nothing to do with master account or not. Does this > happen if you try to open the virtual mailbox again? > > Aki > >> On 09 November 2018 at 00:13 Andr? Rodier <andre at rodier.me> wrote: >> >> >> Hello, >> >> I am running dovecot 2.2.34 (874deae), on Debian stable, from

As promised, here it is finally. v1.0 is getting nearer and I want people to start looking at Dovecot's sources. Getting some more help with development would be nice, but I'd also like to hear if there are any hidden bugs in the code. So, one week from now I'll start offering 1000 EUR for the first person to point out a remotely exploitable security hole in Dovecot. See

Hi There! I run into this problem with virtual Mailboxes on release-2.3.2 (and also in master and in older versions of dovecot) I added the core-file. Jul 25 04:11:29 aldebaran dovecot[10573]: imap(jakob)<11292><rg2GZclxHaPAqADc>: Panic: Leaked view for index /var/lib/dovecot/db/indexes/Maildir/jakob/&ANY-BB/dovecot.index: Opened in index-storage.c:338 Jul 25 04:11:29

And can you provide dovecot --version too, please. Aki > On 25 July 2018 at 09:18 Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > Hi! > > Which debian release is this? > > Aki > > > On 25 July 2018 at 05:18 Jakobus Sch?rz <jakobus.schuerz at ebcont.com> wrote: > > > > > > Hi There! > > > > I run into this problem

On 13/04/16 06:41, Timo Sirainen wrote: > On 09 Apr 2016, at 21:48, Hugh Bragg <hughbragg at dodo.com.au> wrote: >> I'm repeatedly getting this error: >> >> Apr 07 04:37:27 imap(mymail at address): Panic: file mail-search.c: line 84 (mail_search_arg_init): assertion failed: (arg->initialized.keywords == NULL) >> Apr 07 04:37:27 imap(mymail at address):

Hi All, I'm new to the list and may be it's a known issue. I have a set of servers with RHEL6 and dovecot-2.2.10-1_14.el6.x86_64 and another set of servers with RHEL7 and, now, with dovecot-2.2.36-3.el7.x86_64. Both sets write to the same NFS. Since I updated RHEL7 servers (from 2.2.10-8.el7.x86_64) I've problems with index files when a RHEL7 dovecot service write to the

Hi. It seems that dovecot is using the current time, not a maildir file's mtime for INTERNALDATE when a message is re-indexed: $ cd Index $ rm -rf .INBOX $ cd ../Maildir/cur $ stat * File: `1392914632.P54451Q0M08633.smtpin01,S=2215,W=2249:2,' Size: 960 Blocks: 8 IO Block: 1048576 regular file Device: 36h/54d Inode: 11132959 Links: 1 Access: (0600/-rw-------)

Today we had an unclean shutdown of our NFS filler and have had lots of issues with mailboxes being re-synced, mostly all the issues are now resolved but we are seeing the following appear for one user on our system. Dec 19 16:15:29 imap(xxx.xxx at xxx.com)(xxx.xxx at xxx.com): Panic: file file-lock.c: line 287: unreached Dec 19 16:15:29 imap(xxx.xxx at xxx.com)(xxx.xxx at xxx.com): Error: Raw

It'd be useful for us if the IMAP passdb could be used as a prefetch userdb. The remote IMAP server could respond with something like * OK key=value * OK key=value SEQ OK [CAPABILITY ...] Logged in. Or * OK <some JSON key value pairs> SEQ OK [CAPABILITY ...] Logged in. Would anyone else find this useful?

Timo, A rare assert and core dump out of 1.0alpha3. My setup: Solaris 9, mbox format, using imap only. Built dovecot with gcc 4.0.1. The syslog for this was: Oct 14 11:57:56 emerald dovecot: [ID 107833 mail.info] imap-login: Login: user=<epmccull>, method=PLAIN, rip=137.146.210.59, lip=137.146.210.52, TLS Oct 14 11:58:56 emerald dovecot: [ID 107833 mail.info] imap-login: Login: