- dovecot - dovecot.org

Re: [Dovecot] Prevent Download messages from server
by Peter Mogensen 20 Sep '12

20 Sep '12

> we have no problem, just i want to learn how can i do that. i think > it's clear . Well... I'm pretty sure most others don't. But anyway. As in ALL Internet protocols (IMAP being no exception), letting the client read data on the server requires it to download the data. Preventing download will prevent reading the mail. Period. So if you're fine with that and just want to learn how to do it, then just disable the account in the user database. /Peter

4 4

Re: [Dovecot] Dovecot deliver Segmentation fault when arrive the first message
by interfaSys sàrl 20 Sep '12

20 Sep '12

I see the same crashes on FreeBSD. Turning off ACL makes the crashes disappear. I'm getting a different backtrace though and it doesn't seem to be related to ACL: Core was generated by `imap-login'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/dovecot/libdovecot-login.so.0...done. Loaded symbols for /usr/lib/dovecot/libdovecot-login.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/libc.so.7...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/local/lib/libssl.so.8...done. Loaded symbols for /usr/local/lib/libssl.so.8 Reading symbols from /usr/local/lib/libcrypto.so.8...done. Loaded symbols for /usr/local/lib/libcrypto.so.8 Reading symbols from /usr/lib/librt.so.1...done. Loaded symbols for /usr/lib/librt.so.1 Reading symbols from /lib/libthr.so.3...done. Loaded symbols for /lib/libthr.so.3 Reading symbols from /usr/lib/libz.so...done. Loaded symbols for /usr/lib/libz.so Reading symbols from /libexec/ld-elf.so.1...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x00000000104b99a6 in hash_table_destroy (_table=0x28) at _ctype.h:143 143 return (_c < 0 || _c >= __mb_sb_limit) ? _c : [New Thread 10e041c0 (LWP 103332/initial thread)] (gdb) bt full #0 0x00000000104b99a6 in hash_table_destroy (_table=0x28) at _ctype.h:143 table = (struct hash_table *) 0x10e29700 #1 0x0000000010478cf1 in settings_parser_deinit (_ctx=0x10e29778) at array.h:197 ctx = (struct setting_parser_context *) 0x0 #2 0x00000000104ac4ea in master_service_settings_cache_deinit (_cache=0x1045da08) at master-service-settings-cache.c:81 cache = (struct master_service_settings_cache *) 0x10e2e040 entry = (struct settings_entry *) 0x10e29740 next = (struct settings_entry *) 0x0 __FUNCTION__ = "master_service_settings_cache_deinit" #3 0x000000001044d1df in login_settings_deinit () at login-settings.c:129 No locals. #4 0x000000001044dd7e in main_deinit () at main.c:62 No locals. #5 0x000000001044df5c in login_binary_run (binary=0x4051c0, argc=2, argv=0x7fffffffebd8) at main.c:62 service_flags = 72 set_pool = 0x10e2d020 allow_core_dumps = true login_socket = 0x10457491 "login" c = -1 #6 0x00000000004036ee in main (argc=2, argv=0x7fffffffebd8) at client.c:40 No locals. Cheers, Olivier

2 1

Re: [Dovecot] [PATCH] Generalize HMAC implementation
by Florian Zeitz 19 Sep '12

19 Sep '12

Am 11.09.2012 20:21, schrieb Timo Sirainen: > On 11.9.2012, at 21.07, Florian Zeitz wrote: > >>> I think we could simply #define the largest allowed context_size, use it for these buffers' sizes and then add i_assert(meth->context_size <= HMAC_MAX_CONTEXT_SIZE) >>> >> Well, either that, or we could use a union of all known context structs >> there. > > That annoyingly requires #including in hmac.h all the different .h files that contain hash contexts. When new hashes are added I doubt anyone remembers to update that. And since the hmac_context is rather rarely used I don't think it matters if we just use a somewhat large context size. > >> Or we could use i_malloc() and i_free() under the assumption hmac_init() >> + hmac_final() calls are always matched. > > Yeah, that's not too bad either I guess. Although it is different from other hash_init()+final calls which don't require it, and it's also wasting CPU a bit. > Here is an updated version of the patch. It uses the variant defining the largest allowed content size. I choose 1024 bit (128 Byte), since that is what most of the SHA-3 candidates use, so it's hopefully somewhat future proof. It's also rebased to the current head and switches the hmac uses added since the last version over to the changed API. It also fixes an "interesting" compiler warning I got with clang, which complained about the fact that struct hmac_context* was (re)declared in the prototype of hmac_md5_get_cram_context() and therefore separate from the one declared in hmac.h. Regards, Florian

1 1

[Dovecot] Deleting a folder with & character
by Angel L. Mateo 19 Sep '12

19 Sep '12

Hello, One of my users has a mailbox named 'INBOX.Kron & SPM' (maybe created a long time ago, when we use courier imap as pop/imap server, but I'm not sure). I can see the maildir with a doveadm list command: amateo_adm@myotis31:~$ sudo doveadm mailbox list -u <user> ... INBOX.Kron & SPM ... but I can't delete it, neithe rename it: amateo_adm@myotis31:~$ sudo doveadm mailbox delete -u <user> 'INBOX.Kron & SPM' doveadm(jrfv): Error: Can't delete mailbox INBOX.Kron & SPM: Mailbox doesn't exist: INBOX.Kron &- SPM amateo_adm@myotis31:~$ sudo doveadm mailbox delete -u <user> 'INBOX.Kron \& SPM' doveadm(jrfv): Error: Can't delete mailbox INBOX.Kron \& SPM: Mailbox doesn't exist: INBOX.Kron \&- SPM is there any way to delete it with doveadm command? should I use a specific syntax or escape to indicate the name?

5 5

[Dovecot] 2.1.10 crashes at login (buf->used <= buf->alloc)
by interfaSys sàrl 19 Sep '12

19 Sep '12

Hello, There is a big problem with 2.1.10. Here is what I saw in the logs: Sep 18 22:22:23 imap(): Panic: file buffer.c: line 86 (buffer_check_limits): assertion failed: (buf->used <= buf->alloc) Sep 18 22:22:23 imap(): Fatal: master: service(imap): child 26833 killed with signal 6 (core dumped) Reverting to 2.1.9 with the exact same config file works just fine Cheers, Olivier

4 10

[Dovecot] ssl cert for mail server
by cc "maco" young 19 Sep '12

19 Sep '12

for testing a new ssl cert. it works ok for browsers, but > openssl s_client -crlf -connect ms1.trailsandtribulations.net:443 => verify error:num=19:self signed certificate in certificate chain is this ssl cert - as it's constructed - is ok for mail clients? (realize needs to be on mail port etc - right now talking about the cert itself.) have had problems with thunderbird, and was wondering if this might be part of the problem.

2 1

[Dovecot] Released Pigeonhole v0.3.3 for Dovecot v2.1.10
by Stephan Bosch 18 Sep '12

18 Sep '12

Hello Dovecot users, Version 0.3.2 was a bit broken, because it failed to compile against installed Dovecot headers. Changelog v0.3.3: - Fixed compile against installed Dovecot headers. This was broken by the ld.gold fix in the previous release. The release is available as follows: http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.3.tar.gz http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.3.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] lda bug: multiple passdb ignored
by Алексей Панкратов 18 Sep '12

18 Sep '12

Greetings. When dovecot configured to use multiple passdb and static userdb as: #password database in multiple ldap subtree passdb { driver = ldap args = /usr/local/etc/dovecot/dv-ldap-real.conf } passdb { driver = ldap args = /usr/local/etc/dovecot/dv-ldap-virtual.conf } userdb { driver = static args = uid=pop gid=mailnull } all works fine but... When LDA deliver mail it check passdb but only first appeared in configuration: 18.09.2012 15:00:18 auth: Debug: master in: USER 1 info(a)zzz.zz service=lda 18.09.2012 15:00:18 auth: Debug: cache(info(a)zzz.zz): miss 18.09.2012 15:00:18 auth: Debug: ldap(info(a)zzz.zz): pass search: base=ou=account,ou=it,dc=planar,dc=local scope=subtree filter=(&(objectClass=x-mailUser)(uid=info)) fields=x-mailPassword 18.09.2012 15:00:18 lda: Debug: auth input: 18.09.2012 15:00:18 auth: Debug: cache(info(a)planar.spb.ru): hit: 18.09.2012 15:00:18 auth: Debug: master out: NOTFOUND 1 1 P.S. dovecot version 2.1.7 sysytem x86 FreeBSD 9.0

3 4

[Dovecot] Proxy connection timeouts
by Kelsey Cummings 18 Sep '12

18 Sep '12

We are seeing a few (0-15) proxy failures like the following out of ~3m successful proxied connections a day. Average session creation load over our peak hour is about 47/sec. The backend servers aren't logging anything that would suggest any internal problem like insufficient processes to handle the load. It doesn't seem to happen when utilization is lowest at night. dovecot: imap-login: Error: proxy(foo): connect(1.1.1.1, 143) failed: Connection timed out (after 63 secs) I'm curious if anyone else has seen any similar problems or has any suggestions. # dovecot -n # 2.1.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.5.2.el6.x86_64 x86_64 Scientific Linux release 6.3 (Carbon) auth_master_user_separator = * auth_username_format = %Ln auth_verbose = yes auth_verbose_passwords = sha1 auth_worker_max_count = 64 mail_fsync = always mail_log_prefix = "%s(%u): session=%{session} " mail_plugins = stats zlib maildir_very_dirty_syncs = yes mmap_disable = yes passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = imap driver = pam } plugin { lazy_expunge = DELETED_MESSAGES. stats_refresh = 30 secs stats_track_cmds = yes } protocols = imap pop3 service anvil { client_limit = 10000 } service auth { client_limit = 10000 vsz_limit = 512 M } service doveadm { inet_listener { port = 1842 } unix_listener doveadm-server { mode = 0666 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 7000 process_min_avail = 32 } service imap-postlogin { executable = script-login -d /etc/dovecot/bin/sonic-imap-postlogin user = $default_internal_user } service imap { executable = imap imap-postlogin process_limit = 4096 vsz_limit = 512 M } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } process_limit = 2000 process_min_avail = 32 } service pop3-postlogin { executable = script-login -d /etc/dovecot/bin/sonic-pop3-postlogin user = $default_internal_user } service pop3 { executable = pop3 pop3-postlogin process_limit = 4096 } service stats { fifo_listener stats-mail { mode = 0666 } } shutdown_clients = no ssl = required ssl_ca = </etc/dovecot/ssl/gd_bundle.crt ssl_cert = </etc/dovecot/ssl/imap.sonic.net.crt ssl_key = </etc/dovecot/ssl/imap.sonic.net.key ssl_parameters_regenerate = 1 days syslog_facility = local0 userdb { driver = passwd } verbose_proctitle = yes protocol imap { imap_id_send = support-url support-email mail_max_userip_connections = 20 mail_plugins = stats zlib mwi_update mail_log notify imap_stats imap_zlib ssl_ca = </etc/dovecot/ssl/gd_bundle.crt ssl_cert = </etc/dovecot/ssl/imap.sonic.net.crt ssl_key = </etc/dovecot/ssl/imap.sonic.net.key } protocol pop3 { mail_plugins = stats zlib lazy_expunge pop3_fast_size_lookups = yes pop3_uidl_format = %f ssl_ca = </etc/dovecot/ssl/pop.sonic.net.ca-bundle ssl_cert = </etc/dovecot/ssl/pop.sonic.net.crt ssl_key = </etc/dovecot/ssl/pop.sonic.net.key }

2 1

[Dovecot] Mailbox aliases
by Timo Sirainen 18 Sep '12

18 Sep '12

I've been wondering about ways to handle all the various different Sent/Sent Messages/Sent Items/etc mailboxes that different clients create and if there could be a way to make them work at least somewhat better. I'm mainly thinking about ISP-like installations where users are using tons of different clients and there's no way to get everyone configured properly. Of course the eventual solution is hopefully that all the clients will support SPECIAL-USE extension, but while waiting for that maybe mailbox aliases could help some. So one possibility would be to force autocreation of wanted specific mailbox names, and create aliases for the other commonly used mailboxes. The main difference here for the current behavior is that all of the mailboxes would contain the same mails, instead of different mails going to different mailboxes with different clients. So for example: .. mailbox Sent { auto = create special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent alias_for = Sent } .. If "Sent Messages" doesn't exist: - DELETE Sent works as usual - RENAME Sent works as usual If "Sent Messages" is created: - it's symlinked to Sent - DELETE "Sent messages" deletes the symlink, not the contents - RENAME "Sent messages" isn't allowed - DELETE/RENAME Sent fails with message: Delete/Rename for Sent not allowed before "Sent Messages" is deleted. Thoughts? The main disadvantage is that clients would still see two different mailboxes, and some would download contents from both of them. I was thinking about creating some wiki page which could list the best working configurations and also a client list, which would specify if it supports SPECIAL-USE and what the default mailbox names it uses are.

4 4