Re: [Dovecot] Courier to dovecot migrations
On Tue, Mar 16, 2010 at 11:41:47AM +0100, Thomas Leuxner wrote: Hi, to diagnose, can you provide full output of 'dovecot -n' plus the dovecot LDA excerpexcerptom Postfix's 'master.cf'? Regards Thomas ... ouch... Of course this should read: excerpt from 'master.cf' :)
Re: [Dovecot] Dovecot 2.0beta3: Crash with mail_log plugin enabled
Am 16.03.2010 um 13:48 schrieb Timo Sirainen: Actually it happens when copying a message (which is what your client does when deleting). Can you easily reproduce this? I can't.. What mailbox format are you using? Also the backtrace has some wrong values because of gcc optimizations, it might help more if you compiled without -O2 (CFLAGS=-g ./configure). mail_location = mdbox:~/mdbox I can reproduce at will, but have trouble overriding the O2 optimization with 'dpkg-buildpackage'. Thomas
Re: [Dovecot] Dovecot 2.0beta3: Crash with mail_log plugin enabled
Am 16.03.2010 um 20:35 schrieb Pascal Volk:
The CFLAGS env variable is also honored. e.g.:
CFLAGS=-g3 -O0 DEB_BUILD_OPTIONS=nostrip debug dpkg-buildpackage
Thanks Pascal, that did the trick. Core dump attached:
[20:52] root spectre:/tmp# gdb /usr/lib/dovecot/imap /tmp/core
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 x86_64-linux-gnu...
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...done.
Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0
Reading symbols from /usr/lib/dovecot/libdovecot.so.0...done.
Loaded symbols for /usr/lib/dovecot/libdovecot.so.0
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/librt.so.1...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib/libpthread.so.0...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /usr/lib/dovecot/modules/lib01_acl_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/modules/lib01_acl_plugin.so
Reading symbols from /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so
Reading symbols from /usr/lib/dovecot/modules/lib10_quota_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/modules/lib10_quota_plugin.so
Reading symbols from /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so
Reading symbols from /usr/lib/dovecot/modules/lib15_notify_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/modules/lib15_notify_plugin.so
Reading symbols from /usr/lib/dovecot/modules/lib20_mail_log_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/modules/lib20_mail_log_plugin.so
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Core was generated by `dovecot/imap'.
Program terminated with signal 6, Aborted.
[New process 31462]
#0 0x7feb99a2fed5 in raise () from /lib/libc.so.6#0 0x7feb99a2fed5 in
raise () from /lib/libc.so.6
No symbol table info available.
#1 0x7feb99a313f3 in abort () from /lib/libc.so.6
No symbol table info available.
#2 0x7feb9a19efca in default_fatal_finish (type=LOG_TYPE_PANIC, status=0)
at failures.c:164
backtrace = 0x628660 /usr/lib/dovecot/libdovecot.so.0 [0x7feb9a19efa6]
- /usr/lib/dovecot/libdovecot.so.0 [0x7feb9a1a02eb] -
/usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7feb9a19f31a] -
/usr/lib/dovecot/libdovecot-st...
#3 0x7feb9a1a02eb in i_internal_fatal_handler (type=LOG_TYPE_PANIC,
status=0, fmt=0x7feb9a4b9f18 file %s: line %d (%s): assertion failed: (%s),
args=0x7fffba90) at failures.c:592
No locals.
#4 0x7feb9a19f31a in i_panic (format=0x7feb9a4b9f18 file %s: line %d
(%s): assertion failed: (%s)) at failures.c:230
args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area =
0x7fffbb70, reg_save_area = 0x7fffbab0}}
#5 0x7feb9a44c531 in view_lookup_uid (view=0x66a950, seq=0,
uid_r=0x7fffbc2c) at mail-index-view.c:210
__PRETTY_FUNCTION__ = view_lookup_uid
#6 0x7feb9a43fb82 in tview_lookup_uid (view=0x66a950, seq=0,
uid_r=0x7fffbc2c) at mail-index-transaction-view.c:163
tview = (struct mail_index_view_transaction *) 0x66a950
#7 0x7feb9a44ce6e in mail_index_lookup_uid (view=0x66a950, seq=0,
uid_r=0x7fffbc2c) at mail-index-view.c:474
No locals.
#8 0x7feb9a428180 in mail_cache_decision_state_update (view=0x66ac70,
seq=0, field=12) at mail-cache-decisions.c:82
cache = (struct mail_cache *) 0x668090
hdr = (const struct mail_index_header *) 0x7feb9a901548
uid = 0
__PRETTY_FUNCTION__ = mail_cache_decision_state_update
#9 0x7feb9a42adcf in mail_cache_lookup_headers_real (view=0x66ac70,
dest=0x685278, seq=0, field_idxs=0x7fffbdfc, fields_count=1) at
mail-cache-lookup.c:484
cache = (struct mail_cache *) 0x668090
iter = {view = 0x7feb9a3f8760, remap_counter = 2593133896, seq = 32747,
rec = 0x80, pos = 4294967295, rec_size = 0, offset = 4294950208, stop = 1,
failed = 1, appends_checked = 1}
field = {field_idx = 4294950128, data = 0x80, size = 6836816}
ctx = {view = 0x669b10, lines = {arr = {buffer = 0x6692c0, element_size
= 1011198389976563728}, v = 0x6692c0, v_modifiable = 0x6692c0}}
lines = (struct header_lookup_line *) 0x7fffc570
p = (const unsigned char *) 0x0
start = (const unsigned char *) 0x0
Re: [Dovecot] Dovecot 2.0beta3: Auth master process is now running as default_internal_user
Am 16.03.2010 um 20:57 schrieb Timo Sirainen:
[20:27] root spectre:/var/vmail/conf.d# l
drwxr-x--- 4 dovecot vmail 4096 2010-03-14 17:40 leuxner.net
..
drwx-- 2 vmail vmail 4096 2010-03-14 13:09 acls
Why does vmail own any of these files? Dovecot accesses them only via
dovecot-auth. Do you have something else that needs to read/write them
as vmail?
I think the best solutions are (in order):
1) Create a new doveauth user that has read (but no write) access to the
files. Use doveauth for auth process.
2) Use root user for files and auth process.
3) Use dovecot user for files and auth process.
Right, if I'd like to go with 1) where would I put the 'doveauth' user in the
config to have 'passwd' read with it? Looks like it is still using 'dovecot'
per default:
service auth {
unix_listener auth-userdb {
mode = 0600
user = doveauth
}
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
}
service auth-worker {
unix_listener auth-worker {
mode = 0600
user = doveauth
}
}
The reason 'vmail' is the group owner of the 'sieve' and 'acl' subdirs was the
idea to have all config stored under the 'domain.tld' folder. The LMTP Service
will access this folder with the user permissions.
Regards
Thomas
Re: [Dovecot] Dovecot 2.0beta3: Crash with mail_log plugin enabled
Am 16.03.2010 um 21:29 schrieb Timo Sirainen: Right, looks like it was crashing with mdbox. I thought I tested that but I guess I didn't. Fixed now. It does not crash anymore, but it looks like the fix has a bad side effect. Client can not see INBOX any more, tested with Mail.app and Mutt. Rolling back to an previous build without these restores functionality: - mdbox: Don't crash when accessing a copied mail that hasn't been committed yet. - acl: Don't crash if opening dovecot-acl fails with EACCES. Regards Thomas
Re: [Dovecot] Dovecot 2.0beta3: Crash with mail_log plugin enabled
Am 16.03.2010 um 23:40 schrieb Timo Sirainen:
That affects only if you have dovecot-acl files that the process can't open
because it doesn't have permission. Do you have such files somewhere?
Tough one. Caused by the 'doveauth' service permission changes added to my
config before. Actually it was the global INBOX ACL owned by the wrong user,
triggered by:
plugin {
acl = vfile:/var/vmail/conf.d/%d/acls:cache_secs=300
}
Thanks for pointing me in the right direction.
Regards
Thomas
Re: [Dovecot] public folders grayed out
Am 15.03.2010 um 16:40 schrieb Harald Dunkel: Hi folks, I have configured a public folder as described on the Wiki (more or less; see below), but in TB3 I see the Public folder grayed out. I cannot subscribe. Toggling the subscriptions flag doesn't help. What did I miss here? Any helpful comment would be highly appreciated. If this is a TB3 problem: Which MUA would you suggest? Hi, quick guess: Did you create subfolders under 'var/spool/imap/public' with appropriate ACLs, or is the public dir still empty? /var/spool/imap/public/lists $ cat /var/spool/imap/public/lists/dovecot-acl anyone lr Regards Thomas
[Dovecot] Dovecot 2.0beta3: Auth master process is now running as default_internal_user
Hi,
with 'changeset 10910' the Auth master process is running as
'default_internal_user' now (dovecot). This requires permissions tuning for
'passwd-files' at least, while other plugins would run in a different user
context, 'vmail' in my setup. I see that this may be safer, just wondering how
to streamline the config:
[20:27] root spectre:/var/vmail/conf.d# l
drwxr-x--- 4 dovecot vmail 4096 2010-03-14 17:40 leuxner.net
[20:27] root spectre:/var/vmail/conf.d# l leuxner.net/
drwx-- 2 vmail vmail 4096 2010-03-14 13:09 acls
-r 1 dovecot vmail 125 2010-02-07 13:08 passwd
drwx-- 2 vmail vmail 4096 2010-03-14 12:13 sieve
[20:27] root spectre:/var/vmail/conf.d# cat leuxner.net/passwd
t...@leuxner.net:{SSHA}:5000:5000::/var/vmail/leuxner.net/tlx::userdb_quota_rule=*:storage=5G
[…]
Regards
Thomas
Re: [Dovecot] Dovecot 2.0beta3: Auth changes in Mercurial
Core dump with all the latest changes: Mar 14 07:22:57 spectre dovecot: master: service(auth): child 1841 killed with signal 11 (core dumped) 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 x86_64-linux-gnu... warning: Can't read pathname for load map: Input/output error. Reading symbols from /usr/lib/dovecot/libdovecot.so.0...Reading symbols from /usr/lib/debug/usr/lib/dovecot/libdovecot.so.0.0.0...done. done. Loaded symbols for /usr/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libcrypt.so.1...done. Loaded symbols for /lib/libcrypt.so.1 Reading symbols from /lib/libpam.so.0...done. Loaded symbols for /lib/libpam.so.0 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/librt.so.1...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /lib/libc.so.6...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux-x86-64.so.2...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib/libpthread.so.0...done. Loaded symbols for /lib/libpthread.so.0 Core was generated by `dovecot/auth'. Program terminated with signal 11, Segmentation fault. [New process 1841] #0 aqueue_count (aqueue=0x0) at aqueue.c:122 122 aqueue.c: No such file or directory. in aqueue.c (gdb) bt full #0 aqueue_count (aqueue=0x0) at aqueue.c:122 area_size = 6583600 #1 0x0041010b in auth_request_handler_flush_failures (flush_all=true) at auth-request-handler.c:569 auth_requests = value optimized out auth_request = value optimized out i = value optimized out count = value optimized out __PRETTY_FUNCTION__ = auth_request_handler_flush_failures #2 0x004101fe in auth_request_handler_deinit () at auth-request-handler.c:608 No locals. #3 0x0040a136 in auth_deinit (_auth=0x0) at auth.c:229 auth = (struct auth *) 0x644df8 passdb = value optimized out userdb = (struct auth_userdb *) 0x0 #4 0x0040a19f in auths_deinit () at auth.c:291 auth = (struct auth **) 0x642010 i = value optimized out #5 0x004147fe in main (argc=1, argv=0x639370) at main.c:115 c = value optimized out Regards Thomas
[Dovecot] Dovecot 2.0beta3: Crash with mail_log plugin enabled
Latest from Mercurial. Dovecot crashes with 'mail_log' and 'notify' plugins
enabled when deleting a message:
[08:22] root spectre:~# gdb /usr/lib/dovecot/imap /tmp/core
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 x86_64-linux-gnu...
warning: Can't read pathname for load map: Input/output error.
Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...Reading symbols
from /usr/lib/debug/usr/lib/dovecot/libdovecot-storage.so.0.0.0...done.
done.
Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0
Reading symbols from /usr/lib/dovecot/libdovecot.so.0...Reading symbols from
/usr/lib/debug/usr/lib/dovecot/libdovecot.so.0.0.0...done.
done.
Loaded symbols for /usr/lib/dovecot/libdovecot.so.0
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/librt.so.1...done.
Loaded symbols for /lib/librt.so.1
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux-x86-64.so.2...done.
Loaded symbols for /lib64/ld-linux-x86-64.so.2
Reading symbols from /lib/libpthread.so.0...done.
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /usr/lib/dovecot/modules/lib01_acl_plugin.so...Reading
symbols from /usr/lib/debug/usr/lib/dovecot/modules/lib01_acl_plugin.so...done.
done.
Loaded symbols for /usr/lib/dovecot/modules/lib01_acl_plugin.so
Reading symbols from
/usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...Reading symbols from
/usr/lib/debug/usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...done.
done.
Loaded symbols for /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so
Reading symbols from /usr/lib/dovecot/modules/lib10_quota_plugin.so...Reading
symbols from
/usr/lib/debug/usr/lib/dovecot/modules/lib10_quota_plugin.so...done.
done.
Loaded symbols for /usr/lib/dovecot/modules/lib10_quota_plugin.so
Reading symbols from
/usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...Reading symbols from
/usr/lib/debug/usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...done.
done.
Loaded symbols for /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so
Reading symbols from /usr/lib/dovecot/modules/lib15_notify_plugin.so...Reading
symbols from
/usr/lib/debug/usr/lib/dovecot/modules/lib15_notify_plugin.so...done.
done.
Loaded symbols for /usr/lib/dovecot/modules/lib15_notify_plugin.so
Reading symbols from
/usr/lib/dovecot/modules/lib20_mail_log_plugin.so...Reading symbols from
/usr/lib/debug/usr/lib/dovecot/modules/lib20_mail_log_plugin.so...done.
done.
Loaded symbols for /usr/lib/dovecot/modules/lib20_mail_log_plugin.so
Reading symbols from /lib/libgcc_s.so.1...done.
Loaded symbols for /lib/libgcc_s.so.1
Core was generated by `dovecot/imap'.
Program terminated with signal 6, Aborted.
[New process 2151]
#0 0x7f5c79480ed5 in raise () from /lib/libc.so.6
#0 0x7f5c79480ed5 in raise () from /lib/libc.so.6
No symbol table info available.
#1 0x7f5c794823f3 in abort () from /lib/libc.so.6
No symbol table info available.
#2 0x7f5c79be62c5 in default_fatal_finish (type=value optimized out,
status=0) at failures.c:164
backtrace = 0x61f660 /usr/lib/dovecot/libdovecot.so.0 [0x7f5c79be62b2]
- /usr/lib/dovecot/libdovecot.so.0 [0x7f5c79be631a] -
/usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f5c79be66c3] -
/usr/lib/dovecot/libdovecot-st...
#3 0x7f5c79be631a in i_internal_fatal_handler (type=LOG_TYPE_PANIC,
status=0, fmt=value optimized out, args=value optimized out) at
failures.c:592
No locals.
#4 0x7f5c79be66c3 in i_panic (format=value optimized out) at
failures.c:230
args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area =
0x7fffd370, reg_save_area = 0x7fffd2b0}}
#5 0x7f5c79e72748 in view_lookup_uid (view=0x6614c0, seq=0,
uid_r=0x7fffd39c) at mail-index-view.c:210
__PRETTY_FUNCTION__ = view_lookup_uid
#6 0x7f5c79e589c6 in mail_cache_decision_state_update (view=0x661800,
seq=2151, field=12) at mail-cache-decisions.c:82
cache = (struct mail_cache *) 0x65e790
hdr = value optimized out
uid = value optimized out
__PRETTY_FUNCTION__ = mail_cache_decision_state_update
#7 0x7f5c79e5a4b0 in mail_cache_lookup_headers (view=0x661800,
dest=0x67be28, seq=0, field_idxs=0x7fffd56c, fields_count=1) at
mail-cache-lookup.c:484
_data_stack_cur_id = 5
ret = value optimized out
#8 0x7f5c79e88d22 in index_mail_get_raw_headers (mail=0x67b618,
field=0x7f5c78608dc7 Message-ID, value_r=0x7fffd5c8) at
index-mail-headers.c:614
headers = {0x67b618 \230?e, 0x7f5c79bfda98 H\201??}
value = value optimized out
headers_ctx = value optimized out
data = value
Re: [Dovecot] Dovecot 2.0beta3: Latest HG crashed upon LMTP Delivery
On Tue, Mar 09, 2010 at 01:21:40PM +0200, Timo Sirainen wrote: With LMTP or also with LDA? What's the backtrace now? It seems to be working with me. Only tested with LMTP as not using LDA anymore, but in the same manner, with a simple handshake: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f40f2dde6e0 (LWP 26430)] 0x7f40f26be630 in message_parse_header_next () from /usr/lib/dovecot/libdovecot.so.0 (gdb) bt full #0 0x7f40f26be630 in message_parse_header_next () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #1 0x7f40f26bffb3 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #2 0x7f40f26bf659 in message_parser_parse_next_block () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x7f40f26bf86b in message_parser_parse_header () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #4 0x7f40f2970c10 in index_mail_parse_headers () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #5 0x7f40f2970f47 in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #6 0x7f40f29712af in index_mail_get_first_header () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #7 0x7f40f16fe846 in ?? () from /usr/lib/dovecot/modules/lib90_sieve_plugin.so No symbol table info available. #8 0x0040a663 in mail_deliver () No symbol table info available. #9 0x00406a53 in ?? () No symbol table info available. #10 0x00406fc8 in ?? () No symbol table info available. #11 0x7f40f26d900b in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #12 0x7f40f26d8188 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #13 0x7f40f26c8193 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #14 0x00405be3 in main () No symbol table info available. Thomas
Re: [Dovecot] Solaris + Postfix + Dovecot
On Tue, Mar 09, 2010 at 10:48:59AM -0300, Zilon X wrote: Hello Thomas, Thank you - but I found nothing specific to Solaris there. Already installed Postfix 2.7.0, Mysql 5.1, Dovecot 1.2.10, and Posfixadmin 2.3 on a Solaris 10 Sparc zone. Still a lot of quirks on configuration here. I also want to configure Roundcube 0.3.1 with this Dovecot/Postfix install. Hey, how about you post your 'dovecot -n' output here and ask for areas unclear? Regards Thomas
Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)
With the latest fix from Mercurial it does not crash anymore. The message shows empty and the container in question 'm.59.broken' stays in the 'storage' dir. Is this expected behavior and am I save to delete the broken container, or how would I clean up the corruption? Regards Thomas
Re: [Dovecot] Dovecot 2.0beta3: Latest HG crashed upon LMTP Delivery
On Tue, Mar 09, 2010 at 01:04:44AM +0200, Timo Sirainen wrote: Yeah, it's this one. I'll probably revert it soon. I did it mostly while trying to fix istream-zlib bugs, but hopefully zlib won't break when that change is reverted :) Started my stress test again.. Just tested and does not appear to be fixed by changeset 10875 1473de6ba383. Still crashes. Regards Thomas
Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)
Am 09.03.2010 um 19:01 schrieb Timo Sirainen: Is it in the fixed m.59? The fixing/resyncing was supposed to preserve all mails. Actually 'm.59' was not rebuilt but it continued with new containers. Grepping for the content, it remained in the broken container only. Regards Thomas
Re: [Dovecot] Dovecot 2.0beta3: mdbox crash on corrupted mail (backtrace included)
Am 09.03.2010 um 19:02 schrieb Timo Sirainen: I guess this imap session was open while doveadm was running? You are right.
[Dovecot] Dovecot 2.0beta3: Latest HG crashed upon LMTP Delivery
Hi, unsure how to provide more useful information, as I can not get LMTP to create a core dump. With the latest changes from Mercurial it dies upon message delivery: == /var/log/dovecot.log == Mar 8 20:03:33 spectre dovecot: lmtp(11690): Connect from local Mar 8 20:03:33 spectre dovecot: lmtp(11690): Connect from local Mar 8 20:03:33 spectre dovecot: lmtp(11690): Connect from local Mar 8 20:03:33 spectre dovecot: master: service(lmtp): child 11690 killed with signal 11 (core not dumped) Mar 8 20:03:33 spectre dovecot: master: service(lmtp): command startup failed, throttling Thomas
Re: [Dovecot] Dovecot 2.0beta3: Latest HG crashed upon LMTP Delivery
Simple LMTP handshake crashes it: [20:19] root spectre:/usr/lib/dovecot# ./lmtp 220 spectre.leuxner.net Dovecot LMTP ready Info: Connect from local lhlo leuxner.net 250-spectre.leuxner.net 250-8BITMIME 250-ENHANCEDSTATUSCODES 250 PIPELINING mail from:t...@leuxner.net 250 2.1.0 OK rcpt to:t...@leuxner.net 250 2.1.5 OK data 354 OK test . Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7f08f26006e0 (LWP 11784)] 0x7f08f1ee1630 in message_parse_header_next () from /usr/lib/dovecot/libdovecot.so.0 (gdb) bt full #0 0x7f08f1ee1630 in message_parse_header_next () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #1 0x7f08f1ee2fb3 in ?? () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #2 0x7f08f1ee2659 in message_parser_parse_next_block () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x7f08f1ee286b in message_parser_parse_header () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #4 0x7f08f2193c40 in index_mail_parse_headers () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #5 0x7f08f2193f77 in ?? () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #6 0x7f08f21942df in index_mail_get_first_header () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #7 0x7f08f0f21846 in ?? () from /usr/lib/dovecot/modules/lib90_sieve_plugin.so No symbol table info available. #8 0x0040a663 in mail_deliver () No symbol table info available. #9 0x00406a53 in ?? () No symbol table info available. #10 0x00406fc8 in ?? () No symbol table info available. #11 0x7f08f1efc00b in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #12 0x7f08f1efb188 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #13 0x7f08f1eeb193 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #14 0x00405be3 in main () No symbol table info available.
Re: [Dovecot] Dovecot 2.0.beta3: mdbox mailbox crashes upon login
On Thu, Mar 04, 2010 at 04:52:56PM +0200, Timo Sirainen wrote: What about: http://hg.dovecot.org/dovecot-2.0/rev/c691706eee06 If it still crashes, gdb backtrace would be nice. http://dovecot.org/bugreport.html Haven't tested this one yet, but I think the problem vanished with: http://hg.dovecot.org/dovecot-2.0/rev/154f52b7a6fd Just wanted to monitor it for some time, but do consider it fixed now, apart from the ACL problem in another thread. Regards Thomas
Re: [Dovecot] Dovecot 2.0.beta3: mdbox mailbox crashes upon login
Am 04.03.2010 um 15:52 schrieb Timo Sirainen: What about: http://hg.dovecot.org/dovecot-2.0/rev/c691706eee06 If it still crashes, gdb backtrace would be nice. http://dovecot.org/bugreport.html Still running fine with this one applied. Regards Thomas
[Dovecot] Dovecot 2.0b3: mdbox with incorrect ACL file permissions crashes
Hi, played around with 'mdbox' format some more. Converted my personal mailbox with latest Dovecot and dsync from HG: dsync convert -u lo...@yourdomain.com mdbox:~/mdbox One thing I noticed is, that dsync does not take care of existing 'dovecot-acl' files, which it should migrate/copy from my point of view, but simply skips them. Anyway I copied over the ACLs manually and forgot to set the rights accordingly. So the files were owned by 'root:vmail' instead of 'vmail:vmail' in my setup. Voilà Dovecot crashed, where it should really throw a warning or ignore the owner and work with the group permissions: Mar 2 19:27:52 spectre dovecot: imap(t...@leuxner.net): acl vfile: file /var/vmail/conf.d/leuxner.net/acls/Support/Serverloft not found Mar 2 19:27:52 spectre dovecot: imap(t...@leuxner.net): acl vfile: no access to file /var/vmail/leuxner.net/tlx/mdbox/mailboxes/Support/Serverloft/dbox-Mails/dovecot-acl Mar 2 19:27:52 spectre dovecot: imap(t...@leuxner.net): Panic: file acl-cache.c: line 295 (acl_cache_update_rights): assertion failed: (obj_cache-my_current_rights != negative_cache_entry) Mar 2 19:27:52 spectre dovecot: imap(t...@leuxner.net): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x7f4d8595ffb2] - /usr/lib/dovecot/libdovecot.so.0 [0x7f4d8596001a] - /usr/lib/dovecot/libdovecot.so.0 (i_error+0) [0x7f4d859603c3] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7f4d84da690b] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7f4d84da4249] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0 x7f4d84da4572] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7f4d84da472e] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7f4d84da2aba] - /usr/lib/dovecot/modules/lib01_acl_plugin.so(acl_object_get_m y_rights+0x65) [0x7f4d84da2b85] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7f4d84da8fd9] - dovecot/imap [...@leuxner.net 84.58.106.99 STATUS](client_find_namespace+0x17f) [0x41149f] - dovecot/imap [t l...@leuxner.net 84.58.106.99 STATUS](cmd_status+0xfc) [0x40dc2c] - dovecot/imap [...@leuxner.net 84.58.106.99 STATUS] [0x40f9bc] - dovecot/imap [...@leuxner.net 84.58.106.99 STATUS] [0x40fa6d] - dovecot/imap [...@leuxner.net 84.58.106.99 STATUS](client_handle_input+0x45) [0x40fbe5] - dovecot/imap [...@leuxner.net 84.58.106.99 STATUS](client_input+0x62) [0x410622] - /usr/lib/dovecot/libdovecot.so.0(io_loop_handl er_run+0xcb) [0x7f4d8596abab] - /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x18) [0x7f4d85969d28] - /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f4d85959eb3] - dovecot/imap [...@leuxner.n et 84.58.106.99 STATUS](main+0x191) [0x418661] - /lib/libc.so.6(__libc_start_main+0xe6) [0x7f4d851e71a6] - dovecot/imap [...@leuxner.net 84.58.106.99 STATUS] [0x4084e9] Mar 2 19:27:52 spectre dovecot: master: service(imap): child 30281 killed with signal 6 (core dumps disabled) Regards Thomas
[Dovecot] Dovecot 2.0.beta3: Child killed with signal 11
Hi, I'm seeing these after the latest Mercurial updates: == /var/log/dovecot.info == Feb 28 16:07:00 spectre dovecot: master: service(lmtp): child 17322 killed with signal 11 (core dumps disabled) Regards Thomas
Re: [Dovecot] Dovecot 2.0.beta3: Child killed with signal 11
If you have trouble getting a core, an easy way should be to attach to existing lmtp process: 1. telnet localhost lmtp port quit 2. gdb -p `pidof lmtp` cont 3. make it crash 4. gdb: bt full Not sure I'm doing this correctly. Core Dumps seem to be disabled in my vanilla Kernel. Running 'gdb' also seems not to produce the result wanted. As long as GDB is attached it does not crash the 'lmtp' process, only when I quit the debugger. Feb 28 16:51:18 spectre dovecot: lmtp(17782): Disconnect from 188.138.0.199: Client quit [16:50] root spectre:~# gdb -p 17782 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 x86_64-linux-gnu. Attaching to process 17782 Reading symbols from /usr/lib/dovecot/lmtp...(no debugging symbols found)...done. Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/lib/dovecot/libdovecot.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux-x86-64.so.2... (no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done. [Thread debugging using libthread_db enabled] [New Thread 0x7f30067dd6e0 (LWP 17782)] Loaded symbols for /lib/libpthread.so.0 Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /usr/lib/dovecot/modules/lib10_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/modules/lib10_quota_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib90_sieve_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/modules/lib90_sieve_plugin.so Reading symbols from /usr/lib/dovecot/libdovecot-sieve.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/libdovecot-sieve.so.0 (no debugging symbols found) 0x7f3005a07b23 in epoll_wait () from /lib/libc.so.6 (gdb) cont Continuing. Program received signal SIGINT, Interrupt. [Switching to Thread 0x7f30067dd6e0 (LWP 17782)] 0x7f3005a07b23 in epoll_wait () from /lib/libc.so.6 (gdb) bt full #0 0x7f3005a07b23 in epoll_wait () from /lib/libc.so.6 No symbol table info available. #1 0x7f30060d9abb in io_loop_handler_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #2 0x7f30060d8ca8 in io_loop_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x7f30060c8eb3 in master_service_run () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #4 0x00405b02 in main () No symbol table info available. == /var/log/dovecot.info == Feb 28 16:58:30 spectre dovecot: master: service(lmtp): child 17782 killed with signal 11 (core not dumped)
Re: [Dovecot] Dovecot 2.0.beta3: Child killed with signal 11
Hopefully useful now... 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 x86_64-linux-gnu... (no debugging symbols found) warning: Can't read pathname for load map: Input/output error. Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/lib/dovecot/libdovecot.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 Reading symbols from /lib/libpthread.so.0... (no debugging symbols found)...done. Loaded symbols for /lib/libpthread.so.0 Reading symbols from /usr/lib/dovecot/modules/lib01_acl_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/modules/lib01_acl_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/modules/lib02_imap_acl_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib10_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/modules/lib10_quota_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/modules/lib11_imap_quota_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib20_fts_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/modules/lib20_fts_plugin.so Reading symbols from /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so... (no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/modules/lib21_fts_squat_plugin.so (no debugging symbols found) Core was generated by `dovecot/imap'. Program terminated with signal 11, Segmentation fault. [New process 17997] #0 0x7f256d8c86ee in hash_table_destroy () from /usr/lib/dovecot/libdovecot.so.0 (gdb) bt full #0 0x7f256d8c86ee in hash_table_destroy () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #1 0x7f256d8a54c4 in settings_parser_deinit () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #2 0x7f256d8c0bbc in master_service_settings_cache_deinit () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #3 0x7f256db33709 in mail_storage_service_deinit () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #4 0x00418629 in main () No symbol table info available. Feb 28 17:15:22 spectre dovecot: master: service(imap): child 17997 killed with signal 11 (core dumped)
[Dovecot] Dovecot 2.0.beta3: mdbox mailbox crashes upon login
Hi, converted my personal mailbox from 'maildir' to 'mdbox' for testing today: # dsync convert -u u...@domain mdbox:~/mdbox Set mail location to mdbox in 'mail.conf' and restarted server: mail_location = mdbox:~/mdbox Dovecot panicked instantly upon login with different clients. Tried to disable several plugins to no avail: Feb 28 14:43:02 spectre dovecot: imap(u...@domain): Panic: file mailbox-list-fs.c: line 170 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) Feb 28 14:43:02 spectre dovecot: imap(u...@domain): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x7f0a0d891e72] - /usr/lib/dovecot/libdovecot.so.0 [0x7f0a0d891eda] - /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f0a0d892283] - /usr/lib/dovecot/libdovecot-storage.so.0 [0x7f0a0db2b2c3] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7f0a0ccd70c3] - /usr/lib/dovecot/modules/lib01_acl_plugin.so(acl_mailbox_list_have_right+0x5c) [0x7f0a0ccdadbc] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7f0a0ccdb12c] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_iter_next+0xa) [0x7f0a0dafc4da] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7f0a0ccdaa2a] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7f0a0ccdb252] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_iter_next+0xa) [0x7f0a0dafc4da] - dovecot/imap [u...@domain 84.58.106.99 LIST] [0x40b549] - dovecot/imap [u...@domain 84.58.106.99 LIST](cmd_list_full+0x4e6) [0x40c446] - dovecot/imap [u...@domain 84.58.106.99 LIST] [0x40f9bc] - dovecot/imap [u...@domain 84.58.106.99 LIST] [0x40fa6d] - dovecot/imap [u...@domain 84.58.106.99 LIST](client_handle_input+0x45) [0x40fbe5] - dovecot/imap [u...@domain 84.58.106.99 LIST](client_input+0x62) [0x410622] - /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xcb) [0x7f0a0d89c8fb] - /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x18) [0x7f0a0d89ba78] - /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f0a0d88be33] - dovecot/imap [u...@domain 84.58.106.99 LIST](main+0x191) [0x418661] - /lib/libc.so.6(__libc_start_main+0xe6) [0x7f0a0d1191a6] - dovecot/imap [u...@domain 84.58.106.99 LIST] [0x4084e9] Feb 28 14:43:02 spectre dovecot: master: service(imap): child 10202 killed with signal 6 (core dumps disabled) Regards Thomas
Re: [Dovecot] Dovecot 2.0.beta3: mdbox mailbox crashes upon login
Am 28.02.2010 um 20:23 schrieb Timo Sirainen: On Sun, 2010-02-28 at 20:11 +0100, Thomas Leuxner wrote: Feb 28 14:43:02 spectre dovecot: imap(u...@domain): Panic: file mailbox-list-fs.c: line 170 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) I guess this helps: http://hg.dovecot.org/dovecot-2.0/rev/64f6c458aaff Still crashes right away: == /var/log/dovecot.info == Feb 28 20:45:26 spectre dovecot: master: Dovecot v2.0.beta3 starting up (core dumps disabled) Feb 28 20:45:37 spectre dovecot: imap-login: Login: user=t...@leuxner.net, method=PLAIN, rip=84.58.106.99, lip=188.138.0.199, TLS Feb 28 20:45:38 spectre dovecot: imap-login: Login: user=t...@leuxner.net, method=PLAIN, rip=84.58.106.99, lip=188.138.0.199, TLS Feb 28 20:45:38 spectre dovecot: imap(t...@leuxner.net): Connection closed bytes=16/162 Feb 28 20:45:42 spectre dovecot: imap-login: Login: user=t...@leuxner.net, method=PLAIN, rip=84.58.106.99, lip=188.138.0.199, TLS Feb 28 20:45:42 spectre dovecot: imap-login: Login: user=t...@leuxner.net, method=PLAIN, rip=84.58.106.99, lip=188.138.0.199, TLS Feb 28 20:45:43 spectre dovecot: imap-login: Login: user=t...@leuxner.net, method=PLAIN, rip=84.58.106.99, lip=188.138.0.199, TLS Feb 28 20:45:43 spectre dovecot: imap(t...@leuxner.net): Panic: file mailbox-list-fs.c: line 170 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) Feb 28 20:45:43 spectre dovecot: imap(t...@leuxner.net): Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x7ff111d3cf72] - /usr/lib/dovecot/libdovecot.so.0 [0x7ff111d3cfda] - /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7ff111d3d383] - /usr/lib/dovecot/libdovecot-storage.so.0 [0x7ff111fd72e3] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7ff820c3] - /usr/lib/dovecot/modules/lib01_acl_plugin.so(acl_mailbox_list_have_right+0x5c) [0x7ff85dbc] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7ff8612c] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_iter_next+0xa) [0x7ff111fa84da] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7ff85a2a] - /usr/lib/dovecot/modules/lib01_acl_plugin.so [0x7ff86252] - /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_iter_next+0xa) [0x7ff111fa84da] - dovecot/imap [...@leuxner.net 84.58.106.99 LIST] [0x40b549] - dovecot/imap [...@leuxner.net 84.58.106.99 LIST](cmd_list_full+0x4e6) [0x40c446] - dovecot/imap [...@leuxner.net 84.58.106.99 LIST] [0x40f9bc] - dovecot/imap [...@leuxner.net 84.58.106.99 LIST] [0x40fa6d] - dovecot/imap [...@leuxner.net 84.58.106.99 LIST](client_handle_input+0x45) [0x40fbe5] - dovecot/imap [...@leuxner.net 84.58.106.99 LIST](client_input+0x62) [0x410622] - /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xcb) [0x7ff111d47b6b] - /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x18) [0x7ff111d46ce8] - /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ff111d36eb3] - dovecot/imap [...@leuxner.net 84.58.106.99 LIST](main+0x191) [0x418661] - /lib/libc.so.6(__libc_start_main+0xe6) [0x7ff1115c41a6] - dovecot/imap [...@leuxner.net 84.58.106.99 LIST] [0x4084e9] Feb 28 20:45:43 spectre dovecot: master: service(imap): child 12295 killed with signal 6 (core dumps disabled) Feb 28 20:45:43 spectre dovecot: imap-login: Login: user=t...@leuxner.net, method=PLAIN, rip=84.58.106.99, lip=188.138.0.199, TLS
[Dovecot] Dovecot mbox
Hi, Just wondering for all you people using Dovecot out there. 1. What mailbox protocol are you using? 2. What version of Dovecot? Thanks! * * Tom Goerger - Email/Unix System Administrator * * * * University of Minnesota Email: t...@umn.edu * * Operations, Infrastructure and Architecture Phone: 4-5804 * * Internet ServicesOffice: 626J WBOB* * * *
Re: [Dovecot] v2.0.beta3 released
Am 22.02.2010 um 16:29 schrieb Timo Sirainen:
What specific logging option for LDA?.. Seems to work exactly the same
as in v1.2:
protocol lda {
info_log_path = /tmp/deliver.log
}
Ah ok. Thought all logging ought to be configured in 'logging.conf' as there
was no example in 'lda.conf'. Since I switched to lmtp delivery yesterday,
would it also be possible to have a different logging path for that?
Thanks
Thomas
Re: [Dovecot] v2.0.beta3 released
Am 22.02.2010 um 18:53 schrieb Timo Sirainen: Since I switched to lmtp delivery yesterday, would it also be possible to have a different logging path for that? Nope. It would be now much simpler to implement it though. log daemon would just need to support reading/using separate config for each service. Maybe it could even be implemented in less than 50 lines of code.. Maybe an option going forward. Thanks
Re: [Dovecot] v2.0.beta3 released
Am 22.02.2010 um 18:59 schrieb Timo Sirainen: Oh, actually not. The difficult part is that Dovecot just doesn't support logging to multiple files (with same severity) in a same process. The logging code would have to be abstracted out before that would be possible. Actually I like the idea of having a separate delivery log with lmtp. Any idea?
[Dovecot] v2.0 IMAP Capabilities announcement
Hi, I have an Android Mail App which worked fine with IDLE pushes before (K-9 Mail) under 1.2.10. With 2.0 beta 3 it seems to be looking for an IDLE prompt from the server, otherwise it will disable connection idling (whether this is valid or not). Setting 'imap_capability = IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID IDLE ENABLE' does the trick, but is it possible to add additional values to the default reply like this? imap_capability = +IDLE ...or whatever syntax/form one would chose to preserve internal defaults. Thanks Thomas
Re: [Dovecot] Dovecot 2.0.beta3 Configuration issue (I think)
ssl_cert = /etc/postfix/sbh16-cert.pem ssl_key = /etc/postfix/sbh16-key.pem Try ssl_cert = /etc/postfix/sbh16-cert.pem ssl_key = /etc/postfix/sbh16-key.pem Regards Thomas
Re: [Dovecot] Dovecot 2.0.beta3 Configuration issue (I think)
Try
ssl_cert = /etc/postfix/sbh16-cert.pem
ssl_key = /etc/postfix/sbh16-key.pem
I did. It didn't make any difference.
Hmm. It does not say 'protocols = imap' in the dovecot -n output. Is it in
'dovecot.conf' and what does the 'master.conf'
service imap-login {
part look like?
Thomas
Re: [Dovecot] v2.0.beta3 released
Hi,
this is the first 2.0 build I tested, and I haven't been following the 2.0
threads very closely. This said I'm puzzled whether 'protocols = imap' does
what it should. It also enables a listener for IMAPS on port 993, different to
what 1.2 series did. I had to manually disable the IMAPS part by setting its
port to 0.
# 2.0.beta3: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.4
info_log_path = /var/log/dovecot-info.log
log_path = /var/log/dovecot.log
mail_location = maildir:~/maildir
namespace {
hidden = no
inbox = yes
location =
prefix =
separator = /
type = private
}
namespace {
list = yes
location =
maildir:/var/vmail/public:CONTROL=~/maildir/public:INDEX=~/maildir/public
prefix = Public/
separator = /
subscriptions = no
type = public
}
passdb {
args = username_format=%u /var/vmail/conf.d/%d/passwd
deny = no
driver = passwd-file
master = no
pass = no
}
plugin {
acl = vfile:/var/vmail/conf.d/%d/acls:cache_secs=300
quota = dict:user::file:%h/maildir/dovecot-quota
quota_rule = *:storage=1GB
quota_rule2 = Trash:storage=10%%
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
sieve_global_dir = /var/vmail/conf.d/%d/sieve-scripts
}
postmaster_address = postmas...@leuxner.net
protocols = imap
service auth {
unix_listener auth-userdb {
group = vmail
mode = 0600
user = vmail
}
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
}
service imap-login {
inet_listener imap {
address = xxx.xxx.xxx.xxx
port = 143
}
inet_listener imaps {
port = 0
}
}
ssl_cert = /etc/ssl/certs/spectre_leuxner_net_2009.crt
ssl_key = /etc/ssl/private/spectre_leuxner_net_2009.key
userdb {
args = username_format=%u /var/vmail/conf.d/%d/passwd
driver = passwd-file
}
verbose_proctitle = yes
Regards
Thomas
Re: [Dovecot] v2.0.beta3 released
Am 21.02.2010 um 07:16 schrieb Timo Sirainen: Yes, that's intentional. imaps isn't a protocol. Thanks Timo. Has the specific logging option for the LDA been dropped? I see it logging to 'info_log_path=' only. Regards Thomas
[Dovecot] postfix and dovecot on different systems - sasl request
Hello,
until now I have use postfix and dovecot on the same server. Now I
want/must split this both systems (server1 - postfix, server2 - dovecot).
I used dovecot auth system for postfix
## snip ##
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
## snap ##
but this does not work, if dovecot is not running on the same server.
I did not find any information in postfix/dovecot documentation, how I
could solve this problem smart.
My only idea, but it looks like quick and dirty solution:
On the postfix system a small dovecot systems runs only for postfix sasl
via /var/spool/postfix/private/auth. (Or I use saslauthd with sql or imap)
The postfix system (on server 1) delivers mails via transport map to the
dovecot system. On the dovecot system postfix delivers
this mails i.e. via
## snip ##
dovecot unix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -d
${recipient}
## snip ##
to the mail boxes.
Are there other ways, how I could solve this problem?
My wish configuration:
postfix sends the auth request via tcp/ip to the dovecot auth system and
not via a socket.
I use postfix 2.6 and dovecot 1.2.6.
Best regards,
thomas polnik.
Re: [Dovecot] listen to imap*s* on multiple ports?
Thanks for the pointer! That worked fine. Rick On Jan 17, 2010, at 9:32 AM, Pascal Volk wrote: A more recent version for Lenny is available in the lenny-backports repository: http://packages.debian.org/source/lenny-backports/dovecot
Re: [Dovecot] listen to imap*s* on multiple ports?
Pascal Volk wrote:
On 01/16/2010 03:36 AM Frank Cusack wrote:
How can I listen to ssl-wrapped IMAP on multiple ports? …
http://dovecot.org/list/dovecot/2010-January/045874.html
Please don't forget to substitute listen with ssl_listen
Regards,
Pascal
Hmmm... This doesn't work for me. My dovecot.conf has
protocol imap {
# rbt - use conventional port for imap -- only used on local net
listen = *:143
# rbt - use modified port for imaps -- for those logging in from afar
ssl_listen = *:7993
ssl_listen = *:993
}
I get:
# invoke-rc.d dovecot restart
Restarting IMAP/POP3 mail server: dovecot
Fatal: ssl_listen: Can't resolve address *:7993 , *: Name or service
not known
failed!
This is on a Debian Lenny system. The version of Dovecot installed is
1:1.0.15-2.3+lenny1
Do I need a later version?
Rick
[Dovecot] Upgrade path questions
Hi, We are currently running Dovecot v1.1.6 on our servers, and are contemplating an upgrade to 1.2, or 2.0 soon. We are wondering how many organizations are still running a 1.1 version of Dovecot, and if anyone has any thoughts on this transition. Have you upgraded from 1.1 to 1.2? What are your experiences with this? Have you upgraded from 1.1 to 2.0 directly? What are your experiences this way? We are also running an environment with both mbox and maildir formats. How many of you are running similarly, or are running solely maildir or mbox? We're just looking to gather information going forward, and anything you might be able to contribute would be very helpful. Thanks! * * Tom Goerger - Email/Unix System Administrator * * * * University of Minnesota Email: t...@umn.edu * * Operations, Infrastructure and Architecture Phone: 4-5804 * * Internet ServicesOffice: 626J WBOB* * * *
Re: [Dovecot] How to configure dovecot to listen on multiple separate port numbers
On Jan 12, 2010, at 9:18 AM, Timo Sirainen wrote:
On 4.1.2010, at 22.26, Rick Thomas wrote:
Is there any way to tell dovecot to listen for imap/imaps requests
on all interfaces on multiple separate ports?
For example, can I do this:
protocol imap {
listen = *:10143
listen = *:143
listen = *:10143, *:143
Thank you, Timo! That's exactly what I was looking for.
Enjoy!
Rick
Re: [Dovecot] How to configure dovecot to listen on multiple separate port numbers
I sent this a while ago, but got no answers. Maybe it got lost?
Thanks!
Rick
Rick Thomas wrote:
Is there any way to tell dovecot to listen for imap/imaps requests on
all interfaces on multiple separate ports?
For example, can I do this:
protocol imap {
listen = *:10143
listen = *:143
ssl_listen = *:10993
ssl_listen = *:993
...
}
Thanks!
Rick
Re: [Dovecot] First time Dovecot user, really impressed so far. What is best IMAP enabled webmail package to go with Dovecot?
On 1/6/2010 11:38 AM, Steve wrote: An advice on another nice Web enabled mail client? Have you looked at SOGo? Have a look at their online demo - http://www.scalableogo.org/tour/online_demo.html It has more to offer then RoundCube (aka: Calendaring, synchronization with Funambol, etc). Ah? (perks up ears at the mention of Funambol) And SOGo plays nicely with postfix + dovecot?
Re: [Dovecot] Dovecot not delivering mail.
Timo Sirainen schrieb: On 5.1.2010, at 13.55, Charles Marcus wrote: In other words, would you really have to remember to run dovecot -n -c per your example above? I ask because I've never used it with a config file in a non-default location. If this is correct, I would consider it a bug - dovecot -n should know which config file it is using, and outout accordingly. How would it know what config file Dovecot is using? The config file needs to be read before it even knows where the base_dir is. What if there are multiple Dovecots running? The main problem here is that Ubuntu for some reason decided to use dovecot-postfix.conf instead of the default dovecot.conf.. Depends on the package that is installed: t...@mail2:~$ apt-cache search dovecot dovecot-common - secure mail server that supports mbox and maildir mailboxes dovecot-dev - header files for the dovecot mail server dovecot-imapd - secure IMAP server that supports mbox and maildir mailboxes dovecot-pop3d - secure POP3 server that supports mbox and maildir mailboxes dovecot-postfix - full mail server stack provided by Ubuntu server team The package dovecot-postfix installs and uses dovecot-postfix.conf but unfortunately also puts the default dovecot.conf in /etc/dovecot (driving everyone crazy who blindly follows howtos editing dovecot.conf). Highly recommended to remove/rename dovecot.conf in this configuration. Thomas
Re: [Dovecot] Dovecot not delivering mail.
Pascal Volk schrieb: On 01/06/2010 02:15 PM Thomas Wolf wrote: … The package dovecot-postfix installs and uses dovecot-postfix.conf but unfortunately also puts the default dovecot.conf in /etc/dovecot (driving everyone crazy who blindly follows howtos editing dovecot.conf). Highly recommended to remove/rename dovecot.conf in this configuration. And there is big fat warning at the top of the unbuntus's dovecot.conf file: # -- WARNING --- # If there's a file /etc/dovecot/dovecot-postfix.conf, which is part of # dovecot-postfix package, it will be used instead of dovecot.conf. # Keep in mind that, if that file exist, none of the changes in # /etc/dovecot/dovecot.conf will have effect on dovecot's configuration. # In that case you should customize /etc/dovecot/dovecot-postfix.conf. # -- WARNING --- Further more, the file /usr/share/doc/dovecot-postfix/README.Debian contains: dovecot's init script checks existance of /etc/dovecot/dovecot-postfix.conf and if that file exists, it reads it instead of /etc/dovecot/dovecot.conf. Sorry, but I really can't understand, why the most unbuntu users seems to be unable to read AND understand so simple written documentation. :( I agree (that's why i wrote ..who *blindly* follows howtos). Nevertheless, renaming /etc/dovecot/dovecot.conf helps troubleshooting while using dovecot-postfix (forgetting -c when using deliver elsewhere for example) Thomas
Re: [Dovecot] Dovecot not delivering mail.
Literally, in a recent case with me. Debian (any build I could get my hands on, I tried quite a few) would literally not install on a box. I was lucky if the installer ran, let alone did anything. Spent a week trying. Ubuntu installed on the first try and was up and running after fifteen minutes. Thomas Berezansky Merrimack Valley Library Consortium Quoting Jerry ges...@yahoo.com: On Wed, 06 Jan 2010 14:41:32 -0200 Eduardo M KALINOWSKI edua...@kalinowski.com.br articulated: On Qua, 06 Jan 2010, Pascal Volk wrote: Sorry, but I really can't understand, why the most unbuntu users seems to be unable to read AND understand so simple written documentation. :( flamebait If they could, they'd be running debian. :-) /flamebait Ubuntu is an ancient African word meaning, I can’t install Debian. -- Jerry ges...@yahoo.com
Re: [Dovecot] First time Dovecot user, really impressed so far. What is best IMAP enabled webmail package to go with Dovecot?
On 1/4/2010 4:00 PM, Stan Hoeppner wrote: Greetings everyone, I'd like to install a webmail package on the same host. I used Squirrelmail for this purpose many years ago and I wasn't wholly impressed with the user interface. I'm also not impressed by the fact that I regularly receive spam from compromised Squirrelmail hosts/accounts. I really like the look/feel of the Scalix Web Access AJAX based interface, but I can't/won't use Scalix as it's not supported on Debian, it has more features than I need, and the system requirements are a bit steep. SquirrelMail or RoundCube. We have SM setup currently and I plan on setting up RoundCube sometime in January.
Re: [Dovecot] First time Dovecot user, really impressed so far. What is best IMAP enabled webmail package to go with Dovecot?
On 1/5/2010 1:32 AM, Ken Price wrote: If this is more than a hobby system, then you'll need to account for address books and personal settings for your users - at the least. That means some sort of backend database. I've been looking at Funambol lately to support some Blackberry users (we're not running BES). If I understand it correctly, it will let us sync our TBird address book (and Lightning Calendar/Tasks) to the Blackberry and possibly to additional copies of Thunderbird. http://www.funambol.com/ (I've also been looking at some of the groupware solutions like SoGo.)
Re: [Dovecot] Dovecot not delivering mail.
Charles Marcus schrieb: Question: if you use an alternate location for the config file, and start dovecot with that config file properly, does plain 'dovecot -n' output what is in the config file that is in use? Or the one in the default location? It's the default location: t...@mail2:~$ pgrep -lf dovecot 28900 /usr/sbin/dovecot -c /etc/dovecot/dovecot-postfix.conf 28901 dovecot-auth t...@mail2:~$ dovecot -n # 1.1.11: /etc/dovecot/dovecot.conf Error: Can't open configuration file /etc/dovecot/dovecot.conf: No such file or directory Fatal: Invalid configuration in /etc/dovecot/dovecot.conf t...@mail2:~$ Thomas
Re: [Dovecot] Kernel warnings
* Noel Butler, 2010-01-02 12:15 On Sat, 2010-01-02 at 09:45 +0100, Thomas Zajic wrote: Dovecot versions involved were/are 1.2.x, I'm currently at 1.2.9. My system is running Slackware 13.0, but this also happened with 12.2. We run Slackware (yes currently 13.0, and with custom kernels since donkies years ago)... I have never seen this on any of the servers. Yeah, same here, going back to Slackware 3.4 or something ... oh well. Thanks anyway, Thomas
Re: [Dovecot] Kernel warnings
* Timo Sirainen, 2010-01-02 17:48 On 2.1.2010, at 3.45, Thomas Zajic wrote: [c1095367] ? inotify_free_group_priv+0x12/0x21 [c1093c81] ? fsnotify_final_destroy_group+0x16/0x1e .. There are no processes other than dovecot's imap that are ever causing these warnings. Does this indicate a problem in the kernel or rather in dovecot? Yes. Hehe ... okay, so which one is it? :-) I don't even know what exactly to make of this warning - obviously, there may be a potential memory leak related to inotify and dovecot's imap process, but is it 1. a bug in the kernel that is triggered by something that dovecot's inotify code does, or 2. a bug in dovecot's imap that the kernel notices and warns about as of 2.6.31 (but didn't notice and/or warn about in 2.6.30 and earlier)? The reason why only imap process creates these is because it's probably the only process using inotify. You could of course compile Dovecot without inotify support, but that's just a workaround.. Hmmm ... I don't mind the warning as such, as it doesn't have any actual bad side effects as far as I can tell, I'm just curious as to what causes it. Is there anything related I should/could tune in /proc/sys/fs/inotify? [r...@airframe]:~# grep -r . /proc/sys/fs/inotify /proc/sys/fs/inotify/max_user_instances:128 /proc/sys/fs/inotify/max_user_watches:65536 /proc/sys/fs/inotify/max_queued_events:16384 [r...@airframe]:~# Bye, Thomas
Re: [Dovecot] Kernel warnings
* Timo Sirainen, 2010-01-03 22:54 On 3.1.2010, at 9.12, Thomas Zajic wrote: 1. a bug in the kernel that is triggered by something that dovecot's inotify code does, or Yes. Is there anything related I should/could tune in /proc/sys/fs/inotify? Probably not. I'd ask about this in your distro or kernel mailing list. Okay, will do. Thanks! Bye, Thomas
[Dovecot] Kernel warnings
Hi, I've been getting these warnings in syslog since I've been running (Linux) kernels 2.6.31.x and up (I'm currently at 2.6.32.2), they do not show up on 2.6.30.x kernels. Dovecot versions involved were/are 1.2.x, I'm currently at 1.2.9. My system is running Slackware 13.0, but this also happened with 12.2. [ cut here ] WARNING: at fs/notify/inotify/inotify_fsnotify.c:129 idr_callback+0x2a/0x4b() Hardware name: To Be Filled By O.E.M. inotify closing but id=0 for entry=f61e3334 in group=f254ce00 still in idr. Probably leaking memory Modules linked in: tcp_diag inet_diag autofs4 nfsd lockd nfs_acl sunrpc exportfs ipv6 w83627hf hwmon_vid hwmon lp fuse parport_pc 8250_pnp rtc_cmos 8250 parport rtc_core serial_core rtc_lib ohci_hcd button thermal processor evdev e1000 psmouse serio_raw i2c_i801 ide_cd_mod sg i2c_core cdrom ehci_hcd Pid: 10837, comm: imap Not tainted 2.6.32.2 #1 Call Trace: [c1024368] ? warn_slowpath_common+0x5e/0x8a [c10243c6] ? warn_slowpath_fmt+0x26/0x2a [c10953a0] ? idr_callback+0x2a/0x4b [c10ed1c5] ? idr_for_each+0x5a/0x91 [c1095376] ? idr_callback+0x0/0x4b [c1095367] ? inotify_free_group_priv+0x12/0x21 [c1093c81] ? fsnotify_final_destroy_group+0x16/0x1e [c10954dc] ? inotify_release+0x16/0x22 [c1072f76] ? __fput+0xc0/0x163 [c1070a90] ? filp_close+0x4e/0x54 [c1070afc] ? sys_close+0x66/0x9c [c10028b5] ? syscall_call+0x7/0xb ---[ end trace a2df6cbeb716721c ]--- entry-group=(null) inode=(null) wd=1024 There are no processes other than dovecot's imap that are ever causing these warnings. Does this indicate a problem in the kernel or rather in dovecot? The system appears to run fine except for the warnings, no actual crashes, asserts, core dumps or similar in any of dovecot's components. Mandatory 'dovecot -n' output: [r...@airframe]:~# dovecot -n # 1.2.9: /usr/local/etc/dovecot.conf # OS: Linux 2.6.32.2 i686 Slackware 13.0.0.0.0 login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login mail_max_userip_connections: 20 verbose_proctitle: yes mail_location: maildir:~/Maildir:INBOX=~/Maildir/.INBOX fsync_disable: yes mail_process_size: 2048 mail_plugins: expire fts fts_squat auth default: mechanisms: plain digest-md5 cram-md5 passdb: driver: passwd-file args: /usr/local/etc/dovecot-passwd userdb: driver: passwd socket: type: listen master: path: /usr/local/var/run/dovecot/auth-master mode: 384 plugin: expire: Trash 7 Junk 1 expire_dict: proxy::expire fts: squat fts_squat: partial=4 full=6 dict: expire: mysql:/usr/local/etc/dovecot-dict-sql-expire.conf [r...@airframe]:~# Thanks A Happy 2010, Thomas
Re: [Dovecot] architecture to handle 1000 messages per second?
Hello, Actually, thousands of customers would send order emails to a system running postifx. All orders end up in ord...@example.com. Then, another app fetches these emails via Dovecot (POP or IMAP), ideally at the rate of 1000 per second. I think it might be difficult to accomplish this via POP since I think Dovecot would have to lock the account while doing the POP downloads. This makes it difficult to have more than one app downloading at a time. Cheers, Bob Hi Bob, Thanks for the explanation. I would seriously consider delivering the incoming messages to a script/program for further processing, instead of adding a POP3/IMAP layer. Postfix is well suited for to do just that. I simply cannot come up with a single good reason for wasting resources by stuffing an POP3/IMAP server in there, especially when it's so easy to configure Postfix to deliver to a command. :o) /Thomas
Re: [Dovecot] architecture to handle 1000 messages per second?
On Fri, Jan 1, 2010 at 11:23 PM, Bob Eastbrook baconeater...@gmail.comwrote: On Fri, Jan 1, 2010 at 2:09 PM, Bob Eastbrook baconeater...@gmail.com wrote: Can anyone describe an architecture which can handle 1000 IMAP or POP messages per second? Ideally, it would be hosted in the cloud and additional instances could be launched to handle additional load. More information: imagine an app which processes orders for concert tickets via email. The app connects to a server via POP or IMAP, downloads orders, and then deletes them from the server. There aren't thousands of users simultaneously accessing and searching their mail, but rather only one account (ord...@example.com) but thousands of emails per second. Ideally, it could be cloud hosted so that instances could be launched before tickets go on sale. Instances can be shut down after the rush. Hi Bob, Just to make sure I understand you: Some app is sending emails to ord...@example.com at the rate of 1000 per second, and another app is fetching email from ord...@example.com to process them? Regards, Thomas Løcke
Re: [Dovecot] A Dovecot Sieve spam filter question.
On 12/30/2009 2:21 PM, aja-li...@tni.org wrote:
Hi,
I'd like to make a filtering threshold for users to let them
deal with spamassassin spam-level starred 8 themselves,
but spam-level starred higher than 8 should be discarded
In general, it's better to quarantine high-scoring spam (we shove it in
a server-side Junk folder) then to simply discard. (The old adage of
mail delivery is that once you accept delivery of mail into your system
you should never silently drop it on the floor.)
require [comparator-i;ascii-numeric,fileinto,relational];
# Definite spam gets shoved into the Junk folder in IMAP
# Currently defined as a Spam Assassin score of 8.0 or higher
if allof (
header :contains X-Spam-Flag YES,
header :value ge :comparator i;ascii-numeric [X-Spam-Score] [8]
) {
fileinto Junk;
stop;
}
You need to check both that the spam flag is set to YES in addition to
doing a comparison on the value of the spam score header. Otherwise
you'll find that spams with negative scores can confuse the comparison rule.
This script is in a central sieve file that we include from the
individual user's home folders. We always make sure that it's the
*first* include in the user's file (after the require lines) so that
we get a chance to stop processing on spam messages before processing
things like vacation responses.
Basically, we score and tag at 5.0 - putting [SPAM] into the subject
line, and leave the message in the Inbox. But for stuff over 8.0, we
move it server-side to the Junk folder. This gives the users a lot of
flexibility. If they don't trust our filter, then can look at the
maybe spam messages in their Inbox and also look in the Junk folder.
If they're not worried about false-positives in the 5.0-7.9 range, then
they can setup a client side rule to simply move the messages from the
Inbox to the Junk folder, or delete them.
We also have a server-side cron script that runs daily and removes any
files in Junk that are older then 90 days.
Re: [Dovecot] A Dovecot Sieve spam filter question.
On 12/30/2009 5:56 PM, aja-li...@tni.org wrote:
On 12/30/2009 10:08 PM, Andrzej Adam Filip wrote:
As I understand :contains tests presence of the sub-string
= so you can test 'at least n consecutive stars present' ('n stars OR
more')
Okay, thanks, after some searching I see that quite some people
apparently have this working successully, for example here :
http://www.cs.uchicago.edu/info/services/imap/sieve
But this (2nd line is one long line) :
require [fileinto];
if header :contains X-Spam-Level
** {
fileinto Junk;
}
simply delivers the gtube test email in the Inbox instead of the Junk
folder :( No errors in the dovecot-deliver log, what am I missing ?
Probably because after filing it into the Junk folder you also want to
issue a stop; statement to prevent further down rules from firing.
{
fileinto Junk;
stop;
}
(It's a common error that I make all the time.)
Re: [Dovecot] User friendly vacation service
I solved that problem (granted, with virtual domains) by using the dovecot managesieve support and Horde ingo. Any sieve management tool should able to do it, though, we were using Horde for webmail already so rigging ingo to do filters wasn't hard. No experience outside of ingo with this stuff, but ingo itself integrates a vacation rule in quite nicely. There are a pile of other solutions for managing the scripts through the managesieve interface, so finding one that works for you shouldn't be too hard. Thomas Berezansky Merrimack Valley Library Consortium Quoting Raymond Lillard rlill...@sonic.net: Dear Dovecot list, I maintain a few small sendmail/dovecot/procmail based mail servers with system users only (no virtual domains or virtual users) on OpenBSD. I have been able to get a vacation system working with both with the native vacation program from OpenBSD and with procmail. I've been looking into dovecot sieve, but it doesn't appear to solve the bigger user complaint which is, they want to be able to control the vacation feature w/o my involvement. What is wanted is a system where the users can send a control mail message to themselves with the reply body in the message or failing that perhaps a secure web page to control the vacation function. Mail administration is NOT a full time job for me. I'm looking for simple, low overhead solutions. Any suggestions? Thanks for your time. Ray
Re: [Dovecot] Spam filtering (was: Re: Sieve mails with decoded subject)
On 12/10/2009 2:28 PM, Johannes Bauer wrote: Eduardo M KALINOWSKI schrieb: On Qui, 10 Dez 2009, Johannes Bauer wrote: I'm thinking about filtering all such encoded subjects (as there's no reason to encode them US-ASCII), but suppose it were UTF-8 or something: how can I filter on the actual content, not the encoded subject? Surely someone has solved that problem already? Yes, such as the guys behind SpamAssassin, or dspam, or any of the many spam filtering programs that exist. Actually, they make much more complicated decisions instead of only looking for bad words in the subject field. I'd suggest you try installing one of them. I had SpamAssassin running once and was pretty disappointed. All those complicated rules and scoring and smart bayesian filtering did not work very well, although I taught it in around 50k mails right from wrong. I had both lots of false-positives and lots of false-negatives, which was kind of annoying. However, analyzing 274 spam mails I deleted in the last 5 months I can conclude that by using that extremely simple filter list I'd catch 258 of them (that's 94%). So I'd like to stick to KISS in this case. From what I've seen, SA has been extremely good and accurate for us. We use amavisd-new to interface, but SA is at the end of a long chain of checks. Between the (3) HELO checks, clamav-milter, and a SPF policy daemon, we're killing ~60% of all connections at SMTP time. (I analyzed that in November, instead of 65/day hitting my inbox I would've seen 6x that amount if it wasn't for those checks. So ~80% of all spam was getting blocked at SMTP time.) If we were to pay for the Spamhaus Zen list, we could probably boost that percentage to 90%. All of the domains we do business with get a -2 or -4 score using amavisd-new. Specific addresses get a larger negative score. I ran a few thousand spam ham messages at the SA bayes filter, then turned it on. We tag messages with a [spam] flag at 5.0 and quarantine at 9.0. Tagged messages go to the user's Inbox, quarantined messages get sieve'd into a sub-folder in the user's mailbox. So far (in a month), no false positives. Or at least none that people have complained were quarantined when they should not have been. I'm considering lowering the quarantine threshold next month. It's been nice to have my Inbox back, without 65 spams/day cluttering it up. Now I might see 2-5 per day that slip through without getting tagged as borderline spam (at 5.0 or higher). Those are mostly zero-day spam that haven't made it to the URIBLs or DNSBLs yet. I'm still debating grey-listing, Razor, DCC or paying for the Spamhaus Zen list. Compared to another, commercial, product that we were using a few years ago, SA is very very good. Not perfect, but really does a good job of classifying things with decent accuracy.
Re: [Dovecot] busy / developers documentation
On Tue, Dec 01, 2009 at 05:39:55PM -0600, Timo Sirainen wrote: Just thought I'd mention that I probably won't be answering mails very actively this week while I'm in San Antonio (and I was kind of busy last week too). Hopefully I'll get back to answering/bugfixing next week.. I also started writing developers documentation to http://wiki.dovecot.org/Design. Comments welcome. Some things I had planned next: - istream internals - lib-storage API docs - ..? Hello Timo, Just an idea talking about writing documentation : When I looked at the authentication code (using LDAP) back in the 1.1 version, it took me some time to understand the function call cascading, especially with the callback/context mechanism which I found clever but hard to follow. I came to the understanding (hope I was right) that you were using some kind of layered architecture, which went something like this : low level ldap_request level passdb_ldap_request level auth_request level auth_request_handler level auth_client_connection level high level where : . passdb_ldap_request == passwd checking . auth_request == parameters (user, password, state) and internal management of the request . auth_request_handler == building of the answer of the request . auth_client_connecion == sending to the authentication client (imap-login) ... . callback : a pointer in a lower level to a function in an higher level . context : what links objects of those layers eachother I was thinking that, if my understanding is correct, some overview from you of such an architecture would be of great help for those who want to understand the code. Thanks. -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
Re: [Dovecot] different views of a imap account
On 12/2/2009 6:21 PM, Ajaxster wrote: Hi, I've looked around a few times to see if I could figure the answer to this question but I think I may not know the right question to ask... The scenario I have is that I'm running dovecot, exim and procmail on one server (using maildir storage) and also have apache on another server. I can run squirrel mail, roundcube, etc. all on the web server and access all my email just fine. I can run outlook or thunderbird or other imap clients just fine too. I have some smart phones that support imap mail servers, but when I set them up to connect to my server, the client seems to have to sync up data on all the mailboxes (lots of headers to download). All I really want on my remote (phone based) imap clients is to view my inbox. I believe that the subscriptions are done globally in that every client sees the same subscriptions, so that doesn't seem like the way to narrow down what my phone imap clients see. On my HTC Touch Pro (Windows Mobile), it has its own idea of what the folder subscriptions are and doesn't track the IMAP subscription info. Which is good, because it chokes on my archive folders with a few thousand messages per year. So I'm able to tell it to only look at Sent Inbox without messing up the subscriptions on the other IMAP clients that also access that mailbox. My other suggestion... split your high volume folders out to a 2nd IMAP account.
[Dovecot] Dovecot SSL limitations
Hello Timo, I'd like to check if my understanding of dovecot-1.2.x's SSL certificate handling is correct : SSL does not provide the server any mechanism to choose which certificate it must send relatively to the name the client is using. Thus, if you want to use different certificates, you have to listen to different addresses. This is an SSL limitation, not a dovecot nor IMAP limitation. This is the reason why it's possible to use different certificates for IMAP and POP3. But it seems to work only with those two : As a matter of fact, even if you listen to different addresses, how would you tell dovecot to send this certificate for this address and that certificate for that address, since there is no IP dependent section (as in apache IP-based virtual host for instance) ? It seems the only way would be to have more than one instance of dovecot (several dovecot with different config files). The problem is that some clients may be configured with mail.my.domain, some others with imap.my.domain, ...etc... Hence the need to have different certificates with those different names as cn. -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
Re: [Dovecot] Dovecot SSL limitations
On Mon, Nov 30, 2009 at 03:50:00PM +, Jose Celestino wrote: The client compares the CN of the certificate with the hostname it has configured and warns on a mismatch. What you can do is have multiple subjects certificate, that is a certificate again with a single CN but with multiple alt subjects that should cover all the names that server may have. The client should support those kind of certificates, of course. Thanks. You're not talking about wildcard certificate, aren't you ? -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
Re: [Dovecot] /var/run/dovecot mode 750 too tight
Am 29.11.2009 um 19:24 schrieb Frank Cusack:
dovecot-1.2.8 creates /var/run/dovecot mode 750.
I run postfix+dovecot in a virtual user setup. Postfix calls deliver
as user vmail group vmail.
Nov 29 12:53:04 imap.invalid dovecot: [ID 583609 mail.error] deliver(frank):
userdb lookup: connect(/var/run/dovecot/auth-master) failed: Permission
denied (euid=500(vmail) egid=500(vmail) missing +x perm: /var/run/dovecot)
I will say this: dovecot's error reporting in general is head and shoulders
above the norm. Makes tracking down problems sooo much easier.
Something else I noticed, should the dict-server socket really be mode 777?
At least a-x I would think.
-frank
Probably easier to tell if you would post your setup, but I guess this fixes it:
socket listen {
master {
path = /var/run/dovecot/auth-master
mode = 0600
user= vmail
group = vmail
}
Regards
Thomas
Re: [Dovecot] /var/run/dovecot mode 750 too tight
Am 29.11.2009 um 20:31 schrieb Frank Cusack: dovecot-1.2.8 creates /var/run/dovecot mode 750. I run postfix+dovecot in a virtual user setup. Postfix calls deliver as user vmail group vmail. Nov 29 12:53:04 imap.invalid dovecot: [ID 583609 mail.error] deliver(frank): userdb lookup: connect(/var/run/dovecot/auth-master) failed: Permission denied (euid=500(vmail) egid=500(vmail) missing +x perm: /var/run/dovecot) So it can't access that directory as it states. It would create that structure upon start to my knowledge. Mine is [20:38] root spectre:/# l -d /var/run/dovecot drwxr-xr-x 3 root root 4096 2009-11-25 13:20 /var/run/dovecot What is yours? Regards Thomas
Re: [Dovecot] Vacation message with Sieve
On 11/24/2009 6:27 AM, Charles Marcus wrote: On 11/23/2009, Patrick Nagel (patrick.na...@star-group.net) wrote: Yes, that was my first proposal, but that was also rejected harshly by the other project managers. They wanted to have some transit time in which the replacement guy would still access the leaving guy's mailbox. They felt that just deactivating the mailbox and rejecting mails would be rude. 1. Add an alias to the x-managers account that forwards all incoming mail to his replacement, or 2. Add the x-managers account to your replacements email client, so they can check it as well as theirs. 3. (slightly different) Have the vacation auto-reply set and also use the sieve redirect method after the vacation message gets processed? redirect :copy newmana...@example.com; New manager gets the email, clients get a hey, I retired but these folks over here will also get a copy of your message and will help you message. 90% sure you can do that (vacation is supposed to be compatible with redirect)... I'll have to try it the next time that someone retires around here. Eventually (30-90 days), we turned off the redirect and changed the vacation message. You'll want a very good server-side spam filter with aggressive quarantine levels for that user if you're going to have a long-running vacation reply in place. That'll avoid the vacation script replying to every joe-jobbed message that makes it into the mailbox. The sooner that you can start returning 5xx codes for the old address the better (IMHO). (Still doesn't address the issue of more then one per day, but you'd have to complain about that to the folks who wrote RFC 5230 who specify that :days has to be greater then zero.)
Re: [Dovecot] Vacation message with Sieve
Fire the new manager, eh? Now you need to keep TWO old addresses working for the same position! Stop compounding the issue! ;) Thomas Berezansky Merrimack Valley Library Consortium Quoting Charles Marcus cmar...@media-brokers.com: On 11/24/2009, Patrick Nagel (patrick.na...@star-group.net) wrote: 2. Add the x-managers account to your replacements email client, so they can check it as well as theirs. 2. is what we did. In either case you could also enable the vacation message notification if you like, but once per day is plenty in this case since someone else is (or should be) reading the mail). Well, as I said, they weren't satisfied with that. So, the guy who is replacing the x-manager has direct access to the guys email and all incoming messages, but is refusing to accept the responsibility for it? Fire the new manager would be my next step. :)
Re: [Dovecot] Newbee, some questions
On 11/22/2009 12:39 PM, Spyros Tsiolis wrote: Due to reasons beyond me (mainly my clients demanding more for their buck / things like webmail etc.), I was forced to start searching for (always) open source alternatives. We used Postfix only for a long time (SMTP/POP3), back in '07 I started researching, built a test rig in early '08 and we switched full over to Postfix/Dovecot in late spring of '08. You'll have a lot of reading ahead of you and I recommend registering a domain or two to use as a test bed on the new system before you start adding the real domains and repointing MX records at the new box. 1. Do multiple domain handling. This can be done with virtual domains and users. We found it easier to go with virtual users instead of system users for our multi-domain setup. http://wiki.dovecot.org/VirtualUsers http://wiki.dovecot.org/SystemUsers Personally, we use PostfixAdmin (a web-based tool) along with its databases (in PostgreSQL) to store our virtual domains and to manage domains/accounts. Our Postfix (which handles the SMTP side) and Dovecot (which handles the POP3/IMAP side) query this database for domain/user information. We used to use a system users setup, which had the advantage (and disadvantage) that Fred could receive email as f...@anyofourdomains without having to do anything special. With the virtual user setup, we had to put fred@ into one domain, and then setup aliases in the other domains that rewrote f...@otherdomain into f...@homedomain. In the long run, I'm happier, because most of our users really didn't need to be addressable as u...@anyofourdomains. 2. Have a centralized user base 3. Have a centralized mail repository for each user (like exchange, only without the admin/maintenance pain that comes with it) We store user email in Dovecot's Maildir setup, usually under: /var/vmail/domain/user/ There are lots of sub-folders below that point specific to the MailDir implementation. I personally have IMAP mailboxes with hundreds of thousands of messages spread across dozens of folders and a total size of over 2GB. 4. be able to do IMAP/POP3 and not SMTP/POP3 (or do I need all three of them ?) SMTP servers (postfix, sendmail) handle accepting mail from the outside world before handing it off to a LDA (local delivery agent) like Dovecot. The SMTP server also handles taking mail from a mail client (submitted via SMTP) and either handing it to the LDA for local delivery or contacting foreign SMTP servers to deliver to other domains. (Postfix also has an LDA component, and a POP3 component, but you can plug other LDA servers in like Dovecot.) POP3/IMAP access to the mailbox location is usually the job of Dovecot. 5. Interface with things like web-based mail software (LAMP ?) We use SquirrelMail here for our webmail. I'm pretty sure that it talks to the Dovecot IMAP server in order to access the user's mailbox. Once you have IMAP access to your mailboxes configured, you can use lots of different tools to talk to it.
Re: [Dovecot] Vacation message with Sieve
On 11/23/2009 7:19 AM, Rene Bakkum wrote: Hello all, I am trying to get my vacation messages to work correctly. In general it works like how I want, and replies when a message is arived to for example i...@domain.com, but I have some problems to get my vacation message to work on catch-all boxes. Is there an option to for example auto-reply on every mail that is sendto @domain.com? As stated by Pascal, catch-all addresses are evil. Especially when the spammers do a dictionary attack run against your domain (you'll get messages for a...@example.com, a...@example.com, a...@example.com...). In our setup, we specify multiple addresses as: :addresses [na...@example.com, na...@example.com, na...@example.com] (For the few people that we allow inbound mail via multiple aliases.) I understand the desire to have a catch-all address, I used to do it myself a few years ago. But the aggravation eventually caused me to reevaluate whether it was worth all of the dictionary attack spam. So I setup aliases in postfix for all of the addresses that I was truly interested in monitoring and simply 5xx unknown user the rest of them.
Re: [Dovecot] Newbee, some questions
On 11/23/2009 2:12 PM, /dev/rob0 wrote: On Sun, Nov 22, 2009 at 01:55:22PM -0500, Thomas Harold wrote: We used Postfix only for a long time (SMTP/POP3), ... Um, no, Postfix does not serve POP3. Thanks for catching that. I wonder what the Solaris admin was using to serve up POP3 access to the mbox files? Maybe it was qpopper, that sounds familiar... (I'd have to dig back through my SSH session log files to know for sure.)
Re: [Dovecot] [OT] preferred clients
Wait, what? I have, right now, a HTML message open, from an IMAP server, in Outlook 2007. Where did you hear that it wouldn't? Thomas Berezansky Merrimack Valley Library Consortium Quoting Charles Marcus cmar...@media-brokers.com: On 11/22/2009, Seth Mattinen (se...@rollernet.us) wrote: They finally added the ability to set a sent items folder on the IMAP server rather than using stupid tricks to copy it over, so that's a plus. The fact that it can't delete by moving a copy to a deleted items folder still bugs me enough that I won't use it. No idea about the PST size thing though, never got that far. One thing that is ridiculous about 2007 is it won't display HTML messages on IMAP servers... probably related to their totally BRAIN-DEAD decision to use the WORD HTML rendering engine instead of the IE rendering engine. I understand that in spite of a huge number of complaints about this, they did not fix this issue in Outlook 2010...
Re: [Dovecot] [OT] preferred clients
Hi Jonathan, I'm getting tired of Thunderbird telling me I have unread messages in folders that haven't gotten new messages for months so I'm looking for a new mail client. [..] Yes, it's a Thunderbird issue only. Usually that appears when you don't compact your folders (you can ask TB to compact by itself as well). 90% of the time when you have weird stuff in your folders that's because you didn't compact your folders. http://kb.mozillazine.org/Duplicate_messages_received http://kb.mozillazine.org/Thunderbird_:_Tips_:_Compacting_Folders Cheers, Thomas
Re: [Dovecot] [OT] preferred clients
Re, As someone else noted it may be related to the amount of email I have. I probably have nearly 100,000 messages spread across 30-40 folders right now. Close TB. Delete your .msf to recreate indexes. Start TB again and let it re-index (it will take a while). Then everything should be fine. If not do a bug report. Cheers, Thomas
Re: [Dovecot] [OT] preferred clients
On 11/20/2009 12:59 PM, Jonathan wrote: I'm getting tired of Thunderbird telling me I have unread messages in folders that haven't gotten new messages for months so I'm looking for a new mail client. I know the problem lies with Thunderbird because everything is fine via RoundCube and if it tell Thunderbird to rebuild it's index it shows the folder correctly again. Except of course for a subset of the messages in my inbox that it insists where delivered at the exact time I re-indexed it, every time. I'm currently testing out the Thunderbird 3.0 release candidates... overall, it's better then TB 2 was at IMAP. Overall, I'm pretty happy with version 3 and how it deals with my multi-gigabyte IMAP mailboxes with dozens of folders. Stability seems to be better then it was in TB v2 in terms of indexing and downloading messages. (That comes with a huge caveat, however. Beta 4 introduced some rather severe bugs in IMAP performance which have yet to be fixed as of RC1 build #2. I'm hoping that this coming week there will be another more stable build.)
Re: [Dovecot] [OT] preferred clients
On 11/20/2009 1:51 PM, Thomas Berezansky wrote: Personally, I am using Horde (http://www.horde.org/) at work (this address) and Outlook 2007 at home (largely due to getting freaky attachments I need to open on a regular basis that only Microsoft mail clients seem to be able to open properly). Out of morbid curiosity... how good is Outlook 2007 at IMAP? I've had experience with Outlook 2003 and the 2GB PST limit was a deal breaker for me. I'm curious whether Outlook is getting better or worse at IMAP. (In OL2003, they introduced a better PST format that was no longer limited to 2GB. But you can't use it with IMAP accounts. It also had weird behavior like deleting messages would not make them vanish from the folder until you did some sort of compact operation.)
Re: [Dovecot] [OT] preferred clients
On 11/20/2009 2:16 PM, Charles Sprickman wrote: We're talking about a mailbox with two or more users always in it and around 40K messages across a few hundred folders. The scale of it all seems to be part of the issue I think. I run TB v2 on my laptop and TB v3 betas on my desktop. I've not seen messages suddenly getting marked as unread. My mailing list mailbox subscribes to a few dozen mailing lists, so most folders have between 1k and 25k messages in them (about 2GB of mail). The postmaster mailbox routinely has folders with 40-50k messages in a single folder (error reports, mailbox size is up around 2GB at the moment). We're using a MailDir storage format, Dovecot 1.1.6 with Postfix on the front end. All running on top of CentOS 5. (Biggest problem I've had with TB v2 is that it sometimes loses track of the server after a while, so you'll go to send a new message and it will get stuck trying to talk to the server.)
Re: [Dovecot] [OT] preferred clients
On 11/21/2009 9:42 PM, Jonathan wrote: Do you know anything about the date issue I mentioned where TB shows emails with a date of the last time the folder was indexed instead of when the email was actually delivered? I've seen that bug, I generally either reindex / compact or completely unsubscribe and then resubscribe to the folder after restarting TB v2. I don't think I've seen it on the TB 3 side in the past 6 months since I started with beta 2. There's been a lot of work as well on indexing in Beta 3/4 when they introduced gloda (the global indexer). (I severely abuse TB, having folders with 50k messages in them, subscribing to dozens of mailing lists... good thing that I'm the mail admin and don't have to worry about quotas.)
Re: [Dovecot] [OT] preferred clients
On 11/21/2009 9:54 PM, Jonathan wrote: Okay, that didn't take long. I have another spurious unread message already. Should I do what it says here [1] and grab a nightly build and create an entire new profile, or should I just report with what I have? Any suggestions on what component to file the report against? If you decide to use the nightly, start with a new profile and try either (wait a day and I think we'll see a build #3 for RC1): http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/3.0rc1-candidates/build2/ or http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/2009-11-21-03-comm-1.9.1/ Thunderbird 3.0 is based off of Comm-1.9.1, the previews for Thunderbird 3.1 are Comm-1.9.3. The nightly builds for 1.9.1 seem to happen in the early morning hours. As for which component... I'd say either Mail Window Front End or Mail Reader UI. https://bugzilla.mozilla.org/describecomponents.cgi?product=Thunderbird You'll probably have to catch it in the act while logging is turned on. https://wiki.mozilla.org/MailNews:Logging You may also want to rule out hardware issues such as flaky memory, which could be causing corruption in the indexes.
Re: [Dovecot] Dovecot and SATA Backend
On 11/16/2009 8:00 AM, Nicolas GRENECHE wrote: Hi all, I plan to run a dovecot IMAPS and POPS service on our network. We handle about 3 000 mailboxes. I thought first buying a topnotch server (8 cores and 16 Go RAM) with equalogic iSCSI SAN SAS 15K for storage backend. We run about 300 mailboxes, ~1 to 1.5 million inbound connections per month and about 1-1.5 million messages delivered to Dovecot per month on a low-end server. The O/S drive is 10k RPM SATA and the MailDir folders are stored on a 4-disk RAID-10 7200rpm SATA. It's a dual-core, ~2GHz, 64bit CentOS 5 server with only 4GB RAM. We also do anti-virus and spam filtering (SpamAssassin) scoring on that system along with using it for a few other tasks. The system chugs at times (during the daily backup window) but otherwise I'd say we're at about 25-30% load currently. Fortunately, providing basic mail service isn't that system intensive. I think your sizing issue is going to be more about how many messages per month you're pushing through the system then sheer number of mailboxes. And maybe the overall size of the mail store. (Heck, our old mail server was a Solaris 200MHz x86 box with 256MB RAM and a pair of 80GB IDE drives setup before I took over administration of the mail system.) Our current server was a test case that we put in about 18 months ago. Hopefully next year we can upgrade to better equipment (more cores, more memory, and more and faster spindles). And maybe some HA stuff like DRBD and Heartbeat.
Re: [Dovecot] [OT] preferred clients
Didn't notice that my reply to this didn't include the list (the default reply option due to having my address directly was to sender, not to list due to a local setting). Only noticed after the fact. My response: One of my IMAP folders has over 13000 messages and is handled fine, but I am not currently sure how much actual space that is taking up right now. I suspect it isn't even half a GB. However, Microsoft states (http://support.microsoft.com/kb/830336) that Outlook 2007 doesn't use the 2GB limited format for anything by default, and that the default limit is 20GB as a result, likely with registry options to allow it to grow larger. The only issue I see with deleting messages doesn't make them go away is that delete on an IMAP account is flag as deleted by default, which means you need to issue an IMAP purge command. As I don't use trash folders I prefer this behavior, even in Thunderbird and Horde. I just add the purge commands to my toolbar. I think the flagged as deleted thing is what you are thinking about with the some sort of compact operation, and is technically how IMAP is supposed to handle deletes. For that issue, there is a Purge items when switching folders while online option, per account, that can be enabled. Also, the showing of deleted items is optional (when shown they, in all clients I have used, have a strike-through applied to them). Thomas Berezansky Merrimack Valley Library Consortium Quoting Thomas Harold thomas-li...@nybeta.com: On 11/20/2009 1:51 PM, Thomas Berezansky wrote: Personally, I am using Horde (http://www.horde.org/) at work (this address) and Outlook 2007 at home (largely due to getting freaky attachments I need to open on a regular basis that only Microsoft mail clients seem to be able to open properly). Out of morbid curiosity... how good is Outlook 2007 at IMAP? I've had experience with Outlook 2003 and the 2GB PST limit was a deal breaker for me. I'm curious whether Outlook is getting better or worse at IMAP. (In OL2003, they introduced a better PST format that was no longer limited to 2GB. But you can't use it with IMAP accounts. It also had weird behavior like deleting messages would not make them vanish from the folder until you did some sort of compact operation.)
Re: [Dovecot] [OT] preferred clients
Personally, I am using Horde (http://www.horde.org/) at work (this address) and Outlook 2007 at home (largely due to getting freaky attachments I need to open on a regular basis that only Microsoft mail clients seem to be able to open properly). Horde is a webmail client, and works well in Firefox (where you can open the left hand menu in a sidebar separate from your tabs). I install it with the calendar, notes, tasks, etc included and we tell our users to log into it in order to change their passwords. Thomas Berezansky Merrimack Valley Library Consortium Quoting Jonathan jonat...@kc8onw.net: I'm getting tired of Thunderbird telling me I have unread messages in folders that haven't gotten new messages for months so I'm looking for a new mail client. I know the problem lies with Thunderbird because everything is fine via RoundCube and if it tell Thunderbird to rebuild it's index it shows the folder correctly again. Except of course for a subset of the messages in my inbox that it insists where delivered at the exact time I re-indexed it, every time. So what IMAP clients do people prefer these days? Preferably windows or cross platform and it needs to have decent key bindings because (probably like many of you) I get 100s of emails a day via lists and anything that speeds my way through them is good. I run my own server (probably obvious being on this list) and can install webmail clients as well. I ran squirrelmail for a while but although functional it's quite dated. I'm using RoundCube for access away from my systems now but it lacks keyboard shortcut support and trying to click one email after another with a laptop touchpad gets painful fast. Thanks, Jonathan
Re: [Dovecot] Dovecot+Sieve Please Help!...
Andrey Garkin schrieb:
Dovecot Sieve Plugin...
2. dovecot.sieve file in /home/vmail/kipalex.ru/and...@kipalex.ru
require fileinto;
if header :contains Subject ***SPAM*** {
fileinto /home/vmail/kipalex.ru/and...@kipalex.ru/.Spam/new;
}
AFAIK it should just be
fileinto Spam
Thomas
Re: [Dovecot] How to see if sieve is active ?
Am 29.10.2009 um 08:34 schrieb Koenraad Lelong: I just found that lda can have a separate log. I'll enable this and see. I read the wiki-page different times, but I don't see what I'm doing wrong. Hi, put something in the LDA section like this to record the activities: log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log You can raise the logging level with 'mail_debug = yes'. It will then dump more information related to sieve. What MTA are you using? If Postfix, can you post that configuration as well including 'master.cf'? It should have those in 'main.cf' for instance: virtual_transport = dovecot dovecot_destination_recipient_limit = 1 ...and the corresponding entries in 'master.cf' Regards Thomas
[Dovecot] SetUID check problem
Running dovecot 1.2.4 on FreeBSD using Postfix. Everything works fine normally, but deliver is executable by world. This is not normally a problem, as I don't run deliver SetUID root. But for whatever reason, when deliver is called by something that IS SetUID root I get the following error: /usr/local/libexec/dovecot/deliver must not be both world-executable and setuid-root. This allows root exploits. See http://wiki.dovecot.org/LDA#multipleuids Deliver's permissions look like this: -r-xr-xr-x While the program calling deliver has permissions like this: -r-s--x--- If it isn't possible for deliver to differentiate between being called by setuid root programs and being setuid root itself I don't think it should be doing that particular security check. Alternatively, there should be an option to turn that particular check off, but what little I saw of the source code and found searching the documentation told me that there doesn't seem to be such an option already. I also couldn't find any mention that this is fixed by 1.2.5 or 1.2.6. Thomas Berezansky Merrimack Valley Library Consortium
Re: [Dovecot] NFS random redirects
On Wed, Oct 21, 2009 at 04:59:50PM +0100, Guy wrote: Our current setup uses two NFS mounts accessed simultaneously by two servers. [...] Thanks for sharing your experience. Are you using mbox, dbox or maildir ? What % of IMAP and POP3 clients ? -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
Re: [Dovecot] NFS random redirects
On Wed, Oct 21, 2009 at 09:39:22AM -0700, Brandon Davidson wrote: As a contrasting data point, we run NFS + random redirects with almost no problems. Thanks for your answer as well. What mailbox format are you using ? -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
Re: [Dovecot] Public Folders
Am 22.10.2009 um 16:14 schrieb Peter Fraser: Hi All I'm trying to implement public folders. My dovecot -n readout is at the bottom. I created a maildir called resumes in /home/public Its contents are: mail# ls -la /home/public/resumes total 6 drwx-- 3 vmail vmail 512 Oct 22 08:58 . drwx-- 4 vmail vmail 512 Oct 22 08:47 .. drwx-- 5 vmail vmail 512 Oct 22 08:58 Maildir -rw--- 1 vmail vmail0 Oct 21 18:30 dovecot-acl-list Hi, the layout in the public namespace is supposed to be in maildir flavour. /home/public/.resumes namespace: type: public separator: / prefix: public/ location: maildir:/home/public list: yes subscriptions: yes So your shared folder should be called '.resumes' without a 'Maildir' subdirectory in it. Instead of the file 'dovecot-acl-list' use 'dovecot-acl' inside that folder. The list ACL file 'dovecot-acl-list' is then automatically created in the root directory. Regards Thomas
Re: [Dovecot] NFS random redirects
On Tue, Oct 20, 2009 at 10:47:25AM +0200, Thomas Hummel wrote: Actual mail content should be safe. So you seem to say that indexes files would probably get corrupted but that clients wouldn't notice it ? I'm trying to figure out how to use imap-test test script-ing to test this. Any suggestion what the test file should look like ? Thanks. -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
Re: [Dovecot] NFS random redirects
On Mon, Oct 19, 2009 at 12:42:08PM -0400, Timo Sirainen wrote: Thanks for the answers Timo, I understand random redirect is not a good idea but I'm trying to evaluate the damage it can do. If you do it, you'll most likely see some random index related errors. But are index related errors recoverable (does dovecot notice and fix it dynamically ?) or will they cause client-side corruption ? How bad would that corruption be ? (like fetching wrong message, since index store nextuid as well ? setting wrong flag ? ...) and how could a client fix it ? caches.. So I've added some highly OS-specific code that works most of the time, but not perfectly. It works best with Linux. Ouch! I run dovecot on FreeBSD ;-( imaptest exists now in http://imapwiki.org/ImapTest Thanks. Sorry I didn't find it. Do you have any suggestion to test specifically nfs corruption chances ? Actual mail content should be safe. Unless you just happen to get such a cache file corruption that Dovecot doesn't notice it and sends some broken headers to IMAP client. If that happened, with Maildir, the actual content on disk on server wouldn't be corrupted I guess, so I would that be recoverable on the client ? The long term fix for this is http://www.dovecot.org/list/dovecot/2009-August/041983.html Thanks. -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
[Dovecot] NFS random redirects
Hello, Dovecot documentation states that the random redirects to multiple servers NFS solution is to be avoided and I'm investigation the actual risks of it and a way to put it to test. I'm running dovecot-1.2.6 with Maildir (indexes, mailboxes and control files are all on NFS) and I'm using procmail instead of deliver as the LDA. 1. Documentation says : Dovecot locks the maildir while doing modifications to it or while looking for new messages in it and then mention the dovecot-uidlist.lock dotlock file. a) if that file fcntl'ed in addition (i.e. dotlocked + fcntled or just dotlocked) ? b) is that file THE way to lock the Maildir mentionned above or is it just something else used only for updating that particular file (i.e. is Maildir locked in some way + dovecot-uidlist.lock created or just dovecot-uidlist.lock created) ? 2. Documentation says : NFS caching is a big problem when multiple computers are accessing the same mailbox simultaneously I guess it's because of the dotlocks files and not fcntl locking ? Is there anything else than dovecot-uidlist which is dotlocked ? If yes, is it dotlocked only or dotlocked and fcntled ? 3. Documentation says : Dovecot v1.1 flushes NFS caches when needed if you set mail_nfs_storage=yes How can a program flush the NFS caches ? By which (system) call ? 4. Documentation says : Besides the NFS cache problems described above, mailbox contents can't be cached as well in the memory either. Is it about in-memory indexes or part of indexes loaded into memory ? 5. How can I torture-test concurrent access to the same mailbox through 2 dovecot servers ? I don't see imaptest.c anymore on http://dovecot.org/tools but I see 2 nfs_test ? Is there some command line options I should use ? 6. when and why can a random redirect to multiple server can cause mailbox corruption ? On flags only or on content as well ? Thanks -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
Re: [Dovecot] Sieve question
On 7/7/2009 1:59 PM, CJ Keist wrote: If there is a separate sieve mailing list let me know. But have question if someone else has done this or not. Right now I have web form people use to setup their vacation replies using Sieve (1.1.6). The form alows them to set what they want their reply address to be, whether to send the reply once, weekly or bi-weekly. I would like to setup another option to let them set the date in which to de-active the vacation replies automatically. Right now they have to remember to log back into the form to turn off the vacation reply. Has anyone set something like this up? From what I've seen of the sieve RFCs, there's no provision for setting this. (Or has that been added?) I also run into this request regularly with my users who want their vacation replies to turn on at 2pm Friday and turn off at 9am Monday. Which currently means that someone has to babysit the sieve scripts. Ideally, it would be an option to the vacation element (i.e. start time and end time). The reason that a start/end time would be useful is in the case of where someone wants to setup their vacation replies ahead of time, and have them automatically enable/disable for the specified time period. (apologies for continuing an old thread, but I'm curious)
Re: [Dovecot] Panic: file sieve-cmu.c: line 262 (part_save): assertion failed: (buf-used - 1 == part-body_size.physical_size)
Am 13.10.2009 um 10:11 schrieb Raffael Schmid: Hi everybody We are running in the same issue as Maciej Polewczynski does in http://www.dovecot.org/list/dovecot/2008-September/033645.html Is there already a solution? I dont think so? In the TODO-File for 1.2.2 this issue is still reported: [...] - sieve-cmu.c crash: i_assert(buf-used - 1 == part-body_size.physical_size); [...] -- snip -- About our system: # dovecot --version 1.2.2 lda: postmaster_address: postmas...@nine.ch mail_plugins: sieve quota Hi, you can not run into the same problem as the Dovecot 1.2 series has a new Sieve implementation rewritten by Stephan Bosch. If there ought to be a similar problem it is most likely fixed in a later release (1.2.6 is current). Regards Thomas
Re: [Dovecot] dovecot 1.2.6 fails to build with openssl 0.9.8
Am 07.10.2009 um 10:44 schrieb Paul Howarth: I've worked around this by reverting the function to the 1.2.5 version for now but I think a better solution would be to have a configure test for these functions and only include the SSL compression details when they're available. Which I believe was done here: http://www.dovecot.org/list/dovecot/2009-October/043335.html
Re: [Dovecot] Move messages marked as Spam
Am 07.10.2009 um 18:29 schrieb mic...@casa.co.cu: There is an option of deliver to control this -n: http://wiki.dovecot.org/LDA Bye, no desire to control or limit the script wondered whether the script to run and find some header message marked as spam, is able to create for itself a folder called spam so to move the message to her. That's what the option -n is for, as Steffen stated...
Re: [Dovecot] Move messages marked as Spam
Am 07.10.2009 um 21:10 schrieb Michel Bulgado:
global-default.script
#
require [include];
include :global global-spam.script;
global-spam.script
###
require fileinto;
if header :contains X-Bogosity Spam {
fileinto Spam;
stop;
}
The include is intended to be run from a personal script. You kind of
loop it from the global script itself.
And i still seeing this in my logs:
mailserver deliver(mic...@casa.co.cu): Per-user script path is
unknown.
See http://wiki.dovecot.org/LDA/Sieve#location
Per default 'cmusieve' will look for '.dovecot.sieve' in the user's
home directory. Reference your global script from there, or better,
for testing put the code of the global script in '.dovecot.sieve'.
You may also configure the personal script:
sieve = /var/sieve-scripts/%u.sieve
Regards
Thomas
Re: [Dovecot] Debugging IMAP ACLs
Am 06.10.2009 um 16:04 schrieb Kerem Erciyes: a08 login * * a08 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA] Logged in a09 MYRIGHTS a09 BAD Error in IMAP command MYRIGHTS: Unknown command. a10 GETACL INBOX a10 BAD Error in IMAP command GETACL: Unknown command. Add 'imap_acl' to the plugins section to activate it: mail_plugins: imap_acl Regards Thomas
Re: [Dovecot] how to hide mailbox from the IMAP clients
Am 06.10.2009 um 16:27 schrieb Kostik: For example, to hide the directory where the personal Sieve scripts are stored or etc. With recent versions the sieve scripts are stored in the home directory per default, rather than the maildir itself. You may wan't to verify this parameter: sieve = ~/.dovecot.sieve Regards Thomas
Re: [Dovecot] Configuring for virtual users in Postfix
On Sat, Oct 03, 2009 at 11:06:56AM -0400, Jerry wrote:
FreeBSD-7.2 with Postfix-2.7x
dovecot_destination_recipient_limit = 1
virtual_mailbox_domains = your.domain.here
virtual_transport = dovecot
Have you also populated the LDA to 'master.cf'?
dovecot unix - n n - - pipe
flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/deliver -f ${sender} -d
${recipient}
Regards
Thomas
Re: [Dovecot] Apple mail troubles
On Thu, Oct 01, 2009 at 02:44:53PM +0200, Frank Bonnet wrote: OK thank you , but Mac users are difficult to convinct ;-) I have used it with the 'Mail.app' that came with Leopard and I'm using it with Snow Leopard with no (major) problems nowadays. It has some problems when listing/subscribing to several namespaces, but I did not encounter the problem you describe. Maybe you can provide more details, what Mail.app, 'dovecot -n'? Regards Thomas
Re: [Dovecot] Managesieve and Proxy
Hi Oliver, is it possible to use the dovecot proxy feature for the mangaesieve server also ? Yes, it works.
Re: [Dovecot] sieve security problem
Am 19.09.2009 um 21:14 schrieb Robert Schetterer: hi , anybody knows more about this ? http://secunia.com/advisories/36698/ http://secunia.com/advisories/36629/ http://secunia.com/advisories/36713/ The Dovecot site http://www.dovecot.org/ and the 1.2.5 release notes some days ago do :) Seriously, Timo pointed out it's time to move to the rewritten plugin by Stephan. Regards Thomas
