similar to: Backend doesn't support GUIDs

Has anybody ever bothered to measure how many concurrent IMAP sessions dovecot can handle? I know it depends on hardware, filesystem, mailbox type etc., but what exactly controls the number and what have people on the list measured? p at rick -- state of mind Digitale Kommunikation http://www.state-of-mind.de Franziskanerstra?e 15 Telefon +49 89 3090 4664 81669 M?nchen

minutes gets repeated at nice_time_minutes. patch attached -- Jose Celestino <japc@co.sapo.pt> SysAdmin::SAPO.pt http://www.sapo.pt ----------------------------------------------------- "Lately, the only thing keeping me from becoming a serial killer is my distaste for manual labor." -- Dilbert -------------- next part -------------- *** icecast-1.3.12/src/ice_string.c

minutes gets repeated at nice_time_minutes. patch attached -- Jose Celestino <japc@co.sapo.pt> SysAdmin::SAPO.pt http://www.sapo.pt ----------------------------------------------------- "Lately, the only thing keeping me from becoming a serial killer is my distaste for manual labor." -- Dilbert -------------- next part -------------- *** icecast-1.3.12/src/ice_string.c

Some time ago I added the ability for IMAP clients to fetch messages' GUIDs using FETCH X-GUID command. Because of a bug it wasn't working in 1.2.0 or 1.2.1, but I've fixed it now. But now I'm starting to wonder: With Maildirs the GUIDs are the maildir base filenames, which contain host names. Is it a bad idea to expose them to users? -------------- next part -------------- A

Hello, I am running dovecot 2.2.12 Current mail storage is sdbox and I am trying to compress all emails, which works fine, except for a few old mailboxes. If I run the following dsync command "dsync -u flea -o "mail_plugins=zlib" mirror maildir:~/ndbox" It fails with: dsync(flea): Error: Exporting mailbox INBOX failed: Backend doesn't support GUIDs, sync with header

Imagine the following scenario Last Saturday, 3:00 AM a big phishing attack hits our e-mail inboxes. Spamassassin does not mark them as spam, and our 50.000+ users have in their mdbox a very credible phishing attack. What doveadm-fu could I use to delete (or move to spam) that e-mail from each user INBOX (let?s imagine the Subject or a Header is known)? I repeat: already delivered e-mail, how

How is verbose_proctitle supposed to work? I set it in the config but I don't see anything particularly verbose while the mailbox is connected. This is while the connection is open, immediately after deleting a message, before closing the connection. Same for IMAP and POP tests. # `ps axu | grep dove` # root 20392 0.0 0.0 1888 540 ? Ss 12:45 0:00 /usr/sbin/dovecot #

Hello Timo, I'd like to check if my understanding of dovecot-1.2.x's SSL certificate handling is correct : SSL does not provide the server any mechanism to choose which certificate it must send relatively to the name the client is using. Thus, if you want to use different certificates, you have to listen to different addresses. This is an SSL limitation, not a dovecot nor

Greetings I have a customer who has mail server running dovecot with an IMAP account (Customers) which contains hundreds of folders (one per customer). Looks like this: Customers Fred Smith and Co Joe Blogss Cust-1 Cust-n They have a requirement to report monthly on the total number of emails added to each customers' folder during the month. Basically I need to be

I purely love that kind of crap. As if presentations meant anything, as if there aren't all kinds of scholarly work about theoretical perfect world algorithms and conceptual systems that will never be implemented and are as practical and effective as wings on a pig. Please. I'm reminded of the story about how, during the American Civil War, when the North had finally, after years of

dbox format needs at least two tools: 1. Expunging only marks the message having refcount=0. The actual disk space is freed only after calling a tool pointing to the user's dbox dir. 2. Ability to force index resync/rebuild in case it doesn't figure out itself that there's something wrong. I'm starting to think about building a more generic mailutil tool, maybe something similar

If mailbox guids should be unique systemwide, would it be safe to delete all 'dovecot-uidlist' files of the user's mailboxes and then do a doveadm force-resync after mailbox migration? Thanks! Christian ----------------urspr?ngliche Nachricht----------------- Von: Christian Binder Stadt Freilassing [christian.binder at freilassing.de ] An: "dovecot dovecot.org" [dovecot

I have recently updated with 2.2.29.1-avh1~xenial1 ubuntu package on 16.04. It appears that I have a couple of duplicate GUIDs which fsck can't clear so the machine is looping through doing continuous fsck runs. Any way to determine what the offending messages are and how to delete or otherwise stop this? Jul 1 17:09:24 post dovecot: doveadm(djk at tobit.co.uk): Warning: fscking index

Update: seems to me that the old cyrus mailserver already uses these non-unique mailbox guids. Is it necessary to have them unique over all private namespaces? Thanks Christian ----------------urspr?ngliche Nachricht----------------- Von:Christian Binder Stadt Freilassing [christian.binder at freilassing.de ] An:"dovecot dovecot.org" [dovecot at dovecot.org ] Datum:Thu, 29 Jan 2015

Hi all I am using dovecot at home for privat use and i found a lot of documentation here on the web. But you know, i am an old fashion guy and i like books. Is there a book on the market that will help me with understanding dovecot more and the configuration options ? Thanks in advance for any suggestions. -- Regards, Carsten Laun-De Lellis Dipl.-Ing. Elektrotechnik Certified Information

Apr 30 18:12:48 postamt dovecot: dovecot v1.1.14 starting up (core dumps disabled) Uh, how do I enable them? -- Ralf Hildebrandt Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.computerbeschimpfung.de #!/bin/sh cat <<EOF | dc -e "[lila/sulila%Plusili0<y]sy?si256salyx" 403736150440747681954588245935305944858835839713675044439128476844672\

Recently I have in logs a LOT of messages like this: [....] Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13511 in m.1530:845670 (size=2622) and m.1371:1831730 (size=916) Nov 06 19:39:36 IMAP(kjonca): Error: mdbox /home/kjonca/Mail/1/storage: Duplicate GUID 13512 in m.1530:847414 (size=2274) and m.1371:1832476 (size=1069) Nov 06 19:39:36 IMAP(kjonca):

Greetings all, I can view a mailbox's GUID like so: doveadm mailbox status -u guid However, how may I *modify* a mailbox GUID? Can this be done using doveadm or some other tool? If not, how may I go about modifying the dovecot.mailbox.log (where I assume GUID data is stored)? My specific use case has to do with me wanting to modify an existing mailbox's GUID so that its messages

Dovecot version: 2.2.9 I'm using doveadm backup to migrate about hundred user mailboxes from cyrus to dovecot. I defined a master user for the old cyrus mailserver in imapc backend to get access to all the mailboxes. Now I realized that after migration every user's "Inbox" or "Trash" on the new dovecot server has the same mailbox-guid, e.g: User a: inbox dd9456...

Sorry if this is a duplicate message. I'm new in this mailing list and not sure if the first message really got posted ... Dovecot version: 2.2.9 We're using doveadm backup to migrate user mailboxes from cyrus to dovecot. I defined a master user for the old cyrus mailserver in imapc backend to get access to all the mailboxes. Now I realized that after migration every user's