Re: [Dovecot] Outlook 2010 very slow when using IMAP - are there any tweaks?
Il 02/07/2012 16:34, Kaya Saman ha scritto:
Hi,
though this is a bit of a side question, has anybody had an issue
while running Outlook 2010 with Dovecot?
The reason why I am asking is that I have setup a Dovecot 2.1.7 server
on FreeBSD which works fantastically with Thunderbird but Outlook
seems to be twice as slow in transferring information across??
# dovecot -n
# 2.1.7: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 8.2-RELEASE amd64
auth_debug = yes
auth_mechanisms = plain ntlm login
auth_use_winbind = yes
auth_username_format = %n
auth_verbose = yes
auth_winbind_helper_path = /usr/local/bin/ntlm_auth
disable_plaintext_auth = no
info_log_path = /var/log/dovecot-info.log
log_path = /var/log/dovecot.log
mail_gid = mail_user
mail_home = /mail/AD_Mail/%Ld/%Ln
mail_location = maildir:~/Maildir
mail_uid = mail_user
passdb {
args = failure_show_msg=yes
driver = pam
}
pop3_fast_size_lookups = yes
pop3_lock_session = yes
pop3_no_flag_updates = yes
protocols = imap pop3
ssl = no
userdb {
driver = static
}
Since (like most corporate organizations out there) we solely run
Outlook coupled to Exchange, this excersize was meant to be a way of
getting rid of PST files. We don't run out own Exchange however, and
don't have any control over it either.
My workaround was to simply use the Outlook GUI space to transfer
emails between Exchange and Dovecot running the IMAPv4 protocol.
For whatever reason Outlook is being really garbage about dealing with
stuff and since I don't know Outlook or MS products very well (being
your typical average OpenSource guy) I was wondering if there were any
tweaks that could be made within Outlook to speed it up or in Dovecot
to work better with Outlook?
I guess one could get sidetracked into the argument of mdbox vs.
Maildir from my config however, Thunderbird is really fast and
transfers large amounts of data really easily. Reaches round 130Mbps
using nload performance grapher, while Outlook only manages ~50kbps
but spikes at 2-3Mbps on occassion.
Try to understand (from dovecot logs) if there are difference between
outlook and thunderbird, for example outlook connect over ssl and
thunderbird no ecc..
Nicola
Can anyone offer any guidence or assistance in this matter??
Actually wherever I run Dovecot, including my servers at home, it is
fast and reliable. Yes I know MS is the polar opposite of anything
worth using however, my company won't change and I'm stuck banging my
head against the wall while trying to get MS to interface with
ANYTHING.
Regards,
Kaya
Re: [Dovecot] moving from BSD to Ubuntu
Il 30/06/2012 22:19, spamv...@googlemail.com ha scritto: hi.. im planning to move my Mailserver from an FreeBSD Box to an Ubuntu 12.04 LTS Box. Hi, I recently migrated to ubuntu 12.04 (not from freebsd) the only problem was this: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1016905 solved patching openssl ubuntu package, Nicola Both Boxes run Dovecot 2.0 Does anyone did this before and experienced any problems ? Downtime is no problem, my plan is to stop Dovecot on the Bsd Box and copy all Mailbox files to the Uuntu system and start dovecot. Regards Hans
[Dovecot] auth service: out of memory
Hi,
I have some out of memory errors in my logs (file errors.txt attached)
I'm using dovecot 2.0.19, I can see some memory leaks fix in hg after
the 2.0.19 release but they seem related to imap-login service,
I attached my config too, is something wrong there? Should I really
increase the limit based on my settings?
Can these commits fix the reported leak?
http://hg.dovecot.org/dovecot-2.0/rev/6299dfb73732
http://hg.dovecot.org/dovecot-2.0/rev/67f1cef07427
Please note that the auth service is restarted when it reach the limit
so no real issues,
please advice
thanks
Nicola
cat /var/log/mail.log | grep Out of memory
Jun 28 11:48:24 server1 dovecot: master: Error: service(auth): child 31301
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
Jun 28 11:50:18 server1 dovecot: auth: Fatal: pool_system_realloc(8192): Out of
memory
Jun 28 11:50:18 server1 dovecot: master: Error: service(auth): child 10782
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
Jun 28 11:52:43 server1 dovecot: master: Error: service(auth): child 16854
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
Jun 28 11:54:01 server1 dovecot: auth: Fatal: block_alloc(4096): Out of memory
Jun 28 11:54:01 server1 dovecot: master: Error: service(auth): child 23378
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
Jun 28 11:55:09 server1 dovecot: auth: Fatal: pool_system_realloc(8192): Out of
memory
Jun 28 11:55:09 server1 dovecot: master: Error: service(auth): child 28203
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
Jun 28 11:56:07 server1 dovecot: master: Error: service(auth): child 32570
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
Jun 28 11:57:01 server1 dovecot: auth: Fatal: block_alloc(4096): Out of memory
Jun 28 11:57:01 server1 dovecot: master: Error: service(auth): child 5136
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
Jun 28 11:57:57 server1 dovecot: master: Error: service(auth): child 9245
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
Jun 28 11:58:52 server1 dovecot: master: Error: service(auth): child 13779
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
Jun 28 11:59:49 server1 dovecot: master: Error: service(auth): child 18260
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
Jun 28 12:01:03 server1 dovecot: auth: Fatal: pool_system_realloc(8192): Out of
memory
Jun 28 12:01:03 server1 dovecot: master: Error: service(auth): child 22181
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
Jun 28 12:03:24 server1 dovecot: auth: Fatal: pool_system_malloc(3144): Out of
memory
Jun 28 12:03:24 server1 dovecot: master: Error: service(auth): child 27253
returned error 83 (Out of memory (service auth { vsz_limit=128 MB }, you may
need to increase it))
# 2.0.19: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-25-generic x86_64 Ubuntu 12.04 LTS ext4
auth_cache_size = 10 M
auth_mechanisms = plain login
auth_socket_path = /var/run/dovecot/auth-userdb
auth_worker_max_count = 128
base_dir = /var/run/dovecot/
default_process_limit = 200
default_vsz_limit = 128 M
disable_plaintext_auth = no
first_valid_gid = 2000
first_valid_uid = 2000
hostname = mail.example.com
last_valid_gid = 2000
last_valid_uid = 2000
listen = *
login_greeting = SVR ready.
mail_location = maildir:/srv/panel/mail/%d/%t/Maildir
mail_plugins = quota trash autocreate
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date ihave
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
autocreate = Trash
autocreate2 = Junk
autocreate3 = Drafts
autocreate4 = Sent
autosubscribe = Trash
autosubscribe2 = Junk
autosubscribe3 = Drafts
autosubscribe4 = Sent
quota = maildir:User quota
quota_rule = *:storage=300MB
quota_rule2 = Trash:ignore
quota_warning = storage=95%% quota-warning 95 %u
quota_warning2 = storage=80%% quota-warning 80 %u
sieve = ~/.dovecot.sieve
sieve_before = /etc/dovecot/sieve/move-spam.sieve
sieve_dir = ~/sieve
sieve_max_actions = 32
sieve_max_redirects = 4
sieve_max_script_size = 1M
sieve_quota_max_scripts = 10
sieve_quota_max_storage = 2M
trash = /etc/dovecot/dovecot-trash.conf.ext
}
postmaster_address = postmas...@example.com
protocols = imap pop3 sieve
service auth-worker {
user = $default_internal_user
}
service auth {
Re: [Dovecot] auth service: out of memory
Il 29/06/2012 09:19, Timo Sirainen ha scritto: On 29.6.2012, at 9.35, Mailing List SVR wrote: I have some out of memory errors in my logs (file errors.txt attached) How large is your auth process's VSZ when it starts up and has handled a couple of logins? It's possible that it's not leaking at all, you're just not giving enough memory for its normal operation. Some Linux distros nowadays build binaries that eat up a lot of VSZ immediately when they start up. ps aux report this: dovecot 7454 0.0 0.0 85980 3776 ?S09:36 0:00 dovecot/auth before restarting dovecot the auth process was running since about 1 hour and this is the output from ps aux dovecot 25002 0.0 0.0 86112 3780 ?S08:24 0:00 dovecot/auth thanks Nicola
Re: [Dovecot] auth service: out of memory
Il 29/06/2012 09:45, Timo Sirainen ha scritto:
On 29.6.2012, at 10.39, Mailing List SVR wrote:
Il 29/06/2012 09:19, Timo Sirainen ha scritto:
On 29.6.2012, at 9.35, Mailing List SVR wrote:
I have some out of memory errors in my logs (file errors.txt attached)
How large is your auth process's VSZ when it starts up and has handled a couple
of logins? It's possible that it's not leaking at all, you're just not giving
enough memory for its normal operation. Some Linux distros nowadays build
binaries that eat up a lot of VSZ immediately when they start up.
ps aux report this:
dovecot 7454 0.0 0.0 85980 3776 ?S09:36 0:00 dovecot/auth
before restarting dovecot the auth process was running since about 1 hour and
this is the output from ps aux
dovecot 25002 0.0 0.0 86112 3780 ?S08:24 0:00 dovecot/auth
So you have 44 MB of VSZ available after startup. You also have 10 MB of auth
cache, which could in reality take somewhat more than 10 MB. It doesn't leave a
whole lot available for regular use. I'd increase the auth process's VSZ limit
and see if it still crashes.
I increased the limit to 192MB or should I set the limit to 256MB or
more? I'll wait some days to see if still crash
If you want to, you could also test with valgrind if there's a leak:
service auth {
executable = /usr/bin/valgrind --leak-check=full -q /usr/libexec/dovecot/auth
}
You'd then need to restart the auth process to make valgrind output the leaks.
for now I prefer to avoid valgrind on a production server if the crash
persist with the new limit I'll setup a test environment and I'll run
valgrind there,
thanks
Nicola
[Dovecot] 2.0.19 segfault
Hi,
after the upgrade from dovecot 2.0.13 (ubuntu oneiric) to dovecot 2.0.19
(ubuntu precise), in my logs I have a lot of these errors:
Jun 23 00:20:29 server1 dovecot: master: Error: service(imap-login):
child 6714 killed with signal 11 (core dumps disabled)
I tested 2.0.21 and the problem is still here. The problem seems to
appear only when the client is ms outlook, thunderbird works fine
Here is the captured trace (I hope this is enough and I don't need to
install debug symbols for everythings):
Core was generated by `dovecot/imap-login -D'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f4d01c1a031 in RC4 () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
(gdb) bt full
#0 0x7f4d01c1a031 in RC4 () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
No symbol table info available.
#1 0x0134 in ?? ()
No symbol table info available.
#2 0x00cd in ?? ()
No symbol table info available.
#3 0x7f4d03e97470 in ?? ()
No symbol table info available.
#4 0x7f4d01c80629 in ?? () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
No symbol table info available.
#5 0x7f4d01f82bcf in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.0.0
No symbol table info available.
#6 0x7f4d01f79e04 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.0.0
No symbol table info available.
#7 0x7f4d01f7a134 in ?? () from /lib/x86_64-linux-gnu/libssl.so.1.0.0
No symbol table info available.
#8 0x7f4d027fed6f in ssl_write (proxy=0x7f4d03e7c0a0)
at ssl-proxy-openssl.c:499
ret = optimized out
#9 0x7f4d027fee68 in plain_read (proxy=0x7f4d03e7c0a0)
at ssl-proxy-openssl.c:308
ret = optimized out
corked = true
---Type return to continue, or q return to quit---
#10 0x7f4d025b5c98 in io_loop_call_io (io=0x7f4d03e84b10) at
ioloop.c:384
ioloop = 0x7f4d03e3e680
t_id = 2
#11 0x7f4d025b6d27 in io_loop_handler_run (ioloop=optimized out)
at ioloop-epoll.c:213
ctx = 0x7f4d03e505a0
events = 0x6579351d
event = 0x7f4d03e50610
list = 0x7f4d03e93690
io = optimized out
tv = {tv_sec = 59, tv_usec = 999832}
msecs = optimized out
ret = 1
i = optimized out
call = optimized out
#12 0x7f4d025b5c28 in io_loop_run (ioloop=0x7f4d03e3e680) at
ioloop.c:405
No locals.
#13 0x7f4d025a3e33 in master_service_run (service=0x7f4d03e3e550,
callback=optimized out) at master-service.c:481
No locals.
#14 0x7f4d027f7cc2 in main (argc=2, argv=0x7f4d03e3e370) at main.c:371
set_pool = 0x7f4d03e3e880
allow_core_dumps = optimized out
---Type return to continue, or q return to quit---
login_socket = 0x7f4d02800763 login
c = optimized out
#15 0x7f4d021d676d in __libc_start_main ()
from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#16 0x7f4d02c2d5a9 in _start ()
No symbol table info available.
Nicola
Re: [Dovecot] 2.0.19 segfault
Il 23/06/2012 22:39, Mailing List SVR ha scritto:
Hi,
after the upgrade from dovecot 2.0.13 (ubuntu oneiric) to dovecot
2.0.19 (ubuntu precise), in my logs I have a lot of these errors:
Jun 23 00:20:29 server1 dovecot: master: Error: service(imap-login):
child 6714 killed with signal 11 (core dumps disabled)
I tested 2.0.21 and the problem is still here. The problem seems to
appear only when the client is ms outlook, thunderbird works fine
Here is the captured trace (I hope this is enough and I don't need to
install debug symbols for everythings):
Core was generated by `dovecot/imap-login -D'.
Program terminated with signal 11, Segmentation fault.
#0 0x7f4d01c1a031 in RC4 () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
(gdb) bt full
#0 0x7f4d01c1a031 in RC4 () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
No symbol table info available.
#1 0x0134 in ?? ()
No symbol table info available.
#2 0x00cd in ?? ()
No symbol table info available.
#3 0x7f4d03e97470 in ?? ()
No symbol table info available.
#4 0x7f4d01c80629 in ?? () from
/lib/x86_64-linux-gnu/libcrypto.so.1.0.0
No symbol table info available.
#5 0x7f4d01f82bcf in ?? () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0
No symbol table info available.
#6 0x7f4d01f79e04 in ?? () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0
No symbol table info available.
#7 0x7f4d01f7a134 in ?? () from
/lib/x86_64-linux-gnu/libssl.so.1.0.0
No symbol table info available.
#8 0x7f4d027fed6f in ssl_write (proxy=0x7f4d03e7c0a0)
at ssl-proxy-openssl.c:499
ret = optimized out
#9 0x7f4d027fee68 in plain_read (proxy=0x7f4d03e7c0a0)
at ssl-proxy-openssl.c:308
ret = optimized out
corked = true
---Type return to continue, or q return to quit---
#10 0x7f4d025b5c98 in io_loop_call_io (io=0x7f4d03e84b10) at
ioloop.c:384
ioloop = 0x7f4d03e3e680
t_id = 2
#11 0x7f4d025b6d27 in io_loop_handler_run (ioloop=optimized out)
at ioloop-epoll.c:213
ctx = 0x7f4d03e505a0
events = 0x6579351d
event = 0x7f4d03e50610
list = 0x7f4d03e93690
io = optimized out
tv = {tv_sec = 59, tv_usec = 999832}
msecs = optimized out
ret = 1
i = optimized out
call = optimized out
#12 0x7f4d025b5c28 in io_loop_run (ioloop=0x7f4d03e3e680) at
ioloop.c:405
No locals.
#13 0x7f4d025a3e33 in master_service_run (service=0x7f4d03e3e550,
callback=optimized out) at master-service.c:481
No locals.
#14 0x7f4d027f7cc2 in main (argc=2, argv=0x7f4d03e3e370) at
main.c:371
set_pool = 0x7f4d03e3e880
allow_core_dumps = optimized out
---Type return to continue, or q return to quit---
login_socket = 0x7f4d02800763 login
c = optimized out
#15 0x7f4d021d676d in __libc_start_main ()
from /lib/x86_64-linux-gnu/libc.so.6
No symbol table info available.
#16 0x7f4d02c2d5a9 in _start ()
No symbol table info available.
Nicola
Here is a more detailed trace,
Core was generated by `dovecot/imap-login -D'.
Program terminated with signal 11, Segmentation fault.
#0 RC4 () at rc4-x86_64.s:343
343rc4-x86_64.s: File o directory non esistente.
(gdb) bt full
#0 RC4 () at rc4-x86_64.s:343
No locals.
#1 0x0134 in ?? ()
No symbol table info available.
#2 0x00cd in ?? ()
No symbol table info available.
#3 0x7f4d03e97470 in ?? ()
No symbol table info available.
#4 0x7f4d01c80629 in rc4_hmac_md5_cipher (ctx=optimized out,
out=0x7f4d03e8d0b8
\314V\347\335Lc\024\205\221'µ\006\177\313\326ۢ\313\317\303c\266\360\347\364\263\242\316z\326\307\320\303Ω\242`\303\321ί\313Т\177\315\305\313̯\320\307u\307\320\320\303\316ѢzƢ\307\314\303\300\316v\242\313\306\316Ǣ\321c\030T
SORT=DISPLAY\301\021\222RC\005D=R\244\237T\342\004\\020ES
TH\003\246AD=\247\032FS
\351ULTIA\315\025N8\032\341\255\364EZ\376\236\062
CHILDREN\\\b{\250\240\255PACE U\216\331\nLUS LIST-EXTENDED I18NLEVEL=h
CO...,
in=optimized out, len=0) at e_rc4_hmac_md5.c:163
key = 0x1a
rc4_off = 139968754799079
md5_off = optimized out
blocks = optimized out
l = optimized out
plen = optimized out
#5 0x7f4d01f82bcf in tls1_enc (s=0x7f4d03e7b700, send=1) at
t1_enc.c:828
---Type return to continue, or q return to quit---
rec = 0x7f4d03e7bcb8
ds = 0x7f4d03e95cf0
l = 308
bs = 1
i = optimized out
ii = optimized out
j = optimized out
k = optimized out
pad = optimized out
enc = 0x7f4d01f4eae0
#6 0x7f4d01f79e04 in do_ssl3_write (s=0x7f4d03e7b700, type=23,
buf=0x7f4d03e7c514 A0 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR
LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES
THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS
LIST-EXTENDED I18NLEVEL=1 CO..., len=292,
create_empty_fragment=0) at s3_pkt.c:815
p
Re: [Dovecot] 2.0.19 segfault
Il 24/06/2012 00:05, Timo Sirainen ha scritto:
On Sat, 2012-06-23 at 22:39 +0200, Mailing List SVR wrote:
after the upgrade from dovecot 2.0.13 (ubuntu oneiric) to dovecot 2.0.19
(ubuntu precise), in my logs I have a lot of these errors:
Jun 23 00:20:29 server1 dovecot: master: Error: service(imap-login):
child 6714 killed with signal 11 (core dumps disabled)
I tested 2.0.21 and the problem is still here. The problem seems to
appear only when the client is ms outlook, thunderbird works fine
Looks to me more like OpenSSL library bug. The only reason why it could
be Dovecot bug is if Dovecot is causing memory corruption. Could you run
imap-login via valgrind to see if this is the case?
service imap-login {
executable = /usr/bin/valgrind -q --vgdb=no
/usr/local/libexec/dovecot/imap-login
chroot =
}
Also have you changed any ssl-related settings in dovecot.conf?
attached my complete configuration, I hope there is a mistake in my config
I looked at the code and there was no relevant change from dovecot
2.0.13 and dovecot 2.0.19, upgrading between ubuntu releases updated
openssl too and this could be the problem,
however is not clear to me while imap over ssl works fine with
thunderdird and I see the crash in the logs for customers that seems to
use ms outlook,
Nicola
# 2.0.19: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-25-generic x86_64 Ubuntu 12.04 LTS ext4
auth_cache_size = 10 M
auth_mechanisms = plain login
auth_socket_path = /var/run/dovecot/auth-userdb
auth_worker_max_count = 128
base_dir = /var/run/dovecot/
default_process_limit = 200
disable_plaintext_auth = no
first_valid_gid = 2000
first_valid_uid = 2000
hostname = mail.svrinformatica.it
last_valid_gid = 2000
last_valid_uid = 2000
listen = *
login_greeting = SVR ready.
mail_location = maildir:/srv/panel/mail/%d/%t/Maildir
mail_plugins = quota trash autocreate
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date ihave
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
autocreate = Trash
autocreate2 = Junk
autocreate3 = Drafts
autocreate4 = Sent
autosubscribe = Trash
autosubscribe2 = Junk
autosubscribe3 = Drafts
autosubscribe4 = Sent
quota = maildir:User quota
quota_rule = *:storage=300MB
quota_rule2 = Trash:ignore
quota_warning = storage=95%% quota-warning 95 %u
quota_warning2 = storage=80%% quota-warning 80 %u
sieve = ~/.dovecot.sieve
sieve_before = /etc/dovecot/sieve/move-spam.sieve
sieve_dir = ~/sieve
sieve_max_actions = 32
sieve_max_redirects = 4
sieve_max_script_size = 1M
sieve_quota_max_scripts = 10
sieve_quota_max_storage = 2M
trash = /etc/dovecot/dovecot-trash.conf.ext
}
postmaster_address = postmas...@svrinformatica.it
protocols = imap pop3 sieve
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener /var/spool/postfix/private/dovecot-auth {
group = vmail
mode = 0660
user = postfix
}
unix_listener auth-userdb {
group = vmail
mode = 0660
user = vmail
}
user = $default_internal_user
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
}
service quota-warning {
executable = script
/srv/panel/django/systemcp/systemutils/mail/quota-warning.py
unix_listener quota-warning {
user = vmail
}
user = dovecot
}
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_cipher_list =
ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM
ssl_key = /etc/ssl/private/dovecot.pem
userdb {
driver = prefetch
}
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocol lda {
mail_plugins = quota trash autocreate sieve
}
protocol imap {
imap_client_workarounds = delay-newmail
mail_max_userip_connections = 10
mail_plugins = quota trash autocreate imap_quota
}
protocol sieve {
mail_max_userip_connections = 10
mail_plugins = quota trash autocreate
managesieve_max_compile_errors = 5
}
protocol pop3 {
mail_max_userip_connections = 10
mail_plugins = quota trash autocreate
pop3_client_workarounds = outlook-no-nuls oe-ns-eoh
}
Re: [Dovecot] 2.0.19 segfault
Il 24/06/2012 00:05, Timo Sirainen ha scritto:
On Sat, 2012-06-23 at 22:39 +0200, Mailing List SVR wrote:
after the upgrade from dovecot 2.0.13 (ubuntu oneiric) to dovecot 2.0.19
(ubuntu precise), in my logs I have a lot of these errors:
Jun 23 00:20:29 server1 dovecot: master: Error: service(imap-login):
child 6714 killed with signal 11 (core dumps disabled)
I tested 2.0.21 and the problem is still here. The problem seems to
appear only when the client is ms outlook, thunderbird works fine
Looks to me more like OpenSSL library bug.
the bug seems related to this patch:
http://cvs.openssl.org/chngview?cn=22415
I'm applying just now
The only reason why it could
be Dovecot bug is if Dovecot is causing memory corruption. Could you run
imap-login via valgrind to see if this is the case?
service imap-login {
executable = /usr/bin/valgrind -q --vgdb=no
/usr/local/libexec/dovecot/imap-login
chroot =
}
Also have you changed any ssl-related settings in dovecot.conf?
Re: [Dovecot] 2.0.19 segfault
Il 24/06/2012 00:49, Mailing List SVR ha scritto:
Il 24/06/2012 00:05, Timo Sirainen ha scritto:
On Sat, 2012-06-23 at 22:39 +0200, Mailing List SVR wrote:
after the upgrade from dovecot 2.0.13 (ubuntu oneiric) to dovecot
2.0.19
(ubuntu precise), in my logs I have a lot of these errors:
Jun 23 00:20:29 server1 dovecot: master: Error: service(imap-login):
child 6714 killed with signal 11 (core dumps disabled)
I tested 2.0.21 and the problem is still here. The problem seems to
appear only when the client is ms outlook, thunderbird works fine
Looks to me more like OpenSSL library bug.
the bug seems related to this patch:
http://cvs.openssl.org/chngview?cn=22415
I'm applying just now
I can confirm that the patch listed above solve the problem, thanks for
pointing me to openssl,
Nicola
The only reason why it could
be Dovecot bug is if Dovecot is causing memory corruption. Could you run
imap-login via valgrind to see if this is the case?
service imap-login {
executable = /usr/bin/valgrind -q --vgdb=no
/usr/local/libexec/dovecot/imap-login
chroot =
}
Also have you changed any ssl-related settings in dovecot.conf?
