- dovecot - dovecot.org

[Dovecot] mail size needed in dovecot sieve log line
by Maciej Uhlig 26 Sep '12

26 Sep '12

This is a dovecot sieve log line: 2012-09-26T13:47:52+02:00 host/192.168.1.1 dovecot: [ID 583609 mail.info] lmtp(7565, user@domain): vTtJDTrrYlCNHQAAs1WjhA: sieve: msgid=<MSGID>: stored mail into mailbox 'INBOX' Would it be possible to have mail size logged here? MU

3 3

Re: [Dovecot] 76Gb to 146Gb
by Stan Hoeppner 26 Sep '12

26 Sep '12

On 9/25/2012 12:29 AM, Spyros Tsiolis wrote: > My clients don't invest in hardware. I live in Greece. Things are really > bad right now. Not that if they were better they (the client) would invest > in their infrastructure. ... > Thank you very much Stan for you kind reply. > > I reply to you in private since I was told to stop the thread > on the dovecot list because it's off-topic. I'm going to bring it back on topic. To recap the issue: 1. 73GB volume, ~82% full. Volume contains OS, spool, and mailboxes 2. Two 146GB drives on hand that are impossible to employ in either a live or offline migration due to hardware limitations--drive slots (0.82*73GB=60GB)-5GB(OS)= ~55GB/40= ~1.375GB/user mailbox (This math assumes the box has already been scoured and things like source files and other temporary stuff has already been removed, along with anything and everything not necessary to the primary functions of this box) 1.375GB/user suggests these users seem to horde old emails, or simply don't keep their mailboxes tidy. Normally I'd guess that a lot of space in a situation like this is taken up by full text search indexes, but you don't appear to have these enabled. I notice in your 'dovecot -n' output that you are already employing zlib, but to what degree is currently unknown to the list. Are you compressing maildirs with a nightly script? If not, and you're compressing on an ad hoc basis, realtime compression during write could save you quite a bit of additional space, extending the operating life of your current drives. Of course a simple request to your users to clean up their mailboxes would surely help as well, if that's a possibility--some users would flog one for making such a suggestion. If you're not fully taking advantage of compression currently, you may want to consider upgrading to Dovecot 2.x which allows transparent compression to dbox and maildir storage. You may want to migrate to mdbox message store format while still using zlib, and enable single instance attachment storage (SIS). As the name suggests, SIS saves an attachment only once, regardless how many user emails in which it exists. See: http://wiki2.dovecot.org/Plugins/Zlib I'd point you to the docs for SIS but I'm unable to find them in the Wiki. Surely someone else can provide the settings and/or update the wiki. -- Stan

1 0

[Dovecot] Can`t get over 1024 processes on FreeBSD - possible bug?
by Tomáš Randa 24 Sep '12

24 Sep '12

Hello, I still cannot get dovecot running with more then 1000 processes, but hard limit is 8192 per user in box. I tried everything, including modifying startup script of dovecot to set ulimit -u 8192. Could it be some dovecot bug or dovecot<>freebsd bug? I also tried to set client_limit=2 in imap service to spawn more imap clients in one process, but still I am over 1000 processes with kernel message: maxproc limit exceeded by uid 89 Could anybody help? Many thanks Tomas My system have following settings: FreeBSD 9.0 / AMD64 Dovecot 2.1.8 kern.maxproc: 12288 kern.maxfilesperproc: 36864 kern.maxprocperuid: 8192 no limit for uid 89: # limit cputime unlimited filesize unlimited datasize 33554432 kbytes stacksize 524288 kbytes coredumpsize unlimited memoryuse unlimited vmemoryuse unlimited descriptors 36864 memorylocked unlimited maxproc 8192 sbsize unlimited swapsize unlimited My dovecot.conf: # 2.1.8: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.0-STABLE amd64 auth_mechanisms = plain login digest-md5 cram-md5 default_client_limit = 2048 default_process_limit = 2048 disable_plaintext_auth = no first_valid_gid = 89 first_valid_uid = 89 info_log_path = /data/logfiles/dovecot/dovecot-info.log last_valid_gid = 89 last_valid_uid = 89 listen = * log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = Mail Toaster (Dovecot) ready. mail_location = maildir:~/Maildir mail_plugins = " quota" mail_privileged_group = mail maildir_broken_filename_sizes = yes passdb { driver = vpopmail } plugin { quota = maildir quota_rule = Trash:ignore sieve = ~/.sieve/dovecot.sieve sieve_dir = ~/.sieve } protocols = imap pop3 sieve service anvil { client_limit = 6147 } service auth { client_limit = 8192 unix_listener auth-client { mode = 0660 } unix_listener auth-master { mode = 0600 } } service imap-login { process_limit = 2048 service_count = 1 } service imap { client_limit = 1 process_limit = 2048 } service managesieve { process_limit = 2048 } service pop3-login { process_limit = 2048 service_count = 1 } service pop3 { client_limit = 1 process_limit = 2048 } shutdown_clients = no ssl_cert = </var/qmail/control/servercert.pem ssl_key = </var/qmail/control/servercert.pem userdb { args = blocking=yes driver = passwd } userdb { driver = vpopmail } verbose_proctitle = yes protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 2048 mail_plugins = quota imap_quota } protocol lda { mail_plugins = quota sieve sendmail_path = /var/qmail/bin/sendmail } protocol sieve { managesieve_implementation_string = dovecot managesieve_max_line_length = 65536 }

5 4

[Dovecot] Traffic Accounting
by M. Naumann 24 Sep '12

24 Sep '12

Hi, I'm trying to find out how to do traffic accounting with Dovecot 2.x, preferrably v2.0.9, preferrably on CentOS 6. I've previously asked on IRC, but there was little feedback, and my understanding is now this list is the preferred media for such inquiries. If I recall correctly, some weeks ago I was told that traffic accounting is not officially supported on Dovecot 2, but that there could still be ways to get it to work, but no details were provided. I can think of the following approaches: * rawlog, preferrably piped (if that's possible?) into something like wc to prevent privacy issues and to reduce the I/O overhead * maildrop filtering in front of dovecot LDA (for mail inbound to mail storage) * sieve filtering Unfortunately I have little experience with either so far, so it's hard to make a good choice. I would appreciate hints on these approaches, and on any other approaches you can think of, as well as any related documentation / how-to you could point me to. While I'm subscribed to the list (for mail authentication purposes), I've disabled receiving any e-mail form the list, so please CC me on any replies. Thanks in advance, Moritz

2 1

[Dovecot] Patches and dovecot releases
by Jean Michel 24 Sep '12

24 Sep '12

I'd like to know if after a release, for example the recently release 2.1.10, its common to see few days from the release some bug reports and algo some patches, are theses patches applyed on the daily builds ? ------------------------------ Jean Michel Feltrin

2 1

[Dovecot] Logging question regarding delete actions
by Ralf Hildebrandt 24 Sep '12

24 Sep '12

A user is logged in via imap from multiple devices. The log has this: Sep 21 11:46:32 postamt dovecot: imap(awxxxxer): delete: box=INBOX, uid=15347, msgid=<1341851741.4ffb085d2e2b7(a)swift.generated>, size=15675 Sep 21 11:46:32 postamt dovecot: imap(awxxxxer): delete: box=INBOX, uid=15739, msgid=<b23b2e42f6ae9ba1602690be42b7b5c7.squirrel(a)webmail.charite.de>, size=18134 Sep 21 11:46:32 postamt dovecot: imap(awxxxxer): delete: box=INBOX, uid=15740, msgid=<3509D8B3F9054C4BB26C85F3E4B96563036822877538(a)EXCHANGE21.charite.de>, size=22226 Sep 21 11:46:32 postamt dovecot: imap(awxxxxer): delete: box=INBOX, uid=15741, msgid=<C2E306F4-8622-4D0F-98BD-C67F31F2FF08(a)charite.de>, size=5160 How can I find out WHICH CLIENT caused the deletion? Same issue: Sep 21 09:36:05 postamt dovecot: imap-login: Login: user=<awxxxxer>, method=PLAIN, rip=109.45.0.37, lip=141.42.206.36, mpid=30773, TLS, session=<e8TfSjHKgwBtLQAl> Sep 21 10:06:17 postamt dovecot: imap(awxxxxer): Disconnected for inactivity in=2255 out=4398 How can I be sure that the log entry from 10:06:17 "belongs" to the log entry from "09:36:05"? Also, what is the meaning of the "session=<e8TfSjHKgwBtLQAl>"? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 2

[Dovecot] 2.1.10 imapc assert crash report
by Oli Schacher 24 Sep '12

24 Sep '12

Hi Timo I have a simple imapc gmail proxy test setup which works fine on 2.1.9, but crashes on 2.1.10 # 2.1.10: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.4.7-1-ARCH x86_64 auth_mechanisms = plain login imapc_host = imap.gmail.com imapc_port = 993 imapc_ssl = imaps imapc_ssl_ca_dir = /etc/ssl/certs listen = 127.0.0.1 mail_gid = imapproxy mail_home = /home/imapproxy/%u mail_location = imapc:~/imapc mail_uid = imapproxy passdb { args = host=imap.gmail.com port=993 ssl=imaps default_fields = userdb_imapc_user=%u userdb_imapc_password=%w userdb_imapc_ssl=imaps userdb_imapc_port=993 driver = imap } protocols = imap ssl = no userdb { driver = prefetch } Log: Sep 24 10:21:58 codemonkey dovecot: master: Dovecot v2.1.10 starting up Sep 24 10:22:12 codemonkey dovecot: auth: Panic: file imapc-connection.c: line 1289 (imapc_connection_connect_next_ip): assertion failed: (conn->client->set.max_idle_time > 0) Sep 24 10:22:12 codemonkey dovecot: auth: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x453aa) [0x7f8d5ce963aa] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x453ee) [0x7f8d5ce963ee] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f8d5ce6abd3] -> /usr/local/lib/dovecot/auth/libauthdb_imap.so(+0x977c) [0x7f8d5be3677c] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x3618e) [0x7f8d5ce8718e] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f8d5cea3006] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x7f8d5cea3df7] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f8d5cea2b48] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f8d5ce8eb93] -> dovecot/auth(main+0x2ff) [0x40ad4f] -> /lib/libc.so.6(__libc_start_main+0xf5) [0x7f8d5c27d725] -> dovecot/auth() [0x40af61] Sep 24 10:22:12 codemonkey dovecot: auth: Fatal: master: service(auth): child 24008 killed with signal 6 (core not dumped) Sep 24 10:22:12 codemonkey dovecot: imap-login: Warning: Auth connection closed with 1 pending requests (max 0 secs, pid=24007, EOF) Oli -- message transmitted on 100% recycled electrons

2 1

[Dovecot] dsync
by Emmanuel Dreyfus 24 Sep '12

24 Sep '12

Hi Testing dsync, things go wrong: doveadm sync -u user remote:root@mail2.example.net dsync-local(user): Error: Mailboxes don't have unique GUIDs: 72e3be2c6f203b50883c000044af56a8 is shared by RT and RT_72e3be2c6f203b50883c000044af56a8 Obviously RT_72e3be2c6f203b50883c000044af56a8 is an outdated copy of RT But .mailboxlist does not list that mailbox. Is there a trick to make sure dsync only use valid mailboxes? I have this in dovecot.conf mail_location = mbox:~/mail:INBOX=/var/mail/%u:INDEX=/mail/indexes/%u:SUBSCRIPTI ONS=../.mailboxlist Another problem, that may or may not be related: dsync-local(user): Error: Next message unexpectedly corrupted in mbox file /home/user/mail/RT at 60298748 dsync-local(user): Error: Failed to sync mailbox RT: Timeout while waiting for lock dsync-local(user): Error: Next message unexpectedly corrupted in mbox file /home/user/mail/RT at 63587421 dsync-local(user): Error: Failed to sync mailbox RT: Mailbox GUIDs are not permanent without index files I also get this: dsync-local(user): Error: Failed to sync mailbox RT: Mailbox GUIDs are not permanent without index files dsync-local(user): Error: proxy client timed out (waiting for MSG-GET message from remote) And this: dsync-local(user): Error: read() from worker server failed: EOF And generally speaking ,how good is dsync? is it usabel in production? This is on dovecot 2.1.7 -- Emmanuel Dreyfus manu(a)netbsd.org

1 0

[Dovecot] Sieve as mail client?
by Tom Horsley 23 Sep '12

23 Sep '12

A slightly off topic question, but maybe someone here has seen something like this: I want a program that operates entirely on the client side of an IMAP server, and implements the sieve filtering language by doing the necessary client side operations to move mail on the IMAP server, expunge mail, etc. It would also act as a proxy between my real mail client and the IMAP server so I'd never see any mail that hasn't been filtered first. The benefits are obvious: I could finally get sieve filtering on my stupid corporate exchange mail server :-).

3 4

[Dovecot] segfault in Debian Squeeze + Dovecot 2.1.10
by Joe Auty 22 Sep '12

22 Sep '12

Hello, I'm seeing a lot of these in my /var/log/messages in Debian Squeeze, I suspect this might be causing performance issues. Any suggestions what I can try to fix this? > [7236671.301179] imap-login[9306]: segfault at 28 ip 00007f9ff83c7e14 > sp 00007fff49d385c0 error 4 in libdovecot.so.0.0.0[7f9ff837c000+8b000] I'm using the 2.1.10 packages obtained with the following in my sources.list: deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.1 main I need to use Dovecot 2.1.x because I need to support handling multiple SSL certs. -- Joe Auty, NetMusician NetMusician helps musicians, bands and artists create beautiful, professional, custom designed, career-essential websites that are easy to maintain and to integrate with popular social networks. www.netmusician.org <http://www.netmusician.org> joe(a)netmusician.org <mailto:joe@netmusician.org>

1 0