- dovecot - dovecot.org

[Dovecot] Append with literal+ and mailbox over quota
by Ewald Dieterich 19 Jul '12

19 Jul '12

I'm appending a mail with literal+ to a mailbox that is over quota: 1 APPEND INBOX {127+} From: <ewald.dieterich(a)fun.de> To: <ewald.dieterich(a)fun.de> Subject: Quota-Test Message-ID: <abcdefg(a)fun.de> Quota-Test 1 NO [OVERQUOTA] Quota exceeded (mailbox for user is full) 2 NOOP 1 BAD Error in IMAP command APPEND: Invalid arguments. 3 NOOP 3 OK NOOP completed. Somehow the first NOOP is considered to be part of the already failed APPEND. I have to add an empty line after to NO response for the NOOP to work: 1 APPEND INBOX {127+} From: <ewald.dieterich(a)fun.de> To: <ewald.dieterich(a)fun.de> Subject: Quota-Test Message-ID: <abcdefg(a)fun.de> Quota-Test 1 NO [OVERQUOTA] Quota exceeded (mailbox for user is full) 2 NOOP 2 OK NOOP completed. Can somebody confirm this to be bug? Here is the output of doveconf -n # 2.1.8: /usr/local/dovecot-orig/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.3 ext3 auth_debug = yes auth_verbose = yes debug_log_path = /var/log/dovecot/debug.log disable_plaintext_auth = no info_log_path = /var/log/dovecot/info.log log_path = /var/log/dovecot/error.log mail_debug = yes mail_location = mdbox:/var/spool/dovecot/%2.256Hu/%3.4096Hu/%u mail_plugins = notify mail_log quota acl namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { driver = pam } plugin { acl = vfile autocreate = INBOX.Drafts autocreate2 = INBOX.Sent autocreate3 = INBOX.Trash quota = dict:User quota::file:/var/spool/dovecot/%2.256Hu/%3.4096/%u/dovecot.dict quota_rule = *:bytes=2000 } ssl = no userdb { driver = passwd } protocol imap { mail_plugins = notify mail_log quota acl autocreate imap_quota imap_acl

1 1

[Dovecot] Disable W=<vsize> in filenames
by Daniel Pieper 19 Jul '12

19 Jul '12

Hi, I'm using Dovecot 2.1.8. Is it possible to deactivate the "W=" Maildir filename extension, so that dovecot not add it to maildir filenames?

2 1

[Dovecot] Converting from Maildir format ?
by Nick＠5sg.eu 19 Jul '12

19 Jul '12

Hi again, I'm still trying to find out if anyone knows the correct way to either switch the existing Maildir multiple file format to the single file format I believe known as MBox. Failing that, though it'll mean a LOT of work for me to manually convert all of the existing Maildirs, how do I get dovecot to work in future in MBox single file format. I tried entering 'mail_location = mbox:~/mail:INBOX=/%h/%u' in the 'dovecot.conf', but it still saves each message in a file of its own in the /new /cur /tmp directories ?? Thanks, Nick. . . . . -- _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ . . . . . . . . ...---... (Stamp Out Spam and Save Our Servers) http://sosNow.ws -=[ do you know morse code ? ]=- . . . . . . . . _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/

3 2

[Dovecot] Make a whole mailbox read-only
by Sandro Tosi 19 Jul '12

19 Jul '12

Hello, i've found an old thread [1] where it was stated that a whole mailbox can be made read-only only setting the according permissions on the filesystem side. [1] http://www.mailinglistarchive.com/html/dovecot@dovecot.org/2011-12/msg00300… i'd like to check if it's still the only option we have with dovecot v2.0.18 . Regards, -- Sandro Tosi Product Engineer Shared Hosting Products R&D | Dada.pro eml sandro.tosi(a)register.it

3 5

Re: [Dovecot] Issues with Plus addressing and detail part of subaddress.
by Sean Kamath 19 Jul '12

19 Jul '12

On Jul 17, 2012, at 3:18 AM, Charles Marcus wrote: >> I really thought it would be a simple "here's what you missed", since >> the logs are relatively uninformative... > > The point is, what may appear to be uninformative to you may tell Timo (or someone else who knows what to look for) all they need to know to pinpoint the problem. Whilst I would normally agree, at the same time I've had a fair amount of experience with dovecot and sendmail (been running them for over 10 years). Pigeonhole is new to me, however. . . > One thing I did notice is that you are sending this mail from an internal IP... since most people use very different checks for such mail (bypassing many/most checks), maybe you should be testing from an external address (one that comes in from outside your network)? So I have a DMZ that houses the mail server for my domain, which is where the private addresses are. Connections are passed through the OpenBSD router to the mail server. So testing from an external address would be essentially the same (since the connection to the SMTP server talks to the sendmail process as the /usr/lib/sendmail process). Regardless, my original tests were sending mail from the Mac off-network. > Also, it is always recommended when setting up a new server to start with the latest version... for 2.0.x that would be 2.0.19, but the latest is 2.1.8... When I set it up, 2.0.13 _was_ the latest. :-) I was hoping to avoid the pain of recompiling dovecot and pigeonhole. Not that big a deal, I guess. . . >> lda_original_recipient_header = X-Original-To >> lmtp_save_to_detail_mailbox = yes > > Ok, I think this is the problem... > > Dovecot's LMTP currently does NOT preserve the x-original-to header... in fact, brought this up recently (I was one of the ones interested in Timo adding support for it) on this (and the postfix, which is what I use) on this very list: > > http://www.dovecot.org/list/dovecot/2012-April/065075.html > > Apparently, after Timo discussed this on the postfix list, he determined that it would not be a very significant change for him to make to add support for this header in LMTP and that he would get to it sooner than later, but as of now, it has not been added. Actually, I'm not using lmtp. I whacked the lmtp_save_to_detail_mailbox in an effort to see if that was the issue before I realized I don't have it turned on. dovecot.conf has: protocols = imap though in 20-managesieve.conf I have: protocols = $protocols sieve I just turned it off and restarted dovecot (though lmtp was not running) and re-ran the test with the same result. So, I think what's going on is pretty straightforward. The local mailer definition in the sendmail.cf file is: Mlocal, P=/usr/local/libexec/dovecot/dovecot-lda, F=lsDFMAw5:/|@qSPhn9, S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, T=DNS/RFC822/X-Unix, A=/usr/local/libexec/dovecot/dovecot-lda -d $u This is more or less right out of the wiki. Since dovecot-lda is passed the -d option, it's using that (and only that) for delivery. Since there's no X-Original-To: header, it doesn't really have any option (since the non-envelope-to address might not exist, or point to something other than the end user's mailbox, etc). It would appear that I have two options: 1) Figure out what macro(s) is(are) valid to pass to dovecot-lda with the -a option in the sendmail config file (sendmail.cf). 2) Get sendmail to put "X-Original-To: <address>" in the header. Both would appear to be a sendmail issue, not a dovecot/pigeonhole issue. Everything I find on the web seems to center around how to use plus addressing to accept mail from multiple email address and filter it into a single address for delivery, only to have the local delivery agent break it back out again. That's not my issue. :-( Sean Sean

1 1

[Dovecot] doesn't work at all
by David Drexler 19 Jul '12

19 Jul '12

Hi, I can't seem to get dovecot to work. When I connect with thunderbird, tbird complains that it can't find the settings for my email. When I connect with evolution, it seems to go through all the motions but it doesn't pick up the waiting messages. Those messages are marked Status: O s if it had read them. The log file for tbird looks like this: Jul 18 17:03:21 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 The log file with evolution is: Jul 17 19:36:43 why dovecot: imap-login: Login: user=<ddrex>, method=PLAIN, rip=68. 12.110.134, lip=184.176.6.227, mpid=22717, TLS Jul 17 19:36:43 why dovecot: imap(ddrex): Debug: Effective uid=500, gid=500, home=/ home/ddrex Jul 17 19:36:43 why dovecot: imap(ddrex): Debug: fs: root=/home/ddrex/mail, index=, control=, inbox=/var/mail/ddrex Jul 17 19:46:17 why dovecot: imap(ddrex): Error: Next message unexpectedly corrupte d in mbox file /var/mail/ddrex at 1504 My conf file: # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-220.23.1.el6.x86_64 x86_64 CentOS release 6.2 (Final) base_dir = /var/run/dovecot/ imap_client_workarounds = "delay-newmail " listen = * mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail mbox_very_dirty_syncs = yes mbox_write_locks = fcntl passdb { driver = pam } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh protocols = imap pop3 service imap-login { vsz_limit = 64 M } service pop3-login { vsz_limit = 64 M } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } -------------------------------------------------------------------- Thanks for any clues. dd

2 2

[Dovecot] SQLite dovecot query caching
by Dominic Malolepszy 19 Jul '12

19 Jul '12

Hi, I am wondering if Dovecot caches SQLite queries, and how well it works in high performance setups. I am particularly interested because in the below thread SQLite has been suggested as a means of Dovecot proxying connections to different ports. http://old.nabble.com/director%3A-non-standart-ports-at-backends-td33991991… Cheers, Dominic.

2 7

[Dovecot] MySQL dict issues
by list＠airstreamcomm.net 18 Jul '12

18 Jul '12

Testing using the mysql dict for quota storage (dovecot-2.0.12-2_127.el5), and ran into a couple issues. First is a permissions issue: dovecot: lmtp(26786, dude(a)test.tld) Error: net_connect_unix(/var/run/dovecot/dict) failed: Permission denied (euid=5000(<unknown>) egid=5000(<unknown>) missing +r perm: /var/run/dovecot/dict, euid is not dir owner) The file /var/run/dovecot/dict is listed with srw------- perms. I changes the perms to srw----rwx and it works, but I would like to figure out how to configure properly to run with the uid and gid 5000 as this is the user for virtual mail. The second issue is that two identical rows are created in the mysql database for each user quota. The next message delivered updates both rows. Here is my quota config: 90-quota.conf: plugin { quota_rule = *:storage=10G quota_rule2 = Trash:storage=+10% } plugin { quota = dict:user::proxy::userquota } dict { userquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } dovecot-dict-sql.conf.ext: connect = host=a.b.c.d dbname=mail user=user password=derp map { pattern = priv/quota/storage table = domain_user_quotas username_field = username value_field = bytes } map { pattern = priv/quota/messages table = domain_user_quotas username_field = username value_field = message_count } The last issue might be a documentation omission. Dovecot warned me that the mysql user did not have DELETE privileges on the quota table: dovecot: dict: Error: sql dict: commit failed: DELETE command denied to user 'user'@'a.b.c.d' for table 'domain_user_quotas' The quota dict documentation (at http://wiki2.dovecot.org/Quota/Dict) does not mention DELETE being needed: MySQL uses the following queries to update the quota. You need suitable privileges. INSERT INTO table (bytes,username) VALUES ('112497180','foo(a)spam.dom') ON DUPLICATE KEY UPDATE bytes='112497180'; INSERT INTO table (messages,username) VALUES ('1743','foo(a)spam.dom') ON DUPLICATE KEY UPDATE messages='1743'; UPDATE table SET bytes=bytes-14433,messages=messages-2 WHERE username = 'foo(a)spam.dom';

2 2

[Dovecot] Dovecot-2.1.8 process imap crashed
by Marcin Mirosław 18 Jul '12

18 Jul '12

Hello! I've just upgraded dovecot from 2.0.18 to 2.1.8 and configured impac. I notice dovecot/imap throws segfault from time to time. I'm not sure i know what steps are needed to reproduce problem. I'm using gentoo, hardened-kernel-3.4.2. Namespaces (and settings for imapc) are keept in database so i'm not sure doveconf would be useful. If would be needed please let me know. Thanks Marcin Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x000002d0fbf908a2 in mail_storage_set_internal_error (storage=0x0) at mail-storage.c:466 466 mail-storage.c: No such file or directory. in mail-storage.c (gdb) bt #0 0x000002d0fbf908a2 in mail_storage_set_internal_error (storage=0x0) at mail-storage.c:466 #1 0x000002d0fbf5f025 in imapc_noop_callback (reply=<optimized out>, context=<optimized out>) at imapc-storage.c:691 #2 0x000002d0fbf5f07a in imapc_idle_noop_callback (reply=<optimized out>, context=0x2b466158c0) at imapc-storage.c:713 #3 0x000002d0fbf6208a in imapc_connection_abort_commands (conn=0x2b46579c10, disconnected=<optimized out>, keep_retriable=<optimized out>) at imapc-connection.c:271 #4 0x000002d0fbf624be in imapc_connection_disconnect (conn=0x2b46579c10) at imapc-connection.c:371 #5 0x000002d0fbf636b9 in imapc_connection_deinit (_conn=0x2b46579b20) at imapc-connection.c:178 #6 0x000002d0fbf60113 in imapc_client_deinit (_client=0x2b4655b6e8) at imapc-client.c:111 #7 0x000002d0fbf5ea77 in imapc_storage_destroy (_storage=<optimized out>) at imapc-storage.c:275 #8 0x000002d0fbf90600 in mail_storage_unref (_storage=0x2b46558910) at mail-storage.c:417 #9 0x000002d0fbf8a259 in mail_namespace_free (ns=0x2b465588c0) at mail-namespace.c:37 #10 0x000002d0fbf8a784 in mail_namespaces_deinit (_namespaces=0x2b4654c9e8) at mail-namespace.c:437 #11 0x000002d0fbf95311 in mail_user_deinit_base (user=0x2b4654c970) at mail-user.c:29 #12 0x000002d0f940f658 in stats_user_deinit (user=0x2b4654c970) at stats-plugin.c:506 #13 0x000002d0fa86b619 in quota_user_deinit (user=0x2b4654c970) at quota-storage.c:412 #14 0x000002d0fbf95597 in mail_user_unref (_user=<optimized out>) at mail-user.c:153 #15 0x0000002b4461b58e in client_destroy (client=0x2b465891d0, reason=0x0) at imap-client.c:219 #16 0x0000002b44615552 in idle_client_input (ctx=<optimized out>) at cmd-idle.c:113 #17 0x000002d0fbce3767 in io_loop_call_io (io=0x2b46622ff0) at ioloop.c:379 #18 0x000002d0fbce469a in io_loop_handler_run (ioloop=<optimized out>) at ioloop-epoll.c:213 #19 0x000002d0fbce3054 in io_loop_run (ioloop=0x2b46525aa0) at ioloop.c:398 #20 0x000002d0fbccc446 in master_service_run (service=0x2b46525950, callback=<optimized out>) at master-service.c:543 #21 0x0000002b44624e76 in main (argc=1, argv=0x2b46525790) at main.c:389 (gdb) bt full #0 0x000002d0fbf908a2 in mail_storage_set_internal_error (storage=0x0) at mail-storage.c:466 str = 0x2b4651e840 "Internal error occurred. Refer to server log for more information. [2012-07-17 16:06:09]" #1 0x000002d0fbf5f025 in imapc_noop_callback (reply=<optimized out>, context=<optimized out>) at imapc-storage.c:691 storage = <optimized out> #2 0x000002d0fbf5f07a in imapc_idle_noop_callback (reply=<optimized out>, context=0x2b466158c0) at imapc-storage.c:713 mbox = 0x2b466158c0 #3 0x000002d0fbf6208a in imapc_connection_abort_commands (conn=0x2b46579c10, disconnected=<optimized out>, keep_retriable=<optimized out>) at imapc-connection.c:271 cmdp = 0x2b4651e808 cmd = 0x2b466116a0 tmp_array = {arr = {buffer = 0x2b4651e7c8, element_size = 8}, v = 0x2b4651e7c8, v_modifiable = 0x2b4651e7c8} reply = {state = IMAPC_COMMAND_STATE_DISCONNECTED, resp_text_key = 0x0, resp_text_value = 0x0, text_full = 0x2d0fbfe768e "Disconnected from server", text_without_resp = 0x2d0fbfe768e "Disconnected from server"} #4 0x000002d0fbf624be in imapc_connection_disconnect (conn=0x2b46579c10) at imapc-connection.c:371 reconnecting = false #5 0x000002d0fbf636b9 in imapc_connection_deinit (_conn=0x2b46579b20) at imapc-connection.c:178 No locals. #6 0x000002d0fbf60113 in imapc_client_deinit (_client=0x2b4655b6e8) at imapc-client.c:111 client = 0x2b4655c6e0 connp = 0x2b4655c840 __FUNCTION__ = "imapc_client_deinit" #7 0x000002d0fbf5ea77 in imapc_storage_destroy (_storage=<optimized out>) at imapc-storage.c:275 storage = <optimized out> #8 0x000002d0fbf90600 in mail_storage_unref (_storage=0x2b46558910) at mail-storage.c:417 storage = 0x2b4655b5e0 __FUNCTION__ = "mail_storage_unref" #9 0x000002d0fbf8a259 in mail_namespace_free (ns=0x2b465588c0) at mail-namespace.c:37 No locals. #10 0x000002d0fbf8a784 in mail_namespaces_deinit (_namespaces=0x2b4654c9e8) at mail-namespace.c:437 ns = <optimized out> next = 0x2b46550dd0 #11 0x000002d0fbf95311 in mail_user_deinit_base (user=0x2b4654c970) at mail-user.c:29 No locals. #12 0x000002d0f940f658 in stats_user_deinit (user=0x2b4654c970) at stats-plugin.c:506 suser = 0x2b4654e8c8 stats_conn = 0x2b46552170 __FUNCTION__ = "stats_user_deinit" #13 0x000002d0fa86b619 in quota_user_deinit (user=0x2b4654c970) at quota-storage.c:412 quser = 0x2b4654e890 quota_set = 0x2b46551190 #14 0x000002d0fbf95597 in mail_user_unref (_user=<optimized out>) at mail-user.c:153 user = 0x2b4654c970 __FUNCTION__ = "mail_user_unref" #15 0x0000002b4461b58e in client_destroy (client=0x2b465891d0, reason=0x0) at imap-client.c:219 cmd = <optimized out> __FUNCTION__ = "client_destroy" #16 0x0000002b44615552 in idle_client_input (ctx=<optimized out>) at cmd-idle.c:113 ---Type <return> to continue, or q <return> to quit--- client = 0x2b465891d0 #17 0x000002d0fbce3767 in io_loop_call_io (io=0x2b46622ff0) at ioloop.c:379 ioloop = 0x2b46525aa0 t_id = 2 #18 0x000002d0fbce469a in io_loop_handler_run (ioloop=<optimized out>) at ioloop-epoll.c:213 ctx = 0x2b46525e10 events = <optimized out> event = 0x2b46525e80 list = 0x2b465a80a0 io = <optimized out> tv = {tv_sec = 5, tv_usec = 999824} msecs = <optimized out> ret = 1 i = <optimized out> j = <optimized out> call = <optimized out> #19 0x000002d0fbce3054 in io_loop_run (ioloop=0x2b46525aa0) at ioloop.c:398 No locals. #20 0x000002d0fbccc446 in master_service_run (service=0x2b46525950, callback=<optimized out>) at master-service.c:543 No locals. #21 0x0000002b44624e76 in main (argc=1, argv=0x2b46525790) at main.c:389 set_roots = {0x2b4482ad60, 0x0} login_set = {auth_socket_path = 0x2b4651d498 "/var/run/dovecot/auth-master", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x2b44624804 <login_client_connected>, failure_callback = 0x2b446244fd <login_client_failed>} service_flags = <optimized out> storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT username = 0x0 c = <optimized out>

2 2

[Dovecot] expire-tool stops on first box with nothing to expire in it
by Michael Wessel 18 Jul '12

18 Jul '12

Hi, I'm running dovecot 1.2.11 on Centos and have the expire plugin enabled. I've had this in place for some time but until now never actually ran the expire-tool. I'm now trying to put this to use. The expire plugin as such is working fine and also the tool is working fine - up to a point. When I run it with --test it goes through a bunch of boxes and lists the messages it would expunge and the new date being logged at the end. As soon as it hits the first box that has nothing in it that's expired however, it stops and goes no further. As an example here are the last two lines of the output when I just ran it: Info: user(a)domain.com/Trash: timestamp 1342320464 (Sat Jul 14 19:47:44 2012) -> 1342937319 (Sat Jul 21 23:08:39 2012) Info: nextuser(a)domain.com/Trash: stop, expire time in future: Sat Jul 14 20:41:49 2012 If I run it again after the indicated expire time it will now also go through the nextuser(a)domain.com but then again stop as soon as it encounters another user with nothing to expire. As far as I can tell the same happens when I actually run the tool. Harder to tell of course as there is no output, but I can tell that not all boxes are expunged as they should be. Any ideas why this would be? Any way to get debug logging on this? Michael

2 2