search for: map_uids

Is map_uid/guid going to be supported at IMAP protocol level? [via IMAP protocol extension] Specifically I would like to be able to: a) ask for mail_uid/GUID of specific message in mail store b) get list of folders containing copies of message with given mail_uid/GUID http://wiki2.dovecot.org/MailboxFormat/dbox#Multi-dbox Related:

Hello all, I have a problem with an incosistent mdbox: Oct 24 10:43:23 two dovecot: imap-login: Login: user=<...>, method=PLAIN, rip=..., lip=..., mpid=4977, TLS Oct 24 10:43:23 two dovecot: imap(listen at mjh.name): Error: mdbox map .../mdbox/storage/dovecot.map.index corrupted: Unexpectedly lost INBOX uid=638 map_uid=809891 Oct 24 10:43:23 two dovecot: imap(listen at mjh.name): Error:

Is there an easy way of "fixing" these? Oct 26 13:24:52 imap(account at domain): Error: mdbox map /var/mail/domain/account/mdbox/storage/dovecot.map.index corrupted: map_uid=2700 refcount too low (dovecot 2.1.17) -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick

I'm not sure what the code is trying to do, but the SGI Irix compiler spotted this usage of an undefined variable. In uidlist.c: ======= static int map_uid(int id, char *name) { uid_t uid; if (uid != 0 && name_to_uid(name, &uid)) return uid; return id; } static int map_gid(int id, char *name) { gid_t gid; if (gid != 0 && name_to_gid(name, &gid)) return

Hi Timo, hi all! Today i noticed imap throws segmentation faults and dumps cores. I looked into logs I can see: 2013-03-07T12:12:52.257986+01:00 meteor dovecot: imap(marcinxxx at kolekcja.mejor.pl) <7sRXtFPXYAA+eX93>: Error: Corrupted dbox file /dane/domeny/mejor.pl/mail/marcin//.mdbox/mailinglists/storage/m.75 (around offset=2779212): EOF reading msg header (got 0/30 bytes)

Hi, I have recently migrated (under emergency conditions) a dovecot imap/pop based server to a new instance. The mailboxes used mdbox format and due to various screwups I had corrupt indexes. I thought I'd cleaned this up but then I found that this new instance hadn't been set up correctly for nfs. Long story short, I still get users with new cases of corrupt indexes. The symptom is imap

On 25 Jul 2019, at 20.55, Mike via dovecot <dovecot at dovecot.org> wrote: > > Hi, > > > I have recently migrated (under emergency conditions) a dovecot imap/pop > based server to a new instance. The mailboxes used mdbox format and due > to various screwups I had corrupt indexes. I thought I'd cleaned this up > but then I found that this new instance hadn't

Hi, Sorry to bother the list again so soon after fixing my own problem, but I now have this issue when clients try to view shared folders in Thunderbird (v12). They can see the shared folder, but the first time they click on in nothing happens. The second time they get an authentication failure. The third or fourth time it finally loads the shared mailbox, and I see this a few times in the

I am looking at "mdbox" under Dovecot 2.0beta5. Looking at the documentation for "mdbox" I saw that we had a directory "storage" containing files "m.#" where "#" is an integer and a map file ("dovecot.map.index"). I think I expected the map file to be a plain text file with one record per line, but in fact it appears to contain

...m disk for indexes for mdbox is a really bad idea: /"Note that with dbox the Index files actually contain significant data which is held nowhere else. Index files for both *single-dbox* and *multi-dbox* contain message flags and keywords. For *multi-dbox*, the index file also contains the map_uids which link (via the "map index") to the actual message data. This data cannot be automatically recreated, so it is important that Index files are treated with the same care as message data files."/ So in mdbox we should not use a ramdisk for indexes. But what about sdbox? s...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello everybody, I have one thousand virtual users with mdbox mailbox format and 10 GByte quota. I have noticed some performance problem related to I/O (the mailbox disk is a 6TB raid1+0 on ISCSI), so I want to put the index files on a different disk. My actual mail_location is: mail_location = mdbox:/var/vmail/%-1.1u/%u/mdbox and I want to switch

Got a coredump: Mar 5 15:09:42 mail-cbf dovecot: lmtp(backup at backup.invalid)<15425><2B+kCaZPnVpBPAAAplP5LA>: Fatal: master: service(lmtp): child 15425 killed with signal 6 (core dumped) #0 0x00007fea19977428 in __GI_raise (sig=sig at entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54 resultvar = 0 pid = 15425 selftid = 15425 #1 0x00007fea1997902a in

Hi, On saturday one of our dovecot machines had an OOPS, and we had to powercycle it. When it came up, it did a filesystem fsck (ext4) and fixed a couple things, but nothing in lost+found. Now, about 50 users have a problem where their indexes are corrupted. Dovecot tries to fix them, but for some reason it is failing. The users are seeing their mails duplicated and they cannot delete mails. I

Hello everybody, We are updating our old dovecot 1.1 servers to 2.0. We have a farm os servers, with users in nfs filesystems and indexes in local fs. Mail is stored in maildir format. We don't warrant that a user is always directed to the same server, although our load balancer sends all request from one IP to the same server (during a session time with a inactivity timeout). This is

Gentlemen, I've setup 2 servers with dsync replication and hit a serious issue - some messages got duplicated thousands times in some shared mailboxes(~5). There is actually no reason to replicate anything from shared name space and I've tried to limit replication scope with just 'inbox' name space but it didn't help. dovecot version ||2.2.18 (2de3c7248922) errors in the

I could use some help with a corrupt mdbox. doveadm force-resync is crashing (see below), but I really need just to get this account functioning. What's my next step, as far as deleting index files? These were the earliest errors I could find: Nov 28 09:40:21 macy dovecot[6615]: imap(cory at metro-email.com): Error: Corrupted index cache file

Op 3/5/2018 om 3:14 PM schreef Ralf Hildebrandt: > Got a coredump: > > Mar 5 15:09:42 mail-cbf dovecot: lmtp(backup at backup.invalid)<15425><2B+kCaZPnVpBPAAAplP5LA>: Fatal: master: service(lmtp): child 15425 killed with signal 6 (core dumped) Hmm, yes, I think this an unnecessary RFC5322 -> RFC5321 address translation. Will look at making a fix tomorrow. Regards,

> We'll need the `dovecot -n` output first. Here we go: > # 2.2.devel (933d16f): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.devel (63f9b42) > # OS: Linux 3.13.0-98-generic x86_64 Ubuntu 14.04.5 LTS > default_vsz_limit = 2 G > lmtp_user_concurrency_limit = 10000 > mail_attachment_dir = /home/copymail/attachments > mail_location = mdbox:~/mdbox >

$ gdb /usr/lib/dovecot/lmtp core_lmtp.48883.nihlus.leuxner.net GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 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

Hi, I just found this in my logs: Apr 29 11:05:20 lmtp(joerg.eggenstein at ruhr-uni-bochum.de): Panic: file message-part-serialize.c: line 90 (part_serialize): assertion failed: (part->children == NULL) Apr 29 11:05:20 lmtp(joerg.eggenstein at ruhr-uni-bochum.de): Error: Raw backtrace: /usr/local/dovecot/lib/dovecot/libdovecot.so.0(+0x9c7f9) [0x7fa88bfbf7f9] ->