Re: ot: accepting self certs into win pc?
On 10/06/2014 01:48, voy...@sbt.net.au wrote: few month ago, I've got a new Dovecot/Postfix server with self issued certificate (like the previous server), transferred users, all went well EXCEPT for one user on Win/Outlook (or Outlook Express) who tells me his new PC 'doesn't want to accept certificate' (sorry, I'm short on exact details at this time) I need to get it sorted out, I expect it 'should just work' like it did for other users, BUT, before I start looking, trying to 'educate myself' better if any one has any pointers, dos or don't regarding win email clients with self certified server, pls point me that way is using IE withwww.dom.com/mycert.crt good point to start ? (after copying mycer.crt to web linked directory first?) thanks, V I get endless grief over this, but if you think Microsoft is bad, try Apple. I wrote some notes on it once: http://blog.frankleonhardt.com/2012/certificate-errors-on-internet-explorer-9-and-how-to-stop-them/ I didn't mention it in the post, but IIRC this did work for making some versions Outlook (and other Microsoft Mail things) happy at the same time. Regards, Frank.
ot: accepting self certs into win pc?
few month ago, I've got a new Dovecot/Postfix server with self issued certificate (like the previous server), transferred users, all went well EXCEPT for one user on Win/Outlook (or Outlook Express) who tells me his new PC 'doesn't want to accept certificate' (sorry, I'm short on exact details at this time) I need to get it sorted out, I expect it 'should just work' like it did for other users, BUT, before I start looking, trying to 'educate myself' better if any one has any pointers, dos or don't regarding win email clients with self certified server, pls point me that way is using IE with www.dom.com/mycert.crt good point to start ? (after copying mycer.crt to web linked directory first?) thanks, V
Re: [Dovecot] dovecot/lmtp munmap()-ing a lot
* Timo Sirainen : > > Why would that happen? (dovecot 2.1.17) > > Difficult to say. It could be munmap()ing memory allocations or it > could be munmap()ing Dovecot index files. Weren't there equivalent > number of mmap() calls?.. > > BTW. In v2.2 the index file handling is faster for LDA/LMTP because it > doesn't even try to mmap() the full indexes into memory. That's probably the problem here. The user had LOTS of (duplicate!) mails in his inbox. -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Bug when virtual mailbox is set to auto=subscribe
Hi everybody, I'd like to submit a bug: My setup: dovecot version: 2.2.13-1 Kernel: 3.14.5-1-ARCH on arch linux x64 Filesystem: ext4 Bug description: If a virtual mailbox is defined with auto = subscribe dovecot crashes upon access via imap. Configuration is as followed: namespace inbox { [...] mailbox virtual/Flagged { auto = subscribe special_use = \Flagged } [...] dovecot-virtual file: # ~/Maildir/virtual/Flagged/dovecot-virtual * -Trash -Trash/* flagged 'auto' must be set to 'no' for virtual mailboxes, otherwise dovecot crashes when the virtual folder is tried to be accessed via a imap (thunderbird in my case). Crash log: Jun 09 21:55:07 pluto dovecot[24881]: imap($MAILADRESS): Panic: file mail-index-sync.c: line 413 (mail_index_sync_begin_to2): assertion failed: (!index->syncing) Jun 09 21:55:07 pluto dovecot[24881]: imap($MAILADRESS): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x68680) [0x7fa67a692680] -> /usr/lib/dovecot/libdovecot.so.0(+0x6876c) [0x7fa67a69276c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fa67a64c83d] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc3dfe) [0x7fa67a9c3dfe] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin_to+0x3f) [0x7fa67a9c3eaf] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin+0x1c) [0x7fa67a9c3f3c] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0xc3) [0x7fa679e71d23] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) [0x7fa67a97cf29] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fa67a97d037] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7fa67a9a59e1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x8c9d) [0x7fa679e70c9d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7fa67a97e321] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0xf94) [0x7fa679e72bf4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) [0x7fa67a97cf29] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fa67a97d037] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7fa67a9a59e1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x8c9d) [0x7fa679e70c9d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7fa67a97e321] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0xf94) [0x7fa679e72bf4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x29) [0x7fa67a97cf29] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x7fa67a97d037] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x31) [0x7fa67a9a59e1] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0x8c9d) [0x7fa679e70c9d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x31) [0x7fa67a97e321] -> dovecot/imap(imap_status_get+0x67) [0x41d6f7] -> dovecot/imap(cmd_status+0x188) [0x4131c8] -> dovecot/imap(command_exec+0x3c) [0x4171ac] -> dovecot/imap() [0x416202] Jun 09 21:55:07 pluto dovecot[24881]: imap($MAILADRESS): Fatal: master: service(imap): child 24926 killed with signal 6 (core dumped) Below a complete dump of doveconf -n (with corrected 'auto' value for virtual mailboxes): # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.14.5-1-ARCH x86_64 mail_home = /home/vmail/%d/%n mail_location = maildir:~/Maildir:LAYOUT=fs mail_plugins = " virtual" namespace { location = virtual:~/Maildir/virtual prefix = virtual/ separator = / } namespace inbox { inbox = yes location = mailbox Archive { auto = create special_use = \Archive } mailbox Drafts { auto = create special_use = \Drafts } mailbox Junk { auto = create special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = create special_use = \Trash } mailbox virtual/All { auto = no special_use = \All } mailbox virtual/Flagged { auto = no special_use = \Flagged } prefix = } passdb { args = username_format=%n scheme=SHA512-CRYPT /etc/dovecot/%d/passwd driver = passwd-file } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } user = vmail } ssl_cert =
Subject tag [Dovecot] is gone
I've actually been thinking about it almost since the beginning. It's just been annoying waste of space on my screen. And more importantly nowadays it's also breaking DKIM/DMARC signatures. So if somebody still uses Subject-based filtering it's about time to switch to List-ID header based filtering now. Another thing I'm wondering about is if I should allow text/html parts, because removing them will also break the DKIM signatures. Or mainly I'd like to allow only multipart/alternative with text/plain + text/html, but I don't think I can configure Mailman to support that.
Re: [Dovecot] dovecot/lmtp munmap()-ing a lot
On 8.6.2014, at 11.59, Ralf Hildebrandt wrote: > I observed several long running dovecot/lmtp processes hogging the > CPU. I then strace'd them (strace -c -p 6375) and found them > munmap()-ing a lot: > > % time seconds usecs/call callserrors syscall > -- --- --- - - > 97.18 19.5925371878 10430 munmap > 2.280.458984 36 12696 epoll_ctl > 0.260.052926 10 5288 fdatasync > 0.210.042472 3 13679 epoll_wait > ... snip ... > > Why would that happen? (dovecot 2.1.17) Difficult to say. It could be munmap()ing memory allocations or it could be munmap()ing Dovecot index files. Weren't there equivalent number of mmap() calls?.. BTW. In v2.2 the index file handling is faster for LDA/LMTP because it doesn't even try to mmap() the full indexes into memory.
Re: [Dovecot] Outlook 2007 & 2010 hangs in v2.2?
On 9.6.2014, at 20.49, Andy Dills wrote: >>> Has anybody noticed Outlook 2007 & 2010 (but apparently not 2013) hanging >>> IMAP connections with Dovecot v2.2 (but not v2.1) when they're FETCHing >>> large mails? I can't think of any reasonable explanation for this. >> >> Most likely solved by: http://hg.dovecot.org/dovecot-2.2/rev/6a9508d28d34 [1] >> >> Strange that it didn't break more commonly or that more people weren't >> complaining about it.. The bug has been there since v2.2.7. > > Thank you Timo. This patch did indeed correct the problem, we had no > problem doing full syncs with the problematic accounts after > implementing this. > > Is it perhaps something that only happens with directory/proxy > environments? I'm surprised it hasn't been mentioned before, I figured > it was something particular to our implementation since nobody else was > mentioning it, until you did. > > Fascinating to me that it only affects Outlook as well. I don't > understand the code well enough to grasp the impact of the bug, so if > somebody has a minute to share an explanation that would be cool. Only happened when using Dovecot proxy. Only happened if client sent a command while another long running command was already sending data. So basically if Outlook started downloading a large mail on background and user clicked another mail, the already running FETCH was stopped because Outlook sent another FETCH command to the same connection. I guess Outlook was the only client to do that.
Re: [Dovecot] NoSQL support
On 4.6.2014, at 16.55, List wrote: > Is there any support for NoSQL databases such as Cassandra (CQL) or MongoDB > now or planned in the future for userdb and passdb lookups? CQL could probably be nicely implemented as lib-sql driver since it's close enough to SQL. I've some preliminary plans for that, but nothing concrete yet. MongoDB could be implemented as lib-dict backend and used with passdb/userdb dict. I've no plans to implement MongoDB currently. Redis and memcached are implemented already though.
Re: [Dovecot] imap-login killed with signal 11 in Dovecot 2.2.13 (feea8645c4d7)
On 7.6.2014, at 13.15, Thomas Leuxner wrote: > Latest 2.2.13 HG feea8645c4d7 seems to unexpectedly kill imap-login sessions: > > Jun 7 11:56:10 nihlus dovecot: imap(t...@leuxner.net): Disconnected: Logged > out in=2203 out=851225 > Jun 7 11:56:10 nihlus dovecot: imap(t...@leuxner.net): Disconnected: Logged > out in=316 out=2417 > Jun 7 11:56:10 nihlus dovecot: imap-login: Fatal: master: > service(imap-login): child 60505 killed with signal 11 (core not dumped - add > -D parameter to service imap-login { executable } > Jun 7 11:56:10 nihlus dovecot: imap-login: Fatal: master: > service(imap-login): child 60595 killed with signal 11 (core not dumped - add > -D parameter to service imap-login { executable } Should be fixed by these: http://hg.dovecot.org/dovecot-2.2/rev/7129fe8bc260 http://hg.dovecot.org/dovecot-2.2/rev/5259f6320e52
Re: [Dovecot] Issues with VANISHED CHANGEDSINCE
Looks like there was a bug in here: http://hg.dovecot.org/dovecot-2.2/rev/98195220a0f7 On 8.11.2012, at 0.08, Michael M Slusarz wrote: > Quoting Timo Sirainen : > >> On 6.11.2012, at 3.49, Michael J Rubinsky wrote: >> >> These defines in mail-transaction-log-private.h anyway can be changed to >> make it much less likely to see your problem: >> >> /* Rotate when log is older than ROTATE_TIME and larger than MIN_SIZE */ >> #define MAIL_TRANSACTION_LOG_ROTATE_MIN_SIZE (1024*32) >> /* If log is larger than MAX_SIZE, rotate regardless of the time */ >> #define MAIL_TRANSACTION_LOG_ROTATE_MAX_SIZE (1024*1024) >> #define MAIL_TRANSACTION_LOG_ROTATE_TIME (60*5) >> >> /* Delete .log.2 files older than this many seconds. Don't be too eager, >> older files are useful for QRESYNC and dsync. */ >> #define MAIL_TRANSACTION_LOG2_STALE_SECS (60*60*24*2) >> >> Maybe the defaults could be changed.. > > I'm not sure changing the defaults is a good idea. But if someone does want > to use a particular dovecot server as the backend for activesync clients, for > example, it would probably make sense to allow these values to be tweaked via > the config files. (I can see an organization having a "normal" IMAP server > and a "activesync" IMAP server that differ in these details, and also in > things like IDLE timeouts). > > michael >
Re: [Dovecot] Outlook 2007 & 2010 hangs in v2.2?
On 06/09/2014 05:21, Timo Sirainen wrote: > On 5.6.2014, at 17.38, Timo Sirainen wrote: > >> Has anybody noticed Outlook 2007 & 2010 (but apparently not 2013) hanging >> IMAP connections with Dovecot v2.2 (but not v2.1) when they're FETCHing >> large mails? I can't think of any reasonable explanation for this. > > Most likely solved by: http://hg.dovecot.org/dovecot-2.2/rev/6a9508d28d34 [1] > > Strange that it didn't break more commonly or that more people weren't > complaining about it.. The bug has been there since v2.2.7. Thank you Timo. This patch did indeed correct the problem, we had no problem doing full syncs with the problematic accounts after implementing this. Is it perhaps something that only happens with directory/proxy environments? I'm surprised it hasn't been mentioned before, I figured it was something particular to our implementation since nobody else was mentioning it, until you did. Fascinating to me that it only affects Outlook as well. I don't understand the code well enough to grasp the impact of the bug, so if somebody has a minute to share an explanation that would be cool. Andy - ANDY DILLS - XECUNET, LLC 5744-R Industry Lane Frederick MD 21704 www.xecu.net [2] P: 301-682-9972 P: 1-877-XECUNET F: 240-215-0351 Twitter [3] Facebook [4] - Links: -- [1] http://hg.dovecot.org/dovecot-2.2/rev/6a9508d28d34 [2] http://www.xecu.net/ [3] https://twitter.com/Xecunet [4] http://www.facebook.com/xecunet
Re: [Dovecot] Outlook 2007 & 2010 hangs in v2.2?
On 5.6.2014, at 17.38, Timo Sirainen wrote: > Has anybody noticed Outlook 2007 & 2010 (but apparently not 2013) hanging > IMAP connections with Dovecot v2.2 (but not v2.1) when they're FETCHing large > mails? I can't think of any reasonable explanation for this. Most likely solved by: http://hg.dovecot.org/dovecot-2.2/rev/6a9508d28d34 Strange that it didn't break more commonly or that more people weren't complaining about it.. The bug has been there since v2.2.7.