- dovecot - dovecot.org

[Dovecot] Would attempting plaintext auth repeatably cause a DOS and server to crash?
by Hugh Davenport 21 Jun '13

21 Jun '13

Hey All, I'm just wondering whether this is what caused my server to crash. Started last night in NZ land. Jun 20 19:22:11 elm dovecot: imap-login: Disconnected (tried to use disallowed plaintext auth): user=<>, rip=attackerip, lip=10.0.0.3, session=<0C8LzpDfZQDINsQC> occasionally get Jun 20 19:22:52 elm dovecot: imap-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=attackerip, lip=10.0.0.3, session=<bHdz0JDfpwDINsQC> or in 0 secs last at Jun 20 19:26:24 elm dovecot: imap-login: Disconnected (tried to use disallowed plaintext auth): user=<>, rip=attackerip, lip=10.0.0.3, session=<1MUR3ZDfcwDINsQC> and a minute later the server lost contact to the world. When I checked a bit later, the underlying host machine (dovecot runs on a VM (KVM)) had been powered off. Now, here in NZ land, there was also a crazy storm last night, and lots of brown outs. There could potentially of been a surge that killed it, but the UPS was still running fine when I started it again. The "attack" lasted around 4 minutes, in which there was 1161 lines in the log for a single attacker ip, and no other similar logs previously. Would this be enough to kill not only the VM running dovecot, but the underlying host machine? All up to date with patches, running debian stable (wheezy). dovecot-core debian package version 1:2.1.7-7 dovecot version 2.1.7 I notice there is a version 2.2.3 out, but not in debian yet. Could this fix this issue? I don't particularly want to have it happen again :D. Any thoughts? Cheers, Hugh

3 2

[Dovecot] Allowing clients to test their Sieve scripts
by Frerich Raabe 21 Jun '13

21 Jun '13

Hi, One thing which came up repeatedly is that clients using the IMAP server I run (using Dovecot 2.1) wonder whether they broke their Sieve scripts, i.e. it often goes like "I don't know whether I just didn't receive any mail, or whether my filters broke. Can you check the logs?". I then usually just run the sieve-test binary (part of the Pigeonhole distribution) and send them the output. However, I was wondering - is there maybe a way for them to try it themselves? Like, maybe a tiny web server which just prints a form asking for a mail file and a sieve script, and then it runs sieve-script and prints the output of that? I wonder how other people do that. -- Frerich Raabe - raabe(a)froglogic.com www.froglogic.com - Multi-Platform GUI Testing

9 27

[Dovecot] doveadm move syntax
by vincent truc 20 Jun '13

20 Jun '13

Hello I want to forward an email to user1(a)domain.com box to the box user2(a)domain.com For this I try to use 'doveadm move', but I'm having problems with the syntax. Could you give me an example please? thanks

2 1

[Dovecot] MySQL tables and official documenttation
by Mohsen Pahlevanzadeh 20 Jun '13

20 Jun '13

Dear all, Unfortunately, i created my tables according to the older tutorial, i search in dovecot.org and postfix.org but i didn't find any official documentation for tables. I want to use PF 2.10 and dovecot 2. Its tutorial was wrote on debian etch. eatch is very old. ---mohsen

3 2

[Dovecot] HowTo / VirtualUserFlatFilesPostfix
by treanorv 20 Jun '13

20 Jun '13

The following is an excerpt from the HOWTO mentioned Per-domain authentication and configuration structure /var/vmail dr-x------ 3 doveauth dovecot 4096 2010-03-17 19:09 auth.d |--> domain.tld Can anybody decypher the "|--> domain.tld" part please. Regards, treanorv -- View this message in context: http://dovecot.2317879.n4.nabble.com/HowTo-VirtualUserFlatFilesPostfix-tp42… Sent from the Dovecot mailing list archive at Nabble.com.

2 2

[Dovecot] dovecot enterprise release
by mourik jan SOGo 20 Jun '13

20 Jun '13

Hi all, Not sure if this is the right place to ask, but...: On the dovecot enterprise release pages, only debian 6 compatibility is shown. Are there any plans to support wheezy? (as 7 is stable now, and we are running it...) Regards, Mourik Jan

6 12

[Dovecot] pop3 and imap don't run
by Mohsen Pahlevanzadeh 20 Jun '13

20 Jun '13

Dear all, I run dovecot and when i use 'ps ax |egrep dovecot' command , i get the following result: ////////////////// 9290 pts/3 S+ 0:00 tail -f /var/log/dovecot.err 9597 ? Ss 0:00 /opt/dovecot/sbin/dovecot 9598 ? S 0:00 dovecot/anvil 9599 ? S 0:00 dovecot/log 9601 ? S 0:00 dovecot/config 9606 pts/0 S+ 0:00 egrep --color=auto dovecot /////////////// I dont see any pop or imap process. --mohsen

3 2

[Dovecot] Patch for pigeonhole 0.4.0 avoiding PATH_MAX
by Svante Signell 19 Jun '13

19 Jun '13

Hi, I recently downloaded and built dovecot-2.2.2 and dovecot-2.2-pigeonhole-0.4.0 on GNU/Linux and GNU/Hurd. The changes needed will be sent to the Debian maintainer shortly. Latest Debian release is 2.1.7-7 and dovecot-2.1-pigeonhole-0.3.1. When building dovecot-2.2.2 there were no PATH_MAX problems on GNU/Hurd, thank you for that. However, pigeonhole 0.4.0 had one remaining PATH_MAX construct. The attached patch solves this problem. It it good enough to be accepted upstream? (According to the description of t_malloc, free is not needed, right?) Thanks, Svante Signell

3 4

[Dovecot] A common, read-only IMAP INBOX for all accounts
by Gus 19 Jun '13

19 Jun '13

Hi, since I had no luck finding people available on IRC, I hope someone here can provide me with some answers to, hopefully, 2 simple questions (and have the solution recorded in the archives for everyone with the same need). A little background, as the subject says it - I want to have a single INBOX shared among all the accounts on my system, where only one account would have writing rights, and all the rest would only be able to read the messages. Note this is different than providing a shared mailbox in addition to an INBOX - I actually want the shared INBOX to be the one and only folder that users can see and read as they will not be receiving any personal mails on this system. Naturally, I would also want that each account keeps track of read/unread messages independently of others. So, this is what I came up with (showing the relevant part of configuration only): # Per-user mail root and private/shared INBOX namespace userdb { driver = static args = uid=vmail gid=vmail home=/var/vmail/users/%u } namespace { type = private separator = / prefix = location = maildir:/var/vmail/public:INDEX=~/public inbox = yes } # The ACL contents of /var/vmail/public/dovecot-acl user=admin lrwstipekx anyone lrs Now, this actually results in exactly what I want (apart from a problem I'll describe below), but I'm not sure if it's the right way to do it. So the questions: 1. I have doubts that this solution could cause problems with dot file locking or dovecot data files corruption in the /var/vmail/public mailbox/directory when multiple users access the box simultaneously (and this could be thousands of users in production). Is this a valid concern and have I gone completely wrong with this solution, or there should be no problem with locking and I can keep it this way? If this is not the way to do it, can someone advise on the proper configuration that would achieve the same result, if it's possible at all (or what are the alternatives if it can't be done). 2. For testing purposes, I used a perl script (using the Maildir::Lite module) to create a test message in this mailbox (it gets stored in the new/ subdirectory, as I suppose it should). Now this message shows up as "unread" for all accounts, however when I read it in an IMAP client and then refresh the mailbox, it shows up as unread again. Per-user INDEX directory is writable and I see some files created there by dovecot, so shouldn't they contain the \Seen flags that indicate the message has been read? Is this maybe a client problem and how can I check that dovecot actually saves the flag correctly? The dovecot version I'm using is 2.0.9 (from the CentOS 6.x repositories). Thanks in advance and kind regards, Tin

2 2

[Dovecot] Crashes at login time with freshest code
by interfaSys sàrl 19 Jun '13

19 Jun '13

Hello, Dovecot keeps crashing at login time. Things were fine on 2.2.2 Fatal: master: service(imap): child 5014 killed with signal 11 Here is the trace: Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x00000000105cdfdf in mailbox_list_get_storage (list=0x7fffffffe310, vname=0x10a04ab0 "INBOX/spam", storage_r=0x7fffffffe308) at mailbox-list.c:811 811 if (set != NULL && set->driver[0] != '\0') { (gdb) bt full #0 0x00000000105cdfdf in mailbox_list_get_storage (list=0x7fffffffe310, vname=0x10a04ab0 "INBOX/spam", storage_r=0x7fffffffe308) at mailbox-list.c:811 set = 0x10a89758 #1 0x00000000108c2876 in acl_backend_vfile_get_local_dir (backend=0x10a33a40, name=0x10a04a48 "INBOX/spam") at acl-backend-vfile.c:148 ns = 0x10a5d3c0 list = 0x10a45040 storage = 0xb type = MAILBOX_LIST_PATH_TYPE_DIR dir = 0x10a1a250 "INBOX/spam" inbox = 0x1055dcc0 <static_system_pool> "\200\334U\020" vname = 0x10a04ab0 "INBOX/spam" error = 0x0 __FUNCTION__ = "acl_backend_vfile_get_local_dir" #2 0x00000000108c2a6c in acl_backend_vfile_object_init (_backend=0x10a33a40, name=0x10a04a48 "INBOX/spam") at acl-backend-vfile.c:195 _data_stack_cur_id = 9 backend = 0x10a33a40 aclobj = 0x10a8c380 dir = 0x10a04a68 "\003" vname = 0x10a45258 "\220R\244\020" #3 0x00000000108c05a2 in acl_object_init_from_name (backend=0x10a33a40, name=0x10a04a48 "INBOX/spam") at acl-api.c:15 No locals. #4 0x00000000108ca3d7 in acl_mailbox_list_have_right (list=0x10a45040, name=0x10a04a48 "INBOX/spam", parent=false, acl_storage_right_idx=0, can_see_r=0x0) at acl-mailbox-list.c:63 alist = 0x10a45328 backend = 0x10a33a40 idx_arr = 0x10a453f8 aclobj = 0x1ffffe420 ret = 0 ret2 = 10 #5 0x00000000108cad9c in acl_mailbox_list_info_is_visible (ctx=0x10a11040) at acl-mailbox-list.c:336 info = 0x10a110a8 acl_name = 0x10a04a48 "INBOX/spam" ret = 0 __FUNCTION__ = "acl_mailbox_list_info_is_visible" #6 0x00000000108caf36 in acl_mailbox_list_iter_next (_ctx=0x10a11040) at acl-mailbox-list.c:386 _data_stack_cur_id = 8 ctx = 0x10a11040 info = 0x10a4a0c0 ret = 0 #7 0x00000000105e4394 in mailbox_list_iter_next_call (ctx=0x10a11040) at mailbox-list-iter.c:941 info = 0x10a110a8 set = 0x10a11110 #8 0x00000000105e44ae in autocreate_iter_next (ctx=0x10a11040) at mailbox-list-iter.c:969 actx = 0x10a11110 info = 0x7fffffffe510 autoboxes = 0x10a45040 autobox = 0x7fffffffe530 count = 4096 __FUNCTION__ = "autocreate_iter_next" #9 0x00000000105e466c in mailbox_list_iter_next (ctx=0x10a11040) at mailbox-list-iter.c:1010 _data_stack_cur_id = 7 info = 0x10a11118 #10 0x00000000108cacd3 in iter_mailbox_has_visible_children (ctx=0x10a10840, only_nonpatterns=false) at acl-mailbox-list.c:299 iter = 0x10a11040 info = 0x10a11118 pattern = 0x10a047c8 prefix = 0x10a04800 "INBOX/*" i = 5 prefix_len = 6 stars = false ret = true __FUNCTION__ = "iter_mailbox_has_visible_children" #11 0x00000000108cade9 in acl_mailbox_list_info_is_visible (ctx=0x10a10840) at acl-mailbox-list.c:345 info = 0x10a108a8 acl_name = 0x10a047a0 "INBOX" ret = 1 __FUNCTION__ = "acl_mailbox_list_info_is_visible" #12 0x00000000108caf36 in acl_mailbox_list_iter_next (_ctx=0x10a10840) at acl-mailbox-list.c:386 _data_stack_cur_id = 6 ctx = 0x10a10840 info = 0x10a490c0 ret = 0 #13 0x00000000105e4394 in mailbox_list_iter_next_call (ctx=0x10a10840) at mailbox-list-iter.c:941 info = 0x0 set = 0x0 #14 0x00000000105e44ae in autocreate_iter_next (ctx=0x10a10840) at mailbox-list-iter.c:969 actx = 0x10a10910 info = 0x7fffffffe6b0 autoboxes = 0x2 autobox = 0x10a9b000 count = 0 __FUNCTION__ = "autocreate_iter_next" #15 0x00000000105e466c in mailbox_list_iter_next (ctx=0x10a10840) at mailbox-list-iter.c:1010 _data_stack_cur_id = 5 info = 0x10a1b780 #16 0x00000000105e343b in mailbox_list_ns_iter_try_next (_ctx=0x10a10440, info_r=0x7fffffffe768) at mailbox-list-iter.c:580 ctx = 0x10a10440 ns = 0x1050912c <o_stream_get_buffer_used_size+41> info = 0x10a1b808 error = MAIL_ERROR_NONE errstr = 0x10a47840 "" has_children = false __FUNCTION__ = "mailbox_list_ns_iter_try_next" #17 0x00000000105e36fc in mailbox_list_ns_iter_next (_ctx=0x10a10440) at mailbox-list-iter.c:645 info = 0x0 #18 0x00000000105e4394 in mailbox_list_iter_next_call (ctx=0x10a10440) at mailbox-list-iter.c:941 ---Type <return> to continue, or q <return> to quit--- info = 0x417e06 <client_send_line_next+159> set = 0x7fffffffe7d0 #19 0x00000000105e467e in mailbox_list_iter_next (ctx=0x10a10440) at mailbox-list-iter.c:1012 _data_stack_cur_id = 4 info = 0x2 #20 0x000000000041039c in cmd_list_continue (cmd=0x10a47840) at cmd-list.c:229 ctx = 0x10a47938 info = 0x10a10918 flags = (MAILBOX_NOCHILDREN | MAILBOX_SELECT) str = 0x10a04548 mutf7_name = 0x10a04698 name = 0x10a10c40 "INBOX" ret = 1 #21 0x0000000000410c2c in cmd_list_full (cmd=0x10a47840, lsub=false) at cmd-list.c:463 client = 0x10a47040 args = 0x10a100d8 list_args = 0x104e15a0 <buffer_write+90> arg_count = 32767 ctx = 0x10a47938 patterns = {arr = {buffer = 0x10a47978, element_size = 8}, v = 0x10a47978, v_modifiable = 0x10a47978} ref = 0x10a47968 "" pattern = 0x10a47970 "*" patterns_strarr = 0x10a479b0 str = 0x10a04268 #22 0x0000000000410c81 in cmd_list (cmd=0x10a47840) at cmd-list.c:478 No locals. #23 0x0000000000419e11 in command_exec (cmd=0x10a47840) at imap-commands.c:156 hook = 0x10a22100 ret = false #24 0x0000000000418d59 in client_command_input (cmd=0x10a47840) at imap-client.c:775 client = 0x10a47040 command = 0x7fffffffe950 __FUNCTION__ = "client_command_input" #25 0x0000000000419059 in client_command_input (cmd=0x10a47840) at imap-client.c:836 client = 0x10a47040 command = 0x10a277e0 __FUNCTION__ = "client_command_input" #26 0x0000000000419179 in client_handle_next_command (client=0x10a47040, remove_io_r=0x7fffffffe9dd) at imap-client.c:874 No locals. #27 0x00000000004191f9 in client_handle_input (client=0x10a47040) at imap-client.c:886 _data_stack_cur_id = 3 ret = false remove_io = false handled_commands = false __FUNCTION__ = "client_handle_input" #28 0x000000000041938c in client_input (client=0x10a47040) at imap-client.c:928 cmd = 0x10a21178 output = 0x10a92088 bytes = 19 __FUNCTION__ = "client_input" #29 0x00000000104fc976 in io_loop_call_io (io=0x10a8c2c0) at ioloop.c:387 ioloop = 0x10a21040 t_id = 2 #30 0x00000000104fe46f in io_loop_handler_run (ioloop=0x10a21040) at ioloop-kqueue.c:148 ctx = 0x10a190a0 events = 0x10a50000 event = 0x10a50000 tv = {tv_sec = 1799, tv_usec = 999497} ts = {tv_sec = 1799, tv_nsec = 999497000} io = 0x10a8c2c0 events_count = 6 ret = 1 i = 0 __FUNCTION__ = "io_loop_handler_run" #31 0x00000000104fca19 in io_loop_run (ioloop=0x10a21040) at ioloop.c:406 No locals. #32 0x0000000010493800 in master_service_run (service=0x10a1b140, callback=0x425f06 <client_connected>) at master-service.c:560 No locals. #33 0x0000000000426220 in main (argc=1, argv=0x7fffffffebe8) at main.c:400 set_roots = {0x42f680 <imap_setting_parser_info>, 0x0} login_set = {auth_socket_path = 0x10a04038 "p@\240\020", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x425cca <login_client_connected>, failure_callback = 0x425e92 <login_client_failed>, request_auth_token = 1} service_flags = MASTER_SERVICE_FLAG_KEEP_CONFIG_OPEN storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT username = 0x0 c = -1 Cheers, Olivier

3 5