- dovecot - dovecot.org

[Dovecot] dovecot expire doesn't work (?)
by LÉVAI Dániel 31 Oct '08

31 Oct '08

Hi! I'm using dovecot-1.1.5 and trying to make the expire plugin work. What I've configured in dovecot.conf is the following: protocol imap,pop3,lda { mail_plugins = [...] expire } dict { expire = db:/var/dovecot/expire/expire.db } plugin { expire = spamassassin/SPAM 2 spamassassin/HAM 2 expire_dict = proxy::expire } I have a sieve rule, to copy certain messages to my "spamassassin/SPAM" folder. Then I want to expire those messages after 2 days (I think I've configured that under the plugin{} section in dovecot.conf). So the actual message saving is done by the dovecot's deliver, but I have the plugin loaded under the "protocol lda {}" section too. So I thought now I just have to wait 2 days, and run the expire-tool, and then it will expire the messages. Now I have three messages dated back to 10.25, but running the expire-tool outputs nothing. # dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test Nothing in the logfiles, and nothing on the console. I have the /var/dovecot/expire directory: # ls -la /var/dovecot/expire/ total 1640 drwx------ 2 root wheel 512 Oct 26 19:47:53 2008 ./ drwxr-x--- 3 root wheel 512 Oct 27 07:57:42 2008 ../ -rw------- 1 root wheel 24576 Oct 27 13:00:01 2008 __db.001 -rw------- 1 root wheel 57344 Oct 27 13:00:01 2008 __db.002 -rw------- 1 root wheel 270336 Oct 27 13:00:01 2008 __db.003 -rw------- 1 root wheel 98304 Oct 27 13:00:01 2008 __db.004 -rw------- 1 root wheel 49152 Oct 27 13:00:01 2008 __db.005 -rw------- 1 root wheel 32768 Oct 26 19:47:37 2008 expire.db -rw------- 1 root wheel 10485760 Oct 27 14:22:08 2008 log.0000000001 It contains the familiar BDB files, so I think it works, although the expire.db's modify time is yesterday, but deliver saved some messages also today to the spamassassin/SPAM folder. What could be the problem? Am I missing something? Thanks! Daniel -- LEVAI Daniel PGP key ID = 0x4AC0A4B1 Key fingerprint = D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1

3 11

[Dovecot] Problem with Dovecot 1.1.4 and dovecot-antispam 20080829
by Guillaume Hilt 31 Oct '08

31 Oct '08

Hi there, I'm running a server under Gentoo 64 with postfix 2.5.5, Dovecot 1.1.4-r1 and Dovecot-antispam 20080829 (all are the lastest versions availables under Portage). I ran into a problem when I log in to my mailbox : Oct 30 10:39:23 ks29138 dovecot: IMAP(hiltg): Loading modules from directory: /usr/lib64/dovecot/imap Oct 30 10:39:23 ks29138 dovecot: IMAP(hiltg): Module is for different version 1.1.1: /usr/lib64/dovecot/imap/lib90_antispam_plugin.so Oct 30 10:39:23 ks29138 dovecot: Fatal: IMAP(hiltg): Couldn't load required plugins Is there another version for Dovecot 1.1.4 out there or must I go back to 1.1.1 ? Thanks, Guillaume

3 3

[Dovecot] dovecot behind loadbalancers
by Robert Schetterer 31 Oct '08

31 Oct '08

Hi @ll, has anbody experience with dovecot behind load balancers im planning to test ha-proxy pen balance(ng) on ubuntu hardy in a HA-Cluster in front of dovecot servers -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

[Dovecot] Dovecot read only for users
by JC 31 Oct '08

31 Oct '08

All, I have hopefully a base question. How do you give users only read access to their inbox and folders? If I use chmod 600 they have full access. If I do a 400 they have read access but cannot access their inbox. The config file is the out of the box config other than advertising IMAP and IMAPS. Any help will be appreciated. Thanks.

10 20

[Dovecot] Startup info message
by Athan Dimoy 31 Oct '08

31 Oct '08

Hi folks, I'm using the latest Dovecot 1.16 with Postfix for my FreeBSD box. Since v1.1.4 (if i remember correctly), the following message is displayed whenever starting Dovecot. "Info: If you have trouble with authentication failures, enable auth_debug setting. See http://wiki.dovecot.org/WhyDoesItNotWork" Besides that, Dovecot works great but I wonder what this message is all about. I've searched wiki and mailing list but didn't find anything related. PS: I removed Dovecot removing all stalled files and directories and reinstalled it from scratch. Still the message is displayed whenever it starts. Any idea? Athan

4 6

[Dovecot] SIGBART/SIGSEGV while SELECTing virtual folder
by Lars Noschinski 30 Oct '08

30 Oct '08

Hello! I just installed Dovecot's latest nightly build (20081020) and tried the virtual folder features. I started with a really simple "all" folder: | # virtual/all | * | all But selecting this folder causes dovecot to panic (in most cases). While trying to debug this, I got slightly different results and I am not really sure yet if this is just non-deterministic, depends on some cached dovecot data or if there is some difference between the debug build or my rudimentary, unpatched debian package (which lacks the debug symbols). The results below are from a build with --prefix set to a clean, temporary directory. Similar problems occured also with the alpha2 release, which caused me to try the latest nightly build. --------------------------------------------------------------------- % ./sbin/dovecot --exec-mail ext /usr/bin/gdb ./libexec/dovecot/imap GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) r Starting program: /tmp/dd/libexec/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTE NDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH SEARCHRES WITHIN CONTEXT=SEARCH] Logg ed in as lars . SELECT virtual/all Program received signal SIGSEGV, Segmentation fault. mailbox_search_result_free (_result=0x8efc0d0) at mailbox-search-result.c:65 65 results = array_get(&result->box->search_results, &count); (gdb) bt full #0 mailbox_search_result_free (_result=0x8efc0d0) at mailbox-search-result.c:65 result = (struct mail_search_result *) 0x0 i = <value optimized out> __PRETTY_FUNCTION__ = "mailbox_search_result_free" #1 0xb7f4e12e in virtual_storage_mailbox_close (box=0x8efbeb0) at virtual-storage.c:311 i = 0 ret = 0 #2 0x080a9299 in mail_thread_mailbox_close (box=0x8efbeb0) at index-thread.c:638 tbox = (struct mail_thread_mailbox *) 0x9517c68 ret = <value optimized out> __PRETTY_FUNCTION__ = "mail_thread_mailbox_close" #3 0x0806486a in cmd_select_finish (ctx=0x8ef3778, ret=0) at cmd-select.c:190 No locals. #4 0x08064a89 in cmd_select_full (cmd=0x8ef3730, readonly=false) at cmd-select.c:381 client = (struct client *) 0x8ef34b0 box = (struct mailbox *) 0xbfb78258 ctx = (struct imap_select_context *) 0x8ef3778 args = (const struct imap_arg *) 0x8ef87b0 mailbox = 0x8ef8838 "all" ret = 0 __PRETTY_FUNCTION__ = "cmd_select_full" #5 0x080653d9 in cmd_select (cmd=0x8ef3730) at cmd-select.c:387 No locals. #6 0x0806755c in client_command_input (cmd=0x8ef3730) at client.c:592 client = (struct client *) 0x8ef34b0 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #7 0x080675f9 in client_command_input (cmd=0x8ef3730) at client.c:641 client = (struct client *) 0x8ef34b0 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #8 0x08067bfd in client_handle_input (client=0x8ef34b0) at client.c:682 _data_stack_cur_id = 3 ret = <value optimized out> remove_io = <value optimized out> handled_commands = false #9 0x080680b3 in client_input (client=0x8ef34b0) at client.c:737 cmd = <value optimized out> output = (struct ostream *) 0x8ef365c bytes = <value optimized out> __PRETTY_FUNCTION__ = "client_input" #10 0x080f3210 in io_loop_handler_run (ioloop=0x8eefab8) at ioloop-epoll.c:203 ctx = (struct ioloop_handler_context *) 0x8eefbb0 event = (const struct epoll_event *) 0x8eefbf0 list = (struct io_list *) 0x8ef36d8 io = (struct io_file *) 0x8ef36b8 tv = {tv_sec = 1799, tv_usec = 999384} t_id = 2 msecs = <value optimized out> ret = 1 i = 0 j = 0 call = <value optimized out> #11 0x080f26a0 in io_loop_run (ioloop=0x8eefab8) at ioloop.c:320 No locals. #12 0x0806f54d in main (argc=149943736, argv=0xbfb78484, envp=0xbfb7848c) at main.c:309 No locals. --------------------------------------------------------------------- On another folder with the same dovecot-virtual file, I get another backtrace: --------------------------------------------------------------------- % ./sbin/dovecot --exec-mail ext /usr/bin/gdb ./libexec/dovecot/imap GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) r Starting program: /tmp/dd/libexec/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH SEARCHRES WITHIN CONTEXT=SEARCH] Logged in as lars . SELECT "virtual/test" Program received signal SIGABRT, Aborted. 0xb7e83556 in raise () from /lib/libc.so.6 (gdb) bt #0 0xb7e83556 in raise () from /lib/libc.so.6 #1 0xb7e84d78 in abort () from /lib/libc.so.6 #2 0x080ead25 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:150 #3 0x080eade4 in i_syslog_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80ffdec "file %s: line %d (%s): assertion failed: (%s)", args=0xbfdce064 "\203�020\b\t\001") at failures.c:308 #4 0x080ea729 in i_panic ( format=0x80ffdec "file %s: line %d (%s): assertion failed: (%s)") at failures.c:197 #5 0x080c86b8 in view_lookup_seq_range (view=0x9956648, first_uid=1, last_uid=0, first_seq_r=0xbfdce294, last_seq_r=0xbfdce290) at mail-index-view.c:265 #6 0x080c815c in mail_index_lookup_seq_range (view=0x9956648, first_uid=1, last_uid=0, first_seq_r=0xbfdce294, last_seq_r=0xbfdce290) at mail-index-view.c:530 #7 0xb7fa64d6 in virtual_sync_backend_boxes (ctx=0x9e2e3e0) at virtual-sync.c:561 #8 0xb7fa738f in virtual_storage_sync_init (box=0x9811eb0, flags=65) at virtual-sync.c:1194 #9 0x080b0240 in mailbox_sync (box=0x578d, flags=65, status_items=239, status_r=0xbfdce438) at mail-storage.c:523 #10 0x08064c70 in cmd_select_full (cmd=0x9809730, readonly=false) at cmd-select.c:273 #11 0x080653d9 in cmd_select (cmd=0x9809730) at cmd-select.c:387 #12 0x0806755c in client_command_input (cmd=0x9809730) at client.c:592 #13 0x080675f9 in client_command_input (cmd=0x9809730) at client.c:641 #14 0x08067bfd in client_handle_input (client=0x98094b0) at client.c:682 #15 0x080680b3 in client_input (client=0x98094b0) at client.c:737 #16 0x080f3210 in io_loop_handler_run (ioloop=0x9805ab8) at ioloop-epoll.c:203 #17 0x080f26a0 in io_loop_run (ioloop=0x9805ab8) at ioloop.c:320 #18 0x0806f54d in main (argc=Cannot access memory at address 0x578d ) at main.c:309 --------------------------------------------------------------------- with log message -------------------------------------------------------------------- -Oct 20 15:29:22 vertikal EXT(lars): : Panic: file mail-index-view.c: line 265 (view_lookup_seq_range): assertion failed: (first_uid <= last_uid) Oct 20 15:29:22 vertikal EXT(lars): : Raw backtrace: /tmp/dd/libexec/dovecot/imap [0x80ead11] -> /tmp/dd/libexec/dovecot/imap(i_syslog_fatal_handler+0x34) [0x80eade4] -> /tmp/dd/libexec/dovecot/imap [0x80ea729] -> /tmp/dd/libexec/dovecot/imap [0x80c86b8] -> /tmp/dd/libexec/dovecot/imap(mail_index_lookup_seq_range+0x2c) [0x80c815c] -> /tmp/dd/lib/dovecot/imap/lib20_virtual_plugin.so [0xb7fa64d6] -> /tmp/dd/lib/dovecot/imap/lib20_virtual_plugin.so(virtual_storage_sync_init+0x53f) [0xb7fa738f] -> /tmp/dd/libexec/dovecot/imap(mailbox_sync+0x30) [0x80b0240] -> /tmp/dd/libexec/dovecot/imap(cmd_select_full+0x3d0) [0x8064c70] -> /tmp/dd/libexec/dovecot/imap(cmd_select+0x19) [0x80653d9] -> /tmp/dd/libexec/dovecot/imap [0x806755c] -> /tmp/dd/libexec/dovecot/imap [0x80675f9] -> /tmp/dd/libexec/dovecot/imap(client_handle_input+0x1d) [0x8067bfd] -> /tmp/dd/libexec/dovecot/imap(client_input+0x63) [0x80680b3] -> /tmp/dd/libexec/dovecot/imap(io_loop_handler_run+0xe0) [0x80f3210] -> /tmp/dd/libexec/dovecot/imap(io_loop_run+0x20) --------------------------------------------------------------------- Given that result, I tried adding yet another virtual folder with the same configuration - and it succeeded. Once. A second SELECT gave me yet another backtrace: --------------------------------------------------------------------- % ./sbin/dovecot --exec-mail ext /usr/bin/gdb ./libexec/dovecot/imap GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) r Starting program: /tmp/dd/libexec/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH SEARCHRES WITHIN CONTEXT=SEARCH] Logged in as lars . SELECT virtual/test2 * FLAGS (\Answered \Flagged \Deleted \Seen \Draft Old) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft Old \*)] Flags permitted. * 73863 EXISTS * 0 RECENT * OK [UNSEEN 10841] First unseen. * OK [UIDVALIDITY 1224509528] UIDs valid * OK [UIDNEXT 73864] Predicted next UID * OK [HIGHESTMODSEQ 1] . OK [READ-WRITE] Select completed. . SELECT virtual/test2 Program received signal SIGABRT, Aborted. 0xb7e0f556 in raise () from /lib/libc.so.6 (gdb) bt full #0 0xb7e0f556 in raise () from /lib/libc.so.6 No symbol table info available. #1 0xb7e10d78 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x080ead25 in default_fatal_finish (type=<value optimized out>, status=0) at failures.c:150 backtrace = 0x8b27838 "/tmp/dd/libexec/dovecot/imap [0x80ead11] -> /tmp/dd/libexec/dovecot/imap(i_syslog_fatal_handler+0x34) [0x80eade4] -> /tmp/dd/libexec/dovecot/imap [0x80ea729] -> /tmp/dd/libexec/dovecot/imap [0x80c86b8"... #3 0x080eade4 in i_syslog_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x80ffdec "file %s: line %d (%s): assertion failed: (%s)", args=0xbfc57ef4 "\203�020\b\t\001") at failures.c:308 No locals. #4 0x080ea729 in i_panic ( format=0x80ffdec "file %s: line %d (%s): assertion failed: (%s)") at failures.c:197 No locals. #5 0x080c86b8 in view_lookup_seq_range (view=0x8eb77e0, first_uid=1, last_uid=0, first_seq_r=0xbfc58124, last_seq_r=0xbfc58120) at mail-index-view.c:265 __PRETTY_FUNCTION__ = "view_lookup_seq_range" #6 0x080c815c in mail_index_lookup_seq_range (view=0x8eb77e0, first_uid=1, last_uid=0, first_seq_r=0xbfc58124, last_seq_r=0xbfc58120) at mail-index-view.c:530 No locals. #7 0xb7f324d6 in virtual_sync_backend_boxes (ctx=0x90f8eb8) at virtual-sync.c:561 i = 10 #8 0xb7f3338f in virtual_storage_sync_init (box=0x8eba5d0, flags=65) at virtual-sync.c:1194 ret = <value optimized out> #9 0x080b0240 in mailbox_sync (box=0x57a2, flags=65, status_items=239, status_r=0xbfc582c8) at mail-storage.c:523 ctx = (struct mailbox_sync_context *) 0x0 #10 0x08064c70 in cmd_select_full (cmd=0x8b32730, readonly=false) at cmd-select.c:273 client = (struct client *) 0x8b324b0 box = (struct mailbox *) 0x0 ctx = (struct imap_select_context *) 0x8b32778 args = (const struct imap_arg *) 0x8b377b0 mailbox = 0x8b37838 "test2" ret = <value optimized out> __PRETTY_FUNCTION__ = "cmd_select_full" #11 0x080653d9 in cmd_select (cmd=0x8b32730) at cmd-select.c:387 No locals. #12 0x0806755c in client_command_input (cmd=0x8b32730) at client.c:592 client = (struct client *) 0x8b324b0 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #13 0x080675f9 in client_command_input (cmd=0x8b32730) at client.c:641 client = (struct client *) 0x8b324b0 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #14 0x08067bfd in client_handle_input (client=0x8b324b0) at client.c:682 _data_stack_cur_id = 3 ret = <value optimized out> remove_io = <value optimized out> handled_commands = false #15 0x080680b3 in client_input (client=0x8b324b0) at client.c:737 cmd = <value optimized out> output = (struct ostream *) 0x8b3265c bytes = <value optimized out> __PRETTY_FUNCTION__ = "client_input" #16 0x080f3210 in io_loop_handler_run (ioloop=0x8b2eab8) at ioloop-epoll.c:203 ctx = (struct ioloop_handler_context *) 0x8b2ebb0 event = (const struct epoll_event *) 0x8b2ebf0 list = (struct io_list *) 0x8b326d8 io = (struct io_file *) 0x8b326b8 tv = {tv_sec = 1799, tv_usec = 995613} t_id = 2 msecs = <value optimized out> ret = 1 i = 0 j = 0 call = <value optimized out> #17 0x080f26a0 in io_loop_run (ioloop=0x8b2eab8) at ioloop.c:320 No locals. #18 0x0806f54d in main (argc=Cannot access memory at address 0x57a2 ) at main.c:309 No locals. --------------------------------------------------------------------- Oct 20 15:33:31 vertikal EXT(lars): : Panic: file mail-index-view.c: line 265 (view_lookup_seq_range): assertion failed: (first_uid <= last_uid) Oct 20 15:33:31 vertikal EXT(lars): : Raw backtrace: /tmp/dd/libexec/dovecot/imap [0x80ead11] -> /tmp/dd/libexec/dovecot/imap(i_syslog_fatal_handler+0x34) [0x80eade4] -> /tmp/dd/libexec/dovecot/imap [0x80ea729] -> /tmp/dd/libexec/dovecot/imap [0x80c86b8] -> /tmp/dd/libexec/dovecot/imap(mail_index_lookup_seq_range+0x2c) [0x80c815c] -> /tmp/dd/lib/dovecot/imap/lib20_virtual_plugin.so [0xb7f324d6] -> /tmp/dd/lib/dovecot/imap/lib20_virtual_plugin.so(virtual_storage_sync_init+0x53f) [0xb7f3338f] -> /tmp/dd/libexec/dovecot/imap(mailbox_sync+0x30) [0x80b0240] -> /tmp/dd/libexec/dovecot/imap(cmd_select_full+0x3d0) [0x8064c70] -> /tmp/dd/libexec/dovecot/imap(cmd_select+0x19) [0x80653d9] -> /tmp/dd/libexec/dovecot/imap [0x806755c] -> /tmp/dd/libexec/dovecot/imap [0x80675f9] -> /tmp/dd/libexec/dovecot/imap(client_handle_input+0x1d) [0x8067bfd] -> /tmp/dd/libexec/dovecot/imap(client_input+0x63) [0x80680b3] -> /tmp/dd/libexec/dovecot/imap(io_loop_handler_run+0xe0) [0x80f3210] -> /tmp/dd/libexec/dovecot/imap(io_loop_run+0x20) --------------------------------------------------------------------- Configuration was: --------------------------------------------------------------------- % ./sbin/dovecot -n # 1.2.alpha2: /tmp/dd/etc/dovecot.conf listen: 127.0.0.1 ssl_disable: yes login_dir: /tmp/dd/var/run/dovecot/login login_executable: /tmp/dd/libexec/dovecot/imap-login mail_plugins: fts fts_squat virtual zlib namespace: type: private separator: / location: maildir:~/Mailbox/Maildir inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: mbox/ location: mbox:~/Mailbox/mbox/ list: yes subscriptions: yes namespace: type: private separator: / prefix: virtual/ location: virtual:~/Mailbox/virtual list: yes subscriptions: yes auth default: passdb: driver: pam userdb: driver: passwd --------------------------------------------------------------------- System is Linux/i386. I tried narrowing down the problem to a specific mail folder, but did not succeed, it seems I need to give a number of folders for this problem to occur. The SIGABRT kind of crash occured a lot more often. On an unrelated note, given the above configuration file, using a dovecot-virtual file like | mbox/* | all causes dovecot to complain: Oct 20 13:56:59 vertikal EXT(lars): : Connection closed bytes=22/350 Oct 20 13:57:03 vertikal EXT(lars): : /home/lars/Mailbox/virtual/test/dovecot-virtual: No mailboxes defined Greetings, Lars.

2 9

[Dovecot] dovecot 1.1.5 mbox bug (From_-line separator related)
by Anton Yuzhaninov 30 Oct '08

30 Oct '08

If I send mail with content like this: From <test.dovecot(a)m.box> Wed Jan 09 01:33:55 2008 From <test.dovecot(a)m.box> Wed Jan 09 01:33:55 2008 From <test.dovecot(a)m.box> Wed Jan 09 01:33:55 2008 From <test.dovecot(a)m.box> Wed Jan 09 01:33:55 2008 and instead single messages created many messages. Inside mbox file it looks like real_message_headers Status: O X-Keywords: Content-Length: 2859 X-UID: 1471 From <test.dovecot(a)m.box> Wed Jan 09 01:33:55 2008 X-UID: 1472 Status: O From <test.dovecot(a)m.box> Wed Jan 09 01:33:55 2008 X-UID: 1473 Status: O From <test.dovecot(a)m.box> Wed Jan 09 01:33:55 2008 X-UID: 1474 Status: O Yes, Content-Length headers present, but: 1. Why X-UID: and Status: headers inserted into message body? 2. Why IMAP client (thunderbird) show many empty messages instead single message? Mbox related settings from dovecot -n is only: mmap_disable: yes mbox_write_locks: fcntl mbox_min_index_size: 1024 To store messages used dovecot deliver. -- WBR, Anton Yuzhaninov

2 4

[Dovecot] mail_executable's process environment
by Mike Malsman 30 Oct '08

30 Oct '08

Hello, I recently had to get Dovecot 1.1.4 to write to a "pop3/imap-before- smtp" db such that my MTA could permit relay after a successful authentication with Dovecot. The 'pop3' and 'imap' processes are executed only after a successful auth, so replacing them with wrappers which write to the db seemed the natural choice. Lo and behold, someone thought of something like this, as the 'mail_executable' directive exists - neat. Upon inspection of the processes' environment I'm pleased to see that there's a load of useful information in there. However, one essential component in my case is the destination network address, which is missing. I added it with the attached patch, exposed as 'LOCAL_IP'. Works for me. Is this something that would be useful to anyone else? -Mike

3 4

[Dovecot] [dovecot] Enable logging of all client commands in dovecot-1.2.alpha3
by Jonathan Siegle 30 Oct '08

30 Oct '08

Hello, I would like to log all IMAP client commands sent to dovecot. The format would be time pid command arguments. I reviewed http://wiki.dovecot.org/Logging and started digging through dovecot-1.2.alpha3/src/master . I don't need this turned on all the time, just enough to see how clients do things and I don't need to see passwords. Any tips would be appreciated. -Jonathan

2 1

[Dovecot] benchmark dovecot
by Mathieu Kretchner 30 Oct '08

30 Oct '08

Hello, We would like to do a feed back to this active mailing list. We are working on a migration project from cyrus to dovecot. And we have just completed the benchmark sequence. As I say, this benchmark is here only to show that our old imap server is out to date. I would not be the source of controversy at all, so I try to explain my approach. Because the only thing I found was this old oriented benchmark : http://www.isode.com/whitepapers/mbox-benchmark.html We've tried to do our tests, here you could find our results : http://www-sop.inria.fr/members/Mathieu.Kretchner/dotclear/index.php/2008/1…

2 4

[Dovecot] Enh-Req: Mark As Read When Delivered
by Neil 30 Oct '08

30 Oct '08

I'm under the impression bug-reports are supposed to go to the list, so hopefully it's okay if I put in a feature request here too (assuming it's not already implemented; but it doesn't look like it). Basically, all I would like to do is be able to sometimes deliver mail as already mail into mail boxes. Is there some way to do this? If not, could a flag perhaps be added to deliver to do it? (And Sieve; but for now I think procmail still has much higher adoption, and thus having it in deliver would be rather key...) Thanks, -Neil.

2 1

[Dovecot] INBOX stored in AFS
by Hans-Werner Paulsen 30 Oct '08

30 Oct '08

Hello, currently we are storing the incoming mail in the user's home directory, which is within a distributed filesystem called AFS (OpenAFS). Accessing the "mbox" file directly (using the distributed filesystem) works fine with mutt, thunderbird, ... To access the INBOX from a machine, which does not have access to this distributed filesystem, we are using IMAP (UW-imap). Now I wanted to check if dovecot can do the job (maybe faster than UW), and I had the following problem: This is my configuration: ------------------------------------------------------------------------------- # 1.1.4: /opt/dovecot-1.1.4/etc/dovecot.conf log_path: /var/log/dovecot ssl_cert_file: /etc/ssl/certs/imapd.pem ssl_key_file: /etc/ssl/keys/imapd.pem login_dir: /var/run/dovecot/login login_executable: /opt/dovecot-1.1.4/libexec/dovecot/imap-login first_valid_uid: 100 mail_location: mbox:~/Mail:INBOX=~/.maildir/incoming mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mbox_write_locks: fcntl mbox_dirty_syncs: no mbox_lazy_writes: no mail_executable: /opt/dovecot-1.1.4/libexec/dovecot/afs-token /opt/dovecot-1.1.4/libexec/dovecot/imap auth default: verbose: yes debug: yes passdb: driver: pam args: setcred=yes session=yes dovecot userdb: driver: passwd ------------------------------------------------------------------------------- When I start my imap-client, I see the content of the INBOX, and I can read, delete, ... the different entries. But when new mail arrives dovecot (and my imap-client) will never notice this. And when I quit my imap-client the dovecot imap server will write back its view of the INBOX, and delete this new mail. This seems to be a problem related to AFS. I poked in the dovecot code and have the following theory: dovecot opens the INBOX R/W, dovecot calls "stat" on the INBOX file periodically to look for modifications. But this does not work, because this machine will stat the local copy (AFS cache) of the INBOX as long as this file is still open R/W. My questions: Is it possible to have a configuration, that the INBOX file is not left open when stat-ing this file? Or is it possible to open the INBOX file R/W only when it us locked? Or is it necessary to modify the code? Thank you for any help, HW -- Hans-Werner Paulsen hans(a)MPA-Garching.MPG.DE MPI für Astrophysik Tel 089-30000-2602 Karl-Schwarzschild-Str. 1 Fax 089-30000-2235 D-85741 Garching

2 2

[Dovecot] read only FS access
by Mathieu Kretchner 30 Oct '08

30 Oct '08

Hello, I would like to know if it's possible to subscribe to a folder that is on a read only File System ? We have a snapshot mechanism that create a .snapshot directly in the user folder. This is done by our NAS and we would like to give an access to this backup to our users. Thanks.

3 7

[Dovecot] dovecot deliver mail bounce problem
by Dhaval Thakar 30 Oct '08

30 Oct '08

Hi list, I am using dovecot deliver for the local mail delivery with qmail. this is working fine. but when mail is sent to invalid user, it gets bounced back with error "I'm not going to try again; this message has been in the queue too long." rather "no mailbox here by that name" I could find proper solution, kindly guide to resolve it. /var/log/maillog Oct 24 23:03:27 backup dovecot: auth(default): master in: USER 1 d(a)arch.xyz.com service=deliver Oct 24 23:03:27 backup dovecot: auth(default): vpopmail(d(a)arch.xyz.com): lookup user=d domain=arch.xyz.com Oct 24 23:03:27 backup dovecot: auth(default): vpopmail(d(a)arch.xyz.com): unknown user Oct 24 23:03:27 backup dovecot: auth(default): prefetch(d(a)arch.xyz.com): passdb didn't return userdb entries, trying the next userdb Oct 24 23:03:27 backup dovecot: auth(default): master out: NOTFOUND 1 no logs in /var/log/dovecot-deliver.log following is the configuration .qmail-default |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -n -e -d $EXT@$USER dovecot -n # 1.1.5: /etc/dovecot/dovecot.conf protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting: mail ready. mail_plugins: quota imap_quota trash imap_client_workarounds: delay-newmail outlook-idle namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: checkpassword args: /home/vpopmail/bin/vchkpw userdb: driver: vpopmail userdb: driver: prefetch socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vpopmail group: vchkpw plugin: quota: maildir quota_rule: Trash:ignore

4 3

Re: [Dovecot] First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
by seriv＠parkheights.dyndns.org 30 Oct '08

30 Oct '08

Thank you Timo, it was my mistake. In 'plugin {}' section line 'sieve = /var/sievescripts/%n/sieve' worked for both cmusieve and sieve plugins. Command 'fileinto "INBOX/foo/bar"' with private namespace configuration you proposed - also worked in both plugins. I suspected that they have different behavior: cmusieve saved message into INBOX/foo/bar, while sieve - into foo/bar as in the deliver log I'm pasting here. But both messages were filed into the same mail folder. Difference in the logging, I think, is not a big problem. --- ls -l Maildir/.foo.bar/new total 8 -rw------- 1 seriv seriv 513 Oct 30 01:57 1225331850.M790093P1351.sisyphus.office.omniti.com,W=526 -rw------- 1 seriv seriv 518 Oct 30 01:59 1225331966.M468658P1400.sisyphus.office.omniti.com,W=531 tail -n 18 /var/log/deliver/dovecot-deliver.log --- deliver(seriv): Oct 30 01:57:30 Info: Loading modules from directory: /usr/lib64/dovecot/modules/lda/ deliver(seriv): Oct 30 01:57:30 Info: Module loaded: /usr/lib64/dovecot/modules/lda//lib90_cmusieve_plugin.so deliver(seriv): Oct 30 01:57:30 Info: Namespace: type=private, prefix=INBOX/, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes deliver(seriv): Oct 30 01:57:30 Info: maildir: root exists (/home/seriv/Maildir) deliver(seriv): Oct 30 01:57:30 Info: maildir++: root=/home/seriv/Maildir, index=, control=, inbox=/home/seriv/Maildir deliver(seriv): Oct 30 01:57:30 Info: cmusieve: Using sieve path: /var/sieve-scripts/seriv.sieve deliver(seriv): Oct 30 01:57:30 Info: cmusieve: Executing script /var/sieve-scripts/seriv.sievec deliver(seriv): Oct 30 01:57:30 Info: Namespace INBOX/: Using permissions from /home/seriv/Maildir: mode=0644 gid=-1 deliver(seriv): Oct 30 01:57:30 Info: msgid=<20081030015649.B7936140A88(a)sisyphus.office.omniti.com>: saved mail to INBOX/foo/bar deliver(seriv): Oct 30 01:59:26 Info: Loading modules from directory: /usr/lib64/dovecot/modules/lda/ deliver(seriv): Oct 30 01:59:26 Info: Module loaded: /usr/lib64/dovecot/modules/lda//lib90_sieve_plugin.so deliver(seriv): Oct 30 01:59:26 Info: Namespace: type=private, prefix=INBOX/, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes deliver(seriv): Oct 30 01:59:26 Info: maildir: root exists (/home/seriv/Maildir) deliver(seriv): Oct 30 01:59:26 Info: maildir++: root=/home/seriv/Maildir, index=, control=, inbox=/home/seriv/Maildir deliver(seriv): Oct 30 01:59:26 Info: sieve: using sieve path: /var/sieve-scripts/seriv.sieve deliver(seriv): Oct 30 01:59:26 Info: sieve: opening script /var/sieve-scripts/seriv.sieve deliver(seriv): Oct 30 01:59:26 Info: sieve: executing compiled script /var/sieve-scripts/seriv.sieve deliver(seriv): Oct 30 01:59:26 Info: sieve: msgid=<20081030015911.576FC140A88(a)sisyphus.office.omniti.com>: stored mail into mailbox 'foo/bar' -- WBR, Sergey Ivanov. ----- "Timo Sirainen" <tss(a)iki.fi> wrote: > On Wed, 2008-10-29 at 20:31 +0100, Stephan Bosch wrote: > > sergey ivanov schreef: > > > Hi Stephan, > > > Thank you for quick fix. I've built it (from changeset > > > 646:747107b816dc) and it looks like working with dovecot-1.2. > > > I'm doing some testing before put it into Sisyphus repository > > > (http://en.altlinux.org) > > > What I saw - it does not recognize lines like: > > > --- > > > sieve = /var/sievescripts/%n/sieve > > Is this inside protocol lda {} or plugin {}? In former it's not > supposed > to be expanded (shouldn't have been with cmusieve either), in latter > it > should be. > > > > where cmusieve did > > > --- > > > fileinto fileinto "Inbox/R/Commits"; > > > --- > > > this new plugin require changing slashes to dots: > > > --- > > > fileinto fileinto "Inbox.R.Commits"; > > With a namespace configuration like: > > namespace private { > separator = / > prefix = INBOX/ > inbox = yes > } > > And a script: > > require ["fileinto"]; > fileinto "INBOX/foo/bar"; > > It seems to work just fine: > > deliver(tss): Oct 30 00:04:36 Info: sieve: msgid=unspecified: stored > mail into mailbox 'foo.bar' > > Although it probably should use the full untranslated INBOX/foo/bar > name > when logging (same with deliver -m INBOX/foo/bar).

1 0

Re: [Dovecot] First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
by Stephan Bosch 30 Oct '08

30 Oct '08

sergey ivanov schreef: > Hi Stephan, > Thank you for quick fix. I've built it (from changeset > 646:747107b816dc) and it looks like working with dovecot-1.2. > I'm doing some testing before put it into Sisyphus repository > (http://en.altlinux.org) > What I saw - it does not recognize lines like: > --- > sieve = /var/sievescripts/%n/sieve > --- > as cmusieve did. But it works ok with default .dovecot.sieve files in > user home directories Hmm, I'll look into that. This is not intended and would be a bug. > Then, it reports > --- > error: failed to store into mailbox 'Inbox/R/Commits': Invalid mailbox name. > --- > where cmusieve did > --- > fileinto fileinto "Inbox/R/Commits"; > --- > this new plugin require changing slashes to dots: > --- > fileinto fileinto "Inbox.R.Commits"; This doesn't look like something that has changed for the Sieve implementation specifically. Did you try dovecot-sieve-1.1 with dovecot 1.2 to verify? I'll ask Timo about this. What is the configuration of your mail store. Did you perhaps migrate from mbox to maildir? > I think this changes should be described somewhere. May be, it's > already needed to create wiki page for libsieve at wiki.dovecot.org? Well, first one is probably a bug. The second one I am not sure about yet. I'll get back to you when I do. PS: please reply to the mailing list as well. Your problems and solutions may interest others as well. Regards, -- Stephan Bosch stephan(a)rename-it.nl

4 4

[Dovecot] FTS index generation
by Dave McGuire 30 Oct '08

30 Oct '08

Hi folks. I'm experimenting with the Squat plugin. I can execute search commands via direct interaction with IMAP, but I never see the expected dovecot.index.search index file appear in the spool. I'm concerned that I've misconfigured something that is preventing the creation of those indices. Is there a facility to have the squat plugin generate debugging messages so I can see what it's doing? Thanks, -Dave -- Dave McGuire Ahh, you voted for Bush? Port Charlotte, FL Happy now?

2 3

[Dovecot] Embedded "From<space>" Lines
by Lennart Lövstrand 29 Oct '08

29 Oct '08

Hi. As some of you may remember, I reported a problem a while back where dovecot 1.1.beta14 (as well as dovecot 1.0) would corrupt mbox-style mailboxes by ignoring the Content-Length header and breaking up messages with embededed "From<space>" lines. I recently downloaded Dovecot 1.1.5 and noted to my pleasure that this bug now has been fixed. That's great! This fix envolves checking to see if the expected_body_size (from the Content-Length header) is larger than the body_size produced by the "From<space>" scanner, and if so, if there is a valid "From<space>" line at the "expected" end of the message. However, I also noted that there's a case which the fix doesn't cover, and that's where the "From<space>" line appears as the first line of the body of the message. When this happens, the body_offset will point to the blank line between the headers and the body and not the actual first line of the body. This will cause the stream to be mispositioned at the time of the "From<space>" verification check in istream_raw_mbox_get_body_size and the (actually correct) expected_body_size will be rejected. I have enclosed a simple diff that will work around this by adjusting the body_offset to point to the next line at the time of call to istream_raw_mbox_is_valid_from in istream_raw_mbox_get_body_size. This appears to handle the problem correctly in all the test cases I have. To anyone else who has run into this problem and gotten corrupted mailboxes as a result, I can also offer an mbox checker that will attempt to detect and repair this problem in existing mailboxes as well as inspect them for other problems. I'm not ready to send it out for a full release yet, but interested beta testers are invited to contact me directly. Cheers, --Lennart

2 1

[Dovecot] quota warning not working
by Claudio Prono 29 Oct '08

29 Oct '08

Hi all, I have finally get working the quota with dovecot. Now i am setting up the quota warning, with this in dovecot.conf: quota_warning = storage=70%% /usr/bin/quota_warning.sh 70 In the plugin section naturally. All seems to work fine, the quota is calculated right, but seems the script is not executed... In dovecot logs i have this: deliver(test(a)test.com): Oct 27 15:14:53 Info: Quota warning: bytes=10752000 (70%) messages=0 (0%) command=/usr/bin/quota_warning.sh 70 But...nothing happens. My quota_warning.sh is this: #!/bin/bash PERCENT=$1 echo "/usr/lib/dovecot/deliver -d "$USER" -c /usr/local/etc/dovecot-nowarning.conf" > /var/log/quotanotify cat << EOF | /usr/lib/dovecot/deliver -d "$USER" -c /usr/local/etc/dovecot-nowarning.conf From: postmaster(a)mediaservice.net Subject: quota warning Your mailbox is now $PERCENT% full. EOF I have added the echo for debug pourpose, but no file was created, so the script is not executed. I thinked is a permission problem, but seems not. Now the script is like this: -rwx--x--x 1 dovecot dovecot 317 Oct 27 15:30 /usr/bin/quota_warning.sh What can be the problem? Stuck!!! Claudio. -- ------------ Claudio Prono Systems Development @ Atpss.net Srl, Divisione Implementazione Sistemi Via San Bernardino, 17 - 10137 Torino (TO) - IT Tel +39-011.32.72.100 Fax +39-011.32.46.497 PGP Fingerprint: 75C2 4049 E23D 2FBF A65F 40DB EA5C 11AC C2B0 3647 Disclaimer: http://atpss.net/disclaimer ------------

2 2

[Dovecot] Dovecot pop3 and SonicWall?
by Brandon Lamb 29 Oct '08

29 Oct '08

Hello Has anyone else run into a problem with dovecot pop3 and sonicwall? A week after switching to dovecot we had two local customers call and report they could no longer download emails with attachments. It turned out to be the email macro filter on the router. After the first report I thought maybe the customer had just changed something or it was a fluke, but then a day later we had the second call with the same issue. For some reason, after us switching the sonicwall's email macro filter was catching any attachments as a threat. I couldnt see how changing pop3 servers could affect that, but I guess anything is possible. I just emailed sonicwall and am waiting for a response from them now as well. Hopefully maybe someone has heard of this before. Unfortunately, I dont know if this was pure coincidence, or if both customers happened to have updated their sonicwall software, or maybe it autoupdates, I have no information on it.Of course to them it looks like we broke it. We just had them both turn this rule off for now.

2 1

[Dovecot] Panic: pop3-login: file sasl-server.c: line 75 (authenticate_callback): assertion failed: (client->auth_request == request)
by Mike Abbott 29 Oct '08

29 Oct '08

Running Dovecot-1.1.5, I see this assertion failure: Panic: pop3-login: file sasl-server.c: line 75 (authenticate_callback): assertion failed: (client->auth_request == request) Error: pop3-login: Raw backtrace: 2 pop3-login 0x000000010000ac41 default_fatal_finish + 41 -> 3 pop3-login 0x000000010000acac i_syslog_fatal_handler + 0 -> 4 pop3-login 0x000000010000a446 i_info + 0 -> 5 pop3-login 0x00000001000053a2 authenticate_callback + 126 -> 6 pop3-login 0x000000010000841c auth_client_input_fail + 280 -> 7 pop3-login 0x0000000100007910 auth_client_input + 358 -> 8 pop3-login 0x000000010000e074 io_loop_handler_run + 272 -> 9 pop3-login 0x000000010000d449 io_loop_run + 38 -> 10 pop3-login 0x0000000100004864 main + 1572 -> 11 pop3-login 0x00000001000012fc start + 52 Error: child 1302 (login) killed with signal 6 This happens when I feed multiple user/pass lines to Dovecot all at once like this: $ telnet gromit 110 Connected. Escape character is '^]'. +OK Dovecot ready. user x pass y user x pass y +OK +OK Connection closed by foreign host. The four user/pass lines I pasted in all at once. IMAP login does not crash when presented with multiple login commands, but it does not read them all at once and needs prodding (in the form of extra command lines sent later on) to read them. Actually it appears to read the first two lines then stops reading until more data comes in: $ telnet gromit 143 Connected. Escape character is '^]'. * OK Dovecot ready. a login a b b login c d c login e f d login g h e login i j a NO Authentication failed. b NO Authentication failed. c NO Authentication failed. d NO Authentication failed. e NO Authentication failed. * BAD Error in IMAP command received by server. * BAD Error in IMAP command received by server. * BAD Error in IMAP command received by server. * BAD Error in IMAP command received by server. ^] telnet> q Connection closed. You probably don't care about the odd imap-login behavior, but I tried it and mentioned it just for completeness after seeing pop3-login crash.

2 1

[Dovecot] Best configuration of dovecot for limit Outlook problems with IMAP
by Alessio Cecchi 29 Oct '08

29 Oct '08

Hi, in some installation where users using IMAP and Outlook Express I have some problems. Outolook randomly presents problems in messages retrieving, for example: "Outlook Express is unable to retrieve the requested message because the server no longer has the message available.... server response: Fecth Completed" or "Message could not be displayed" error message when I try to view an Outlook Express e-mail message I'm using dovecot 1.1.4 with qmail and vpopmail. This is my dovecot configure options: ./configure --prefix=/usr --sysconfdir=/etc/dovecot --localstatedir=/var --with-ssldir=/etc/ssl and this my dovecot config: # dovecot -n # 1.1.4: /etc/dovecot/dovecot.conf log_path: /var/log/dovecot/dovecot-err.log info_log_path: /var/log/dovecot/dovecot.log ssl_cert_file: /etc/apache2/ssl/comun.crt ssl_key_file: /etc/apache2/ssl/comun.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_greeting: Ready login_process_per_connection: no first_valid_uid: 89 last_valid_uid: 89 first_valid_gid: 89 last_valid_gid: 89 mail_uid: 89 mail_gid: 89 mail_location: maildir:~/Maildir mail_debug: yes mail_plugins: quota imap_quota imap_client_workarounds: outlook-idle delay-newmail namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: verbose: yes debug: yes passdb: driver: checkpassword args: /home/vpopmail/bin/vchkpw userdb: driver: prefetch args: uid=89 gid=89 home=/home/vpopmail/domains/%d/%u plugin: quota: maildir What further changes to the configuration of dovecot could I do? Do you have other suggestions? Thanks -- Alessio Cecchi is: @ ILS -> http://www.linux.it/~alessice/ Assistenza Sistemi GNU/Linux -> http://www.cecchi.biz/ @ PLUG -> ex-Presidente, adesso senatore a vita, http://www.prato.linux.it @ LOLUG -> neo-Socio http://www.lolug.net

4 4

[Dovecot] Dovecot and quota enforcement - only reporting?
by dovecot＠corwyn.net 29 Oct '08

29 Oct '08

I'm currently setting up postfix and dovecot with virtual users (mysql), imap, and quotas. I'm setting the quotas using mysql. I have quotas working correctly, and I can telnet into the imap server, and submit . getquotaroot inbox and get back valid quota information. I get a maildirsize file in the Maildir directory. Very cool. When I delete mail and expunge it, the quota updates. However, inbound email doesn't appear to update the quota. Two questions, probably related: What causes the quota (which I presume is the maildirsize file) to update? Is there any actual quota enforcement, or just reporting? Because if I send mail to an account, even if it currently reporting (via maildirsize or . getquotaroot) that the user is over quota, they still can send and receive email. Thanks! Rick Rick Steeves http://www.sinister.net "The journey is the destination"

4 7

[Dovecot] mail_location: mbox: mkdir failed
by Albert E. Whale 29 Oct '08

29 Oct '08

Is there an automatic solution to this? Oct 27 08:00:48 192.168.50.5 dovecot: POP3(evelina2): mail_location: mbox: mkdir(/home/popuser_evelina2/mail) failed: Permission denied Oct 27 08:00:48 192.168.50.5 dovecot: Fatal: POP3(evelina2): Namespace initialization failed Oct 27 08:00:51 192.168.50.5 dovecot: POP3(evelina2): mail_location: mbox: mkdir(/home/popuser_evelina2/mail) failed: Permission denied Oct 27 08:00:51 192.168.50.5 dovecot: Fatal: POP3(evelina2): Namespace initialization failed -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ------------------------------------------------------------------------ ABS Computer Technology, Inc. <http://www.ABS-CompTech.com> - Email, Internet and Security Consultants SPAMZapper <http://www.Spam-Zapper.com> - No-JunkMail.com <http://www.No-JunkMail.com> - *True Spam Elimination*.

2 5

[Dovecot] Authentication Error Message formats
by Albert E. Whale 29 Oct '08

29 Oct '08

I have been using UW's IMAP server and I am converting to Dovecot for Maildir support. When a user fails authentication, or a user does not exist, it appears that the same message is used for these events. Is there a way to indicate that the user does not exist (Invalid user), and authentication Failure (Failed Password)? Clearly these two failures indicate a different error in the system. One that some forgot their password, the other indicates a dictionary attack. -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ------------------------------------------------------------------------ ABS Computer Technology, Inc. <http://www.ABS-CompTech.com> - Email, Internet and Security Consultants SPAMZapper <http://www.Spam-Zapper.com> - No-JunkMail.com <http://www.No-JunkMail.com> - *True Spam Elimination*.

3 5