search for: deles

I cleaned up the lib-storage code a bit so that it's easier to write support for new mailbox formats. It could still use a bit of cleaning up. Anyway, I thought I'd try how easy it would be to implement Cyrus-like mail store which would consist of only Dovecot's index files and "<uid>." message files. Flags and everything else is kept only in Dovecot's index files

I wasted too much time today doing this, but they do show a few interesting things: 1) mmap_disable=yes is faster than mmap_disable=no. I didn't expect this. I'm not yet sure why this is, but possibly because then it updates the mail index by reading the changes from dovecot.index.log, instead of reopening and re-mmaping dovecot.index. At least that's the biggest difference between

Hi folks I'm new to Dovecot. I'm wonderng if it's a way that dovecot delete a message just after the DELE POP3 command and not just mark the message for deletion and wait until the QUIT command is received. The main reason is for slow and unstable links fetching mail this is madness. Any suggestions? David

GMail doesn't delete mails when POP3 client issues a DELE command for it. Instead they just become invisible for future POP3 sessions, but they still exist for IMAP/webmail. The same could be implemented pretty easily for Dovecot: - Add a new setting to enable this: pop3_deleted_flag = $POP3Deleted - When DELEting a message, add this flag to the message. - When listing messages, skip all

We have done some benchmarking tests using dovecot 2.0.12 to find the best shared filesystem for hosting many users, here I share with you the results, notice the bad perfomance of all the shared filesystems against the local storage. Is there any specific optimization/tunning on dovecot for use GFS2 on rhel6??, we have configured the director to make the user mailbox persistent in a node, we will

Some new features in CVS HEAD are: - v1.0 saves most of the data to dovecot.index.cache only when the client is FETCHing the messages. With mboxes the message headers are saved while parsing the mbox, which is almost the same thing. With CVS HEAD the dovecot.index.cache file is updated already when the new messages are being saved (with deliver or IMAP APPEND). This avoids reading the message

I thought I'd try benchmarking with dbmail (v2.2.4) to see how much slower a SQL backend could actually be. Skip to bottom for the conclusions. Originally I ran the tests with the databases being in XFS filesystem. MySQL's performance was horrible. It went 3-7x faster with ext3. MySQL 5.0.30 backend (innodb): ./imaptest clients=1 - append=100 seed=1 secs=30 msgs=1000000 logout=0

Hi folks A POP3 client not configured to keep a copy of messages on the server, as soon as retieve a message send a DELE commando with the number of the just retrieved message. Then, at the end of the POP3 session, the clent sends a QUIT command, wich order POP3 server to close the conection and delete the messages marqued with DELE command. So, I'm wondering if it's possible to tell

To simplify recovery of accidentally deleted messages we'd like to send all messages that are deleted by pop clients to their Trash folder. (Which is auto expired already.) This allows a POP client who deletes an important email to restore it themselves by logging into our webmail client and move the lost message from Trash to the Inbox where it would be fetched by their client again. Has

Hi, it looks like there is a bug (in dovecot or in my config) with quota on maildir mailboxes when accessed via POP3. The maildirsize is not created when not already present (even after a DELE + QUIT command). The quota limit (the first line of maildirsize) is not updated if values are not in sync with those in the database. If maildirsize is present, DELE commands are correctly reported in

Hi All, We're on migration stage to a new 2-node active/active cluster with shared iSCSI storage,? everything is ready, but we are in the process of I/O testing, before we going to in production. Cluster info: 2 nodes with CentOS 7.4 balancer ( keepalived + ldirectord ), 2 dovecot directors, 2 dovecot IMAP backends, 2 Postfix SMTP, gfs2 ( corosync + dlm ), LMTP between Postfix and Dovecot

v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to have a stable v1.1 in a month or two. The rest of the features that didn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0:

Hi, When I enable (and it only happens when it is actually running) replication over TCP my users get duplicate mails via pop3. Here?s what happens: * User gets mail * Mail appears in (Maildir) new/ folder on both replicas * user retrieves mail (retr), calls dele. Mail still exists in new/ folder on both replicas. * user runs retr (and gets the duplicate) and dele a second time, the mail is

Hi, The measurements were created under the following conditions : ? operating system : Red Hat Enterprise Linux Server release 6.6 (Santiago) kernel in version 2.6.32-504.el6.x86_64 ? virtual server (VMware) with an Intel(R) Xeon(R) 4vCPU E5649 x 2,526 GHz (2 cores per virtual socket) and 4 GB RAM ? 7,200 RPM SATA 1TB (FC SAN IBM System Storage N3400) ? all file systems had been formated in

Greetings - I've now got as far as playing with the imaptest10 test utility to see if I can stress-test our development server. imaptest10 is built against dovecot-1.0rc28 It may just be that I'm excessively heavy handed, but when I let imaptest10 rip with the command... ./imaptest10 user=test%03d host=testserver.imap.york.ac.uk clients=50 mbox=./dovecot.mbox msgs=1000 secs=30

http://dovecot.org/patches/1.1/maildir-dirty-syncs.diff This patch adds a new maildir_very_dirty_syncs setting. If set to "yes", Dovecot assumes it's the only one changing the cur/ directory (so other MDAs can add mails to new/ without problems). This makes it possible to avoid rescanning the cur/ directory all the time looking for filenames. It also looks like (in stress testing)

dovecot-1.1.beta16]# gcc imaptest.c -o imaptest -g -Wall -W -I. -Isrc/lib-mail -Isrc/lib -Isrc/lib-imap -Isrc/lib-storage/index/mbox -DHAVE_CONFIG_H src/lib-storage/index/mbox/mbox-from.o src/lib-imap/libimap.a src/lib-mail/libmail.a src/lib/liblib.a imaptest.c: In client_append function: imaptest.c:1492: error: too many arguments for i_stream_create_limit function

I've read about one month back this list's messages. I've still 216 messages from this year marked as "unread" which I should look into more (+258 older ones). Also I've 180 "unread" messages in my INBOX also which might contain something useful. So those messages could still contain something that should be added to this list. Anyway looking at my current

I'd like to use Dovecot as our IMAP server when our users are within our LAN, but I'd also like to give them the ability to access their emails via POP3 when they are outside the LAN. I know most POP3 clients will give their users the option of not deleting the messages from the server after they are downloaded, but is there any way to restrict them from being able to do so at the server

Hi List, I of present dovecot 1.1.10 use it, and test dict quota backend and mysql. However, I am troubled so that it is IMAP4, and behavior when mysql fell is different from POP3. I become the error in Copy of Mail in IMAP4, but do not become the error in DELE of the POP3. Therefore I think that contradiction happens in database and real storage when mysql fell. I want an error to do it at the