January 2017 - dovecot

Vacation Sending To Root
by Shaun Forsyth 31 Jan '17

31 Jan '17

Dovecot Version 2.0.9 I am having an issue where all vacation messages are being sent to root. Is any one able to advise. Dovecot Log Shows :- Sieve: msgid=< CAMD5TViw0sSigGm8JY5WOv0ROs1UdCJFnvb9vo-RzcNN74E92Q(a)mail.xxxxxx.com>: sent vacation response to <root> The emails are handed off to dovecot from sendmail using procmail :0 w | $DELIVER The variable $DELIVER is set as DELIVER="/usr/libexec/dovecot/deliver" I do have DROPPRIVS=YES in procmail, however I don't think deliver works without this. Any advice would greatly help. Shaun

2 2

mail_location in userdb inconsistent with imap and pigeonhole
by Ladislav Laska 31 Jan '17

31 Jan '17

Hi! I'm still fighting with lost mails and what I think is a locking problem. As I've lost some pretty important mails already, I decided to mitigate my troubles by moving to maildir format, which should not be susceptible to these problems. I read the docs and wanted to test on my account, before I mess with all the others and possibly break something. The way to do it seems to be to do an override via userdb. I already have a passwd-file authdb, so I uncommented those few lines in configuration, and added this to my passwd-file: krakonos:{SHA256}xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx=:1000:100::/home/krakonos:/bin/bash:userdb_mail=maildir:/home/krakonos/Mail Now, I'm not really sure why it has to be prefixed with userdb_, but the example in docs has it, and it seems to work. I've attached the relevant part of a logfile, with some debugging enabled, but in short: Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: Added userdb setting: mail=maildir:/home/krakonos/Mail [...] Dec 10 18:39:22 ibex dovecot: imap(krakonos): Debug: maildir++: root=/home/krakonos/Mail, index=, indexpvt=, control=, inbox=/home/krakonos/Mail, alt= [...] Dec 10 18:39:52 ibex dovecot: lda(krakonos): Debug: mbox: INBOX defaulted to /home/krakonos/.mbox/inbox I'm confused why the last line chooses my old mbox over the new location. I'm even more confused by the fact the IMAP works fine, and as I connect from mutt over imap, I can see empty mailboxes (the ~/Mail has only the basic cur/new/tmp structure). However, pigeonhole delivers into the .mbox, and not only if it's for INBOX, but also for spam and others. I read somewhere in the docs that the order is first try userdb, then mail_location and namespaces override the rest. This might be the problem, as I have: mail_location = mbox:~/.mbox namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } Due to inbox=yes this would explain why inbox is using the default path in mail_location. But why even the spam is delivered into the old mbox? And how do I solve the problem anyway, should I just remove the namespace? Anyway, it doesn't explain why the IMAP part and pigeonhole apply different rules and show me different inboxes, which is probably a bug. Thanks! ----------------------------------------------------------------------- Here is the rest of my configuration for reference, the log is attached: ----------------------------------------------------------------------- # 2.2.26.0 (23d1de6): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.26-gentoo x86_64 Gentoo Base System release 2.2 auth_username_format = %n hostname = ibex.krakonos.org login_greeting = Dovecot(a)krakonos.org ready. mail_debug = yes mail_location = mbox:~/.mbox mbox_read_locks = dotlock fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = * driver = pam } passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_bin_dir = /usr/lib/dovecot/sieve-execute sieve_execute_socket_dir = sieve-execute sieve_extensions = +vnd.dovecot.filter +editheader sieve_filter_bin_dir = /usr/lib/dovecot/sieve-filter sieve_filter_socket_dir = sieve-filter sieve_pipe_bin_dir = /usr/lib/dovecot/sieve-pipe sieve_pipe_socket_dir = sieve-pipe sieve_plugins = sieve_extprograms } postmaster_address = postmaster(a)krakonos.org protocols = imap service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } ssl_cert = </etc/ssl/dovecot/server.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol lda { mail_plugins = sieve } -- S pozdravem Ladislav "Krakonoš" Láska http://www.krakonos.org/

2 2

Sieve & Public folders issue (2nd episode)
by dovecot＠avv.solutions 31 Jan '17

31 Jan '17

Hello Community, Getting back to my previous post, here a a complement: - Having enabled sieve, I can store mails and create folder under the recipient - Having enabled public folders, I can move mail into them using a client (eg Thunderbird); security is therefore ok (actually I gave full control to the user) eg Public/Newsletters/SomeCompany - *BUT* running a sieve script to store to Public/Newsletters/SomeCompany returns the following in the logs: "failed to store into mailbox 'Public/Newsletters/SomeCompany': Permission denied." Any tip? Thank you for your help. Greetz

2 1

panic when doveadm sieve put between multiple hosts
by Tyler Jachetta 31 Jan '17

31 Jan '17

Dovecot version: 2.2.25 (7be1766) I’m looking into an issue we’re having with a new setup. We have one fronted host with two backend hosts, and we’re attempting to use doveadm to allow us to administer sieve on the frontend and have it replicated to the backend hosts. When I attempt to use doveadm sieve put on the frontend host, i get the following on the frontend host: frontend-machine $ cat /tmp/default.sieve | doveadm sieve put default doveadm(root): Error: doveadm server disconnected before handshake: Connection reset by peer doveadm(root): Error: 10.1.11.82:10993: Command sieve put failed for root: Connection reset by peer when this happens, on the backend, I see this in /var/log/maillog: Jan 9 17:00:35 was-imap1 dovecot: doveadm: Panic: epoll_ctl(add, 0) failed: Operation not permitted (fd doesn't support epoll - instead of '<file', try 'cat file|') Jan 9 17:00:35 was-imap1 dovecot: doveadm: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x8d52e) [0x7f7a86ba952e] -> /usr/lib64/dovecot/libdovecot.so.0(+0x8d60e) [0x7f7a86ba960e] -> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7a86b481b6] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_add+0x147) [0x7f7a86bbe067] -> /usr/lib64/dovecot/libdovecot.so.0(+0xa0311) [0x7f7a86bbc311] -> /usr/lib64/dovecot/libdovecot.so.0(io_add+0xd) [0x7f7a86bbc3bd] -> dovecot/doveadm-server(doveadm_mail_get_input+0xde) [0x7f7a875c53de] -> dovecot/doveadm-server(doveadm_mail_single_user+0x73) [0x7f7a875c5633] -> dovecot/doveadm-server(+0x2874d) [0x7f7a875c574d] -> dovecot/doveadm-server(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x27d) [0x7f7a875c65fd] -> dovecot/doveadm-server(doveadm_cmd_run_ver2+0x50c) [0x7f7a875d492c] -> dovecot/doveadm-server(+0x3b223) [0x7f7a875d8223] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7f7a86bbce8c] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xff) [0x7f7a86bbe2ef] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f7a86bbcf15] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f7a86bbd0c8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f7a86b4e613] -> dovecot/doveadm-server(main+0x186) [0x7f7a875b6276] -> /lib64/libc.so.6(__libc_start_main+0xf5) [0x7f7a8677bb15] -> dovecot/doveadm-server(+0x19321) [0x7f7a875b6321] Jan 9 17:00:36 was-imap1 dovecot: doveadm: Fatal: master: service(doveadm): child 28542 killed with signal 6 (core dumped) Now, if I log in to either of the backend hosts, I can run the sieve put command and it all works out fine, so it’s something in the communication between the frontend and backend. dovecot -n output for both a frontend and backend below frontend-machine $ dovecot -n # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.15 (97b3da0) # OS: Linux 3.10.0-327.18.2.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_username_format = %Ln director_mail_servers = 10.1.11.82 10.1.11.83 director_servers = 10.1.11.81 director_username_hash = %Ln doveadm_port = 10993 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 index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = proxy=y nopassword=y ssl=any-cert driver = static } plugin { sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap pop3 lmtp sieve service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 1109 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 10993 } } service imap-login { executable = imap-login director } service imap { process_limit = 250 } service ipc { unix_listener ipc { user = dovecot } } service managesieve-login { executable = managesieve-login director } service pop3-login { executable = pop3-login director } ssl = required ssl_ca = </etc/pki/CA/ca-cert-***.pem ssl_cert = </etc/pki/tls/certs/dovecot.cert ssl_client_ca_file = </etc/pki/CA/ca-cert-***.pem ssl_key = </etc/pki/tls/private/dovecot.key ssl_protocols = !SSLv2 !SSLv3 ssl_require_crl = no userdb { driver = passwd } protocol doveadm { auth_socket_path = director-userdb } protocol sieve { passdb { args = proxy=y nopassword=y starttls=any-cert driver = static name = } } local 10.1.11.0/24 { doveadm_password = # hidden, use -P to show it } backend-machine $ dovecot -n # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.15 (97b3da0) # OS: Linux 3.10.0-327.18.2.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_username_format = %Ln default_vsz_limit = 2 G lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_location = maildir:~/Maildir mail_plugins = " notify replication" 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 index ihave duplicate mime foreverypart extracttext mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / } passdb { driver = pam } plugin { mail_replica = tcp:10.1.11.82:10993 sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap pop3 lmtp sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service doveadm { inet_listener { port = 10993 } } service lmtp { inet_listener lmtp { port = 24 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl = required ssl_ca = </etc/pki/CA/ca-cert-***.pem ssl_cert = </etc/pki/tls/certs/dovecot.cert ssl_client_ca_file = </etc/pki/CA/ca-cert-***.pem ssl_key = </etc/pki/tls/private/dovecot.key ssl_protocols = !SSLv2 !SSLv3 ssl_require_crl = no userdb { driver = passwd } protocol lmtp { auth_username_format = %Ln info_log_path = /var/log/dovecot/lmtp.log mail_plugins = " notify replication sieve" postmaster_address = postmaster(a)***global.com } protocol sieve { passdb { args = proxy=y nopassword=y starttls=any-cert driver = static name = } } local 10.1.11.0/24 { doveadm_password = # hidden, use -P to show it }

2 1

dovecot 2.2.18 replication I/O Timeout
by Jan Büren 31 Jan '17

31 Jan '17

Dear list, I am having an issue like this http://www.dovecot.org/list/dovecot-cvs/2014-September/024898.html with my current dovecot 2.2.18 Concret: doveadm -Dv replicator replicate -p high -f info throws an I/O Timeout error and the only thing I can see are some lock issues: Error: Couldn't lock /var/vmail/info/.dovecot-sync.lock: Timed out after 30 seconds Can I debug the communication one level deeper? I replicate over a somewhat slow DSL connection. I had the some problem with dovecot 2.2.9 and after upgrading to 2.2.15 everything went smoothly, just a wild guess, maybe the timeout_reset was removed again? Well, doesn't look like it: https://github.com/dovecot/core/blob/master/src/doveadm/dsync/dsync-ibc-str… or https://github.com/dovecot/core/blame/master/src/doveadm/dsync/dsync-ibc-st… Some debug hints would be nice. Thanks! Jan -- Blog http://blog.kivitendo.de/ kivitendo GmbH Jan Büren Kölnstr. 311 53117 Bonn USt-IdNr. DE292363254 Telefon: 0228 92 98 2012 persönliche Durchwahl: 0228 92 97 8965

1 0

Auth cache does not take %real_rip into account
by Tom Sommer 31 Jan '17

31 Jan '17

I run a Director setup with a webmail in front, the webmail is in login_trusted_networks and sends IMAP-ID x-original-ip to log the client IP. If I enable auth_debug on the director, I see that the cache key contains the client IP, and not the %real_rip. This is causing problems because in my passdb SQL query, I use the %real_rip to determine if login is allowed. Should %real_rip not be added to the auth cache key? Or should it be the cache key instead of the %rip? Thanks -- Tom

1 0

Re: dovecot mdbox never fix broken indexes
by Andrey Melnikov 31 Jan '17

31 Jan '17

2017-01-30 11:43 GMT+03:00 Aki Tuomi <aki.tuomi(a)dovecot.fi>: > Hi! > > Please send these to dovecot(a)dovecot.org instead of us directly. Thank you. Ok, added to cc. > Also, did you try force-resync? Not help. # doveadm force-resync -u altek(a)altek.info \* doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332136) doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: rebuilding indexes doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332196) doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332212) doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: rebuilding indexes doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332272) doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332288) doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: rebuilding indexes doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332348) doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332364) doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: rebuilding indexes doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332424) doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332440) doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: rebuilding indexes doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332500) doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index doveadm(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index in logs after force-resync Jan 30 11:49:23 mail dovecot: lmtp(21946): Connect from ::1 Jan 30 11:49:23 mail dovecot: lmtp(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332516) Jan 30 11:49:23 mail dovecot: lmtp(altek(a)altek.info): Error: Log synchronization error at seq=63,offset=58292 for /srv/vmail/altek.info/altek/storage/dovecot.map.index: Extension record inc drops number below zero (uid=5845, diff=-1, orig=0) Jan 30 11:49:23 mail dovecot: lmtp(altek(a)altek.info): Error: Log synchronization error at seq=63,offset=78516 for /srv/vmail/altek.info/altek/storage/dovecot.map.index: Extension record inc drops number below zero (uid=11497, diff=-1, orig=0) Jan 30 11:49:23 mail dovecot: lmtp(altek(a)altek.info): Error: Log synchronization error at seq=63,offset=201684 for /srv/vmail/altek.info/altek/storage/dovecot.map.index: Extension record inc drops number below zero (uid=14249, diff=-2, orig=0) Jan 30 11:49:23 mail dovecot: lmtp(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index Jan 30 11:49:24 mail dovecot: lmtp(altek(a)altek.info): 7inAKRP+jli6VQAANAhlbg: msgid=<7e59e033dac89045b4429bde28e559aa7ca6662c(a)41sem-glav.ru>: saved mail to INBOX Jan 30 11:49:24 mail dovecot: lmtp(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: Inconsistency in map index (63,31880 != 63,332640) Jan 30 11:49:24 mail dovecot: lmtp(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index Jan 30 11:49:24 mail dovecot: lmtp(altek(a)altek.info): Warning: mdbox /srv/vmail/altek.info/altek/storage: rebuilding indexes Jan 30 11:49:24 mail dovecot: lmtp(altek(a)altek.info): Warning: fscking index file /srv/vmail/altek.info/altek/storage/dovecot.map.index Jan 30 11:49:24 mail dovecot: lmtp(21946): Disconnect from ::1: Successful quit > On 30.01.2017 10:20, Andrey Melnikov wrote: >> Hello. >> >> After power crash mdbox index corrupted and dovecot never fix it. >> >> -- cut -- >> Jan 30 09:36:05 mail dovecot: lmtp(altek(a)altek.info): Warning: mdbox >> /srv/vmail/altek.info/altek/storage: Inconsistency in map index >> (63,31880 != 63,327528) >> Jan 30 09:36:05 mail dovecot: lmtp(altek(a)altek.info): Error: Log >> synchronization error at seq=63,offset=58292 for >> /srv/vmail/altek.info/altek/storage/dovecot.map.index: Extension >> record inc drops number below zero (uid=5845, diff=-1, orig=0) >> Jan 30 09:36:05 mail dovecot: lmtp(altek(a)altek.info): Error: Log >> synchronization error at seq=63,offset=78516 for >> /srv/vmail/altek.info/altek/storage/dovecot.map.index: Extension >> record inc drops number below zero (uid=11497, diff=-1, orig=0) >> Jan 30 09:36:05 mail dovecot: lmtp(altek(a)altek.info): Error: Log >> synchronization error at seq=63,offset=201684 for >> /srv/vmail/altek.info/altek/storage/dovecot.map.index: Extension >> record inc drops number below zero (uid=14249, diff=-2, orig=0) >> Jan 30 09:36:05 mail dovecot: lmtp(altek(a)altek.info): Warning: fscking >> index file /srv/vmail/altek.info/altek/storage/dovecot.map.index >> Jan 30 09:36:05 mail dovecot: lmtp(altek(a)altek.info): >> gfPAFtXejlhbOAAANAhlbg: >> msgid=<E1cY5ZK-00037Z-AM(a)mx-out.depo-magazine.ru>: saved mail to INBOX >> Jan 30 09:36:05 mail dovecot: lmtp(altek(a)altek.info): Warning: mdbox >> /srv/vmail/altek.info/altek/storage: Inconsistency in map index >> (63,31880 != 63,327652) >> Jan 30 09:36:05 mail dovecot: lmtp(altek(a)altek.info): Warning: fscking >> index file /srv/vmail/altek.info/altek/storage/dovecot.map.index >> Jan 30 09:36:05 mail dovecot: lmtp(altek(a)altek.info): Warning: mdbox >> /srv/vmail/altek.info/altek/storage: rebuilding indexes >> Jan 30 09:36:05 mail dovecot: lmtp(altek(a)altek.info): Warning: fscking >> index file /srv/vmail/altek.info/altek/storage/dovecot.map.index >> Jan 30 09:43:32 mail dovecot: pop3-login: Login: >> user=<altek(a)altek.info>, method=PLAIN, rip=192.168.0.28, >> lip=192.168.0.1, mpid=14619, session=<azNKIkpHtg7AqAAc> >> Jan 30 09:43:35 mail dovecot: pop3(altek(a)altek.info): Warning: mdbox >> /srv/vmail/altek.info/altek/storage: Inconsistency in map index >> (63,31880 != 63,327728) >> Jan 30 09:43:35 mail dovecot: pop3(altek(a)altek.info): Warning: fscking >> index file /srv/vmail/altek.info/altek/storage/dovecot.map.index >> Jan 30 09:43:35 mail dovecot: pop3(altek(a)altek.info): Warning: mdbox >> /srv/vmail/altek.info/altek/storage: rebuilding indexes >> Jan 30 09:43:35 mail dovecot: pop3(altek(a)altek.info): Warning: fscking >> index file /srv/vmail/altek.info/altek/storage/dovecot.map.index >> Jan 30 09:43:35 mail dovecot: pop3(altek(a)altek.info): Disconnected: >> Logged out top=0/0, retr=4/1676349, del=0/1153, size=439478778 >> Jan 30 09:43:35 mail dovecot: pop3(altek(a)altek.info): Warning: mdbox >> /srv/vmail/altek.info/altek/storage: Inconsistency in map index >> (63,31880 != 63,327788) >> Jan 30 09:43:35 mail dovecot: pop3(altek(a)altek.info): Warning: fscking >> index file /srv/vmail/altek.info/altek/storage/dovecot.map.index >> Jan 30 09:43:35 mail dovecot: pop3(altek(a)altek.info): Warning: fscking >> index file /srv/vmail/altek.info/altek/storage/dovecot.map.index >> Jan 30 09:45:11 mail dovecot: lmtp(altek(a)altek.info): Warning: mdbox >> /srv/vmail/altek.info/altek/storage: Inconsistency in map index >> (63,31880 != 63,327804) >> Jan 30 09:45:11 mail dovecot: lmtp(altek(a)altek.info): Error: Log >> synchronization error at seq=63,offset=58292 for >> /srv/vmail/altek.info/altek/storage/dovecot.map.index: Extension >> record inc drops number below zero (uid=5845, diff=-1, orig=0) >> Jan 30 09:45:11 mail dovecot: lmtp(altek(a)altek.info): Error: Log >> synchronization error at seq=63,offset=78516 for >> /srv/vmail/altek.info/altek/storage/dovecot.map.index: Extension >> record inc drops number below zero (uid=11497, diff=-1, orig=0) >> Jan 30 09:45:11 mail dovecot: lmtp(altek(a)altek.info): Error: Log >> synchronization error at seq=63,offset=201684 for >> /srv/vmail/altek.info/altek/storage/dovecot.map.index: Extension >> record inc drops number below zero (uid=14249, diff=-2, orig=0) >> Jan 30 09:45:11 mail dovecot: lmtp(altek(a)altek.info): Warning: fscking >> index file /srv/vmail/altek.info/altek/storage/dovecot.map.index >> Jan 30 09:45:11 mail dovecot: lmtp(altek(a)altek.info): >> vwxyI/fgjlgyOQAANAhlbg: msgid=<003a01d27ac4$639789e0$2ac69da0$@ru>: >> saved mail to INBOX >> Jan 30 09:45:11 mail dovecot: lmtp(altek(a)altek.info): Warning: mdbox >> /srv/vmail/altek.info/altek/storage: Inconsistency in map index >> (63,31880 != 63,327928) >> Jan 30 09:45:11 mail dovecot: lmtp(altek(a)altek.info): Warning: fscking >> index file /srv/vmail/altek.info/altek/storage/dovecot.map.index >> Jan 30 09:45:11 mail dovecot: lmtp(altek(a)altek.info): Warning: mdbox >> /srv/vmail/altek.info/altek/storage: rebuilding indexes >> Jan 30 09:45:12 mail dovecot: lmtp(altek(a)altek.info): Warning: fscking >> index file /srv/vmail/altek.info/altek/storage/dovecot.map.index >> -- cut -- >

2 3

2.2.26.0 : accessing "mdbox_deleted" content destroys indexes
by Benoit Branciard 31 Jan '17

31 Jan '17

Accessing or listing "mdbox_deleted" contents seems to destroy MDBOX indexes. Examples of commands which triggers this problem ($home being the home directory of $user, and mail_location being mdbox:~/mdbox): doveadm -o mail="mdbox_deleted:$home/mdbox" -f table mailbox status -u "$user" 'messages vsize' INBOX doveadm -v import -s -u "$user" "mdbox_deleted:$home/mdbox" restored-mail ALL The above "doveadm mailbox status" command outputs an error: doveadm(user): Error: Log synchronization error at seq=1,offset=104908 for (in-memory index): Append with UID 1, but next_uid = 5227 doveadm(user): Warning: fscking index file (in-memory index) Subsequent "doveadm mailbox status -u $user 'messages vsize'" on the active mailbox report empty folders (null messages and vsize), whereas folders actually aren't empty. Workaround: this problem is corrected by a "doveadm search -u $user all", which obviously forces indexes to be rebuilt. Vesion: 2.2.26.0 (23d1de6) (Debian jessie-backports package) We did *not* have this problem in 2.2.24 version (previous Debian jessie-backports package). We use following mail_location with explicit DIRNAME (don't know if that matters): mail_location = mdbox:~/mdbox:DIRNAME=_@@_dbox-Mails_@@_ I tested with and without appending ":DIRNAME=_@@_dbox-Mails_@@_" to mail="mdbox_deleted:$home/mdbox" with same results. -- Benoit BRANCIARD Service InfraStructures (SIS) Direction du Système d'Information et des Usages Numériques (DSIUN) Université Paris 1 Panthéon-Sorbonne Centre Pierre Mendès France 90 rue de Tolbiac - 75634 Paris cedex 13 - France Bur. B406 - Tél +33 1 44 07 89 68 - Fax +33 1 44 07 89 66 Accueil: +33 1 44 07 89 65 - Assistance-DSIUN(a)univ-paris1.fr http://dsi.univ-paris1.fr

1 1

Re: tlsv1 alert unknown ca: SSL alert number 48
by Joseph Tam 31 Jan '17

31 Jan '17

> Jan 28 22:42:44 dovecot: imap-login: Disconnected (no auth attempts in 0 > secs): user=<>, rip=192.168.1.16, lip=192.168.1.3, TLS: SSL_read() > failed: error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown > ca: SSL alert number 48, session= > ... > # SSL/TLS support: yes, no, required. <doc/wiki/SSL.txt> > ssl = yes > ssl_cert = </etc/ssl/certs/dovecot.pem > ssl_key = </etc/ssl/private/dovecot.pem > ssl_ca = </etc/ssl/private/cert.pem Are you using client verification (i.e. mutual authentication of mail client and server)? If not, just comment out ssl_ca. Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: Moving to new password scheme
by Joseph Tam 30 Jan '17

30 Jan '17

Okn Mon, 30 Jan 2017, dovecot-request(a)dovecot.org wrote: > OK, I have the dovecot.conf stuff working so that it calls the external > script and I have that script spitting out the login and a SHA256-CRYPT > password with hash: > > Thu Jan 26 06:45:54 MST 2017 > USER: xander(a)xanmax.com > {SHA512-CRYPT}$6$CfKc0NdiRkWOisjL$kHAx2oxB? Did you truncate the results? This hash looks far too short to be a real SHA512 hash. Joseph Tam <jtam.home(a)gmail.com>

1 0