Panic: file imap-client.c: line 1204 (client_handle_input): assertion failed: (o_stream_is_corked(client->output))
Running Dovecot from the daily builds: 2:2.3.0~alpha0-1~auto+1287 in
an proxy setup:
auth_mechanisms = plain login
default_vsz_limit = 1 G
imapc_host = .charite.de
imapc_port = 993
imapc_ssl = imaps
imapc_ssl_verify = no
listen = *,::
mail_gid = imapproxy
mail_home = /home/imapproxy/%u
mail_location = imapc:~/imapc
mail_plugins = mail_log notify
mail_uid = imapproxy
passdb {
args = host=.charite.de port=993 ssl=imaps
ssl_ca_file=/etc/ssl/certs/ca-certificates.crt
default_fields = userdb_imapc_user=%u userdb_imapc_password=%w
userdb_imapc_host=.charite.de userdb_imapc_ssl=imaps
userdb_imapc_port=993
driver = imap
}
postmaster_address = postmas...@charite.de
protocols = imap
service auth {
inet_listener {
address = 127.0.0.1
port = 12345
}
}
ssl = required
ssl_ca = : Panic:
file imap-client.c: line 1204 (client_handle_input): assertion failed:
(o_stream_is_corked(client->output))
Dec 14 14:35:28 mproxy dovecot: imap(voea)<79305>: Panic:
file imap-client.c: line 1204 (client_handle_input): assertion failed:
(o_stream_is_corked(client->output))
Dec 14 14:35:28 mproxy dovecot: imap(voea)<79275>: Error:
Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xc3cd5)
[0x7fe40d9cccd5] -> /usr/lib/dovecot/libdovecot.so.0(+0xc3dbc)
[0x7fe40d9ccdbc] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7fe40d942f8e] -> dovecot/imap [voea
193.175.2.18](client_handle_input+0x2a8)
[0x564f326e0e18] -> dovecot/imap [voea
193.175.2.18](client_continue_pending_input+0x80)
[0x564f326e0f20] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69)
[0x7fe40d9e48f9] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a)
[0x7fe40d9e612a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52)
[0x7fe40d9e4a02] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38)
[0x7fe40d9e4c18] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13)
[0x7fe40d965b63] -> dovecot/imap [voea 193.175.2.18](main+0x333)
[0x564f326d3113] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)
[0x7fe40d5623f1] -> dovecot/imap [voea 193.175.2.18](+0xe2f1)
[0x564f326d32f1]
Dec 14 14:35:28 mproxy dovecot: imap(voea)<79305>: Error:
Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xc3cd5)
[0x7faa962d8cd5] -> /usr/lib/dovecot/libdovecot.so.0(+0xc3dbc)
[0x7faa962d8dbc] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0)
[0x7faa9624ef8e] -> dovecot/imap [voea
193.175.2.18](client_handle_input+0x2a8)
[0x5615124cde18] -> dovecot/imap [voea
193.175.2.18](client_continue_pending_input+0x80)
[0x5615124cdf20] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69)
[0x7faa962f08f9] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a)
[0x7faa962f212a] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52)
[0x7faa962f0a02] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38)
[0x7faa962f0c18] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13)
[0x7faa96271b63] -> dovecot/imap [voea 193.175.2.18](main+0x333)
[0x5615124c0113] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf1)
[0x7faa95e6e3f1] -> dovecot/imap [voea 193.175.2.18](+0xe2f1)
[0x5615124c02f1]
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] v2.2.34 released
* Timo Sirainen : > https://dovecot.org/releases/2.2/dovecot-2.2.34.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.34.tar.gz.sig Currently, I'm not getting any updates for prebuilt packages (I'm on Ubuntu Xenial 16.04.4) - I'm stuck on 2.2.22: ii dovecot-core1:2.2.22-1ubuntu2.6 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.22-1ubuntu2.6 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-lmtpd 1:2.2.22-1ubuntu2.6 amd64 secure POP3/IMAP server - LMTP server using these /etc/apt/sources.list entry: # Dovecot 2.2 deb http://xi.dovecot.fi/debian/ stable-auto/dovecot-2.2 main What is the current apt repository I could use? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] v2.2.34 released
* Aki Tuomi : > > What is the current apt repository I could use? > > > > We do not provide official packages for 2.2.x versions, only 2.3 and > later. I switched to 2.3 now. > XI is not intended for production usage. Most of the time it works ok (it's only for backup purposes) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
I have an email which cannot be delivered using LMTP: Mar 2 15:26:54 mail-cbf dovecot: lmtp(backup@backup.invalid)<29736>: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p)) Mar 2 15:26:54 mail-cbf dovecot: lmtp(backup@backup.invalid)<29736>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xc6aca) [0x7f7fb50d3aca] -> /usr/lib/dovecot/libdovecot.so.0(+0xc6bad) [0x7f7fb50d3bad] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7fb5045721] -> /usr/lib/dovecot/libdovecot.so.0(smtp_address_write+0x21d) [0x7f7fb504931d] -> /usr/lib/dovecot/libdovecot.so.0(smtp_address_encode+0x21) [0x7f7fb5049411] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x3774) [0x7f7fb56d0774] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x3abf) [0x7f7fb56d0abf] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_finish+0x7c) [0x7f7fb53c858c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_copy+0x104) [0x7f7fb53baeb4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_copy+0x46) [0x7f7fb53e13f6] -> /usr/lib/dovecot/libdovecot-lda.so.0(+0x3999) [0x7f7fb56d0999] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x48956) [0x7f7fb53c8956] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x1ac) [0x7f7fb56d12ac] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x1f6) [0x7f7fb56d1916] -> dovecot/lmtp(lmtp_local_data+0x610) [0x560dfd665dc0] -> dovecot/lmtp(cmd_data_continue+0x233) [0x560dfd664b53] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a6e0) [0x7f7fb50576e0] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x69) [0x7f7fb50eb649] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x109) [0x7f7fb50ecf29] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x52) [0x7f7fb50eb752] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f7fb50eb968] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f7fb50682a3] -> dovecot/lmtp(main+0x23d) [0x560dfd663c3d] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f7fb4c63830] -> dovecot/lmtp(_start+0x29) [0x560dfd663d79] Mar 2 15:26:55 mail-cbf dovecot: lmtp(backup@backup.invalid)<29736>: Fatal: master: service(lmtp): child 29736 killed with signal 6 (core dumped) Using dovecot 2:2.3.0.1-6 packages on Ubuntu 16.04 The address causing the error is: From: =?utf-8?Q?Dorit_M=C3=BCller?= Note the "umlaut" in the email address... :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
> 1) Who or what is sending messages like that (without the proper > capability support available at the server side)? I think that was some sort of commercial mass mailer: List-Unsubscribe: <http://newsletter.jomec.de/rmftlp.php?cid=...> > 2) Why would an MTA accept this message? What software is doing that > (and why)? Postfix. It was just in the headers, so it was not relevvant for delivery. > 3) What does the envelope address look like? Do both header and envelope > have that umlaut (unlikely, because Dovecot should reject that already)? > Maybe this could be fixed by substituting the envelope address if it is > sufficiently similar. Envelope sender is: bounce+15...@bounce.crsend.com > 4) Where does this fail actually? At some point it is trying to > construct an SMTP (RFC 5321) address from the header address (RFC 5322). > Do you have a GDB backtrace with proper symbols? Don't have a backtrace yet, but since the mail is still in the queue I could try getting one. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
> I wasn't able to confirm it since I've not moved to 2.3 yet and the 2.2 > code is different, but this should happen if there are characters from > 0x01 to 0x1f or from 0x7f to 0xff in the local part. Yeah, I was running 2.2.x prior to my upgrade and never encountered this. > By the way I noticed that if Postfix has SMTPUTF8 enabled, then it won't > hand off messages with this content to Dovecot since Dovecot does not > advertise support for SMTPUTF8. If SMTPUTF8 is unavailable or disabled > then Postfix passes on those characters. I suspect that Ralph has > SMTPUTF8 turned off. Ah I see: When a message is received with the SMTPUTF8 request, Postfix will deliver the message to a non-SMTPUTF8 SMTP or LMTP server ONLY if: * No message header value contains UTF-8. * The envelope sender address contains no UTF-8, * No envelope recipient address for that specific SMTP/LMTP delivery transaction contains UTF-8. I wonder if this will break a lot. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
* A.L.E.C : > On 03/02/2018 03:32 PM, Ralf Hildebrandt wrote: > > The address causing the error is: > > > > From: =?utf-8?Q?Dorit_M=C3=BCller?= > > > > Note the "umlaut" in the email address... :) > > This is about SMTPUTF8 (RFC6531). Looks like your only option is to disable > smtputf8_enable in Postfix config. It IS already disabled. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de signature.asc Description: PGP signature
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
* John Fawcett : > Postfix already permitted UTF8 in message headers and local part of the > address before the introduction of SMTPUTF8 and that has remained so. I > don't believe turning off SMTPUTF8 in Postfix will change the behaviour > in this case. I agree. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de signature.asc Description: PGP signature
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
> From the code in lib-smtp/smtp-address.c function smtp_address_write, it > looks as though the assertion will happen whenever there is a non ascii > char that is also non qpair in the local part, ie > !smtp_char_is_atext(*p) and !smtp_char_is_qpair(*p). Could somebody please point me in the direction how to obtain a coredump here? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de signature.asc Description: PGP signature
Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
* Ralf Hildebrandt : > > From the code in lib-smtp/smtp-address.c function smtp_address_write, it > > looks as though the assertion will happen whenever there is a non ascii > > char that is also non qpair in the local part, ie > > !smtp_char_is_atext(*p) and !smtp_char_is_qpair(*p). > > Could somebody please point me in the direction how to obtain a > coredump here? I found sysctl -w fs.suid_dumpable=2 but where will coredumps be written? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de signature.asc Description: PGP signature
Coredump: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
0x56239bde2238, 0x0}
#21 cmd_data_continue (conn_ctx=0x56239bdbc338, cmd=0x56239bde1ea8,
trans=0x56239bde0d68) at commands.c:190
client = 0x56239bdbc338
state = 0x56239bdbc3c0
data_input =
data =
size = 543
ret =
__func__ = "cmd_data_continue"
#22 0x7fea19d566e0 in cmd_data_handle_input (cmd=0x56239bde1ea8) at
smtp-server-cmd-data.c:199
conn = 0x56239bde0930
callbacks = 0x56239abd27a0
command = 0x56239bde1ea8
data_cmd = 0x56239bde83e8
ret =
__func__ = "cmd_data_handle_input"
#23 0x7fea19dea649 in io_loop_call_io (io=0x56239bdba970) at ioloop.c:614
ioloop = 0x56239bd82c70
t_id = 2
__func__ = "io_loop_call_io"
#24 0x7fea19debf29 in io_loop_handler_run_internal
(ioloop=ioloop@entry=0x56239bd82c70) at ioloop-epoll.c:222
ctx = 0x56239bd849f0
ret =
__func__ = "cmd_data_handle_input"
#23 0x7fea19dea649 in io_loop_call_io (io=0x56239bdba970) at ioloop.c:614
ioloop = 0x56239bd82c70
t_id = 2
__func__ = "io_loop_call_io"
#24 0x7fea19debf29 in io_loop_handler_run_internal
(ioloop=ioloop@entry=0x56239bd82c70) at ioloop-epoll.c:222
ctx = 0x56239bd849f0
---Type to continue, or q to quit---
io =
tv = {
tv_sec = 299,
tv_usec = 999816
}
events_count =
msecs =
ret = 1
i = 0
j =
call =
__func__ = "io_loop_handler_run_internal"
#25 0x7fea19dea752 in io_loop_handler_run (ioloop=) at
ioloop.c:666
No locals.
#26 0x7fea19dea968 in io_loop_run (ioloop=0x56239bd82c70) at ioloop.c:639
__func__ = "io_loop_run"
#27 0x7fea19d672a3 in master_service_run (service=0x56239bd82b00,
callback=) at master-service.c:767
No locals.
#28 0x56239a9ccc3d in main (argc=1, argv=0x56239bd82890) at main.c:159
set_roots = {0x56239abd3280 ,
0x56239abd31e0 , 0x56239abd2600
, 0x0}
service_flags =
storage_service_flags = (MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT |
MAIL_STORAGE_SERVICE_FLAG_USERDB_LOOKUP |
MAIL_STORAGE_SERVICE_FLAG_TEMP_PRIV_DROP |
MAIL_STORAGE_SERVICE_FLAG_NO_LOG_INIT |
MAIL_STORAGE_SERVICE_FLAG_NO_IDLE_TIMEOUT)
tmp_base_dir = 0x56239bd7a040 "tp data)"
c =
error = 0x0
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@charite.de | https://www.charite.de
Re: lmtp panic with many recipients
* Stephan Bosch : > > > Op 08/05/2018 om 10:34 schreef Olaf Hopp: > > Hi, > > > > I had an email with 58 recipients in the "To" and 13 in the "CC" > > Delivering it from exim to dovecot lmtp panics (see below) > > Panic: file smtp-address.c: line 533 (smtp_address_write): assertion > > failed: (smtp_char_is_qpair(*p)) > > > > # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf > > # Pigeonhole version 0.5.devel (61b47828) > > # OS: Linux 2.6.32-696.23.1.el6.x86_64 x86_64 CentOS release 6.9 (Final) > > > > Do you have an example e-mail that triggers the problem and the sieve > scripts that are involved for the recipient that causes the crash? That looks a bit like https://www.mail-archive.com/dovecot@dovecot.org/msg72690.html -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Re: lmtp panic with many recipients
* Olaf Hopp : > Seems to be. There is a > =?iso-8859-1?Q?s=2Ev=F6gele=40X=2Ede?= > within the "To"-header, together with the line > not address :all :comparator "i;octet" :contains "To" "robocup" > in my global sieve_before script seems to trigger it > > Fucking german umlaut. Yep, that's the one. But ... hasn't this particular error already been fixed? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de smime.p7s Description: S/MIME cryptographic signature
expunge not removing attachments?
I have a large mail backup folder backup@backup.invalid; I'm cleaning up daily like this: infimum=`date -d "-4 day" +"%Y-%m-%d"` doveadm expunge -u backup@backup.invalid mailbox INBOX SAVEDBEFORE $infimum doveadm purge -u backup@backup.invalid yet I see this: # find attachments/ -type f -ctime +5 | wc -l 7522 # find attachments/ -type f | wc -l 127579 # find attachments/ -type f -mtime +5 | wc -l 14361 # find attachments/ -type f | wc -l 127793 About 5.9% of the files in attachments and below are older than 5 days. Why? Is that normal? using dovecot 2:2.3.1-1 from the official repos. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
QUERY string clarification
The manpage https://wiki.dovecot.org/Tools/Doveadm/SearchQuery specifies: BODY string Matches messages, which contain string in the body part. and a bit further down: TEXT string Matches messages, which contain string in the message body. Where's the difference? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Crash during "doveadm import"
t message-header-parser.c:85 #20 0x7735239f in message_parse_header (input=, hdr_size=hdr_size@entry=0x0, flags=flags@entry=MESSAGE_HEADER_PARSER_FLAG_CLEAN_ONELINE, callback=callback@entry=0x776f2cb0 , context=context@entry=0x7fffdcf0) at message-header-parser.c:392 #21 0x776f3741 in search_arg_match_text (ctx=0x5585bad0, args=0x558216d0) at index-search.c:759 #22 search_match_once (ctx=0x5585bad0) at index-search.c:1398 #23 0x776f49f4 in search_match_next (ctx=0x5585bad0) at index-search.c:1505 #24 search_more_with_mail (mail=, ctx=0x5585bad0) at index-search.c:1621 #25 search_more_with_prefetching (mail_r=, ctx=) at index-search.c:1703 #26 search_more (ctx=ctx@entry=0x5585bad0, mail_r=mail_r@entry=0x7fffde20) at index-search.c:1777 #27 0x776f51cd in index_storage_search_next_nonblock (_ctx=0x5585bad0, mail_r=0x7fffdef0, tryagain_r=0x7fffde87) at index-search.c:1805 #28 0x776776e2 in mailbox_search_next_nonblock (ctx=0x5585bad0, mail_r=0x7fffdef0, tryagain_r=) at mail-storage.c:2307 #29 0x7767774d in mailbox_search_next (ctx=0x5585bad0, mail_r=mail_r@entry=0x7fffdef0) at mail-storage.c:2292 #30 0x55586c02 in doveadm_mail_iter_next (iter=, mail_r=mail_r@entry=0x7fffdef0) at doveadm-mail-iter.c:161 #31 0x55585a33 in cmd_import_box (search_args=, info=0x5584f820, dest_user=, ctx=0x5581fda8) at doveadm-mail-import.c:143 #32 cmd_import_run (_ctx=0x5581fda8, user=0x558374a8) at doveadm-mail-import.c:203 #33 0x55580518 in doveadm_mail_next_user (ctx=ctx@entry=0x5581fda8, error_r=error_r@entry=0x7fffe0d0) at doveadm-mail.c:462 #34 0x5558116e in doveadm_mail_single_user (ctx=ctx@entry=0x5581fda8, error_r=error_r@entry=0x7fffe0d0) at doveadm-mail.c:492 #35 0x55581256 in doveadm_mail_cmd_exec (ctx=ctx@entry=0x5581fda8, wildcard_user=wildcard_user@entry=0x0) at doveadm-mail.c:653 #36 0x555820ce in doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=) at doveadm-mail.c:1149 #37 0x55592fa8 in doveadm_cmd_run_ver2 (argc=8, argv=0x557f6bb8, cctx=cctx@entry=0x7fffe2c0) at doveadm-cmd.c:575 #38 0x55592ff7 in doveadm_cmd_try_run_ver2 (cmd_name=, argc=, argv=, cctx=0x7fffe2c0) at doveadm-cmd.c:497 #39 0x55570641 in main (argc=, argv=) at doveadm.c:395 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Crash during "doveadm import"
* Ralf Hildebrandt : > Today I was looking for some spam and issued this command: > == > > doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox INBOX > header Reply-To bixrs.com This is dovecot from the package 2.3.10.1-3+ubuntu18.04 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Crash during "doveadm import"
* Ralf Hildebrandt : > Today I was looking for some spam and issued this command: > == > > doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox INBOX > header Reply-To bixrs.com Little typo on my part in the syntax: doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox "" mailbox INBOX header reply-to bixrs.com -> crash doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox "" mailbox INBOX header reply-to "" -> crash doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox "" mailbox INBOX header cc bixrs.com -> crash doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox "" mailbox INBOX header from bixrs.com -> no crash doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox "" mailbox INBOX header message-id bixrs.com -> no crash doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox "" mailbox INBOX header X-Spam yes --> no crash -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
doveadm crash on import
% doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox '' mailbox INBOX header Reply-To gmail.com results in: doveadm(restore@backup.invalid): Panic: fcntl(/home/copymail2/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log, write-lock, F_SETLKW) locking failed: Resource deadlock avoided (WRITE lock held by pid 37462) doveadm(restore@backup.invalid): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x42) [0x7fb131662d22] -> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fb131662e3e] -> /usr/lib/dovecot/libdovecot.so.0(+0xed75e) [0x7fb13166d75e] -> /usr/lib/dovecot/libdovecot.so.0(+0xed7a1) [0x7fb13166d7a1] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7fb1315c2beb] -> /usr/lib/dovecot/libdovecot.so.0(+0xf2932) [0x7fb131672932] -> /usr/lib/dovecot/libdovecot.so.0(file_wait_lock_error+0x26) [0x7fb131672966] -> /usr/lib/dovecot/libdovecot.so.0(file_wait_lock+0x20) [0x7fb131672a00] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_file_lock+0x90)[0x7fb131a28050] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_lock_head+0x3d)[0x7fb131a2d4dd] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_transaction_log_append_begin+0x3e)[0x7fb131a26a8e] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xf52f2) [0x7fb131a202f2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit_full+0x76)[0x7fb131a20826] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit+0x1c)[0x7fb131a208bc] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xdd619) [0x7fb131a08619] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_cache_add+0x214) [0x7fb131a08f24] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_header+0x5a5) [0x7fb1319eaef5] -> /usr/lib/dovecot/libdovecot.so.0(+0xc5b13) [0x7fb131645b13] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_memarea+0x74) [0x7fb13167ab14] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x29) [0x7fb13167ae49] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fb13167b7bd] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x68) [0x7fb13164c288] -> /usr/lib/dovecot/libdovecot.so.0(message_parse_header+0x4f) [0x7fb13164cc5f] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xc9f61) [0x7fb1319f4f61] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcb214) [0x7fb1319f6214] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x10d)[0x7fb1319f69ed] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x22)[0x7fb131978df2] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next+0x3d)[0x7fb131978e5d] -> doveadm(+0x31c14) [0x557ac63f1c14] -> doveadm(+0x2c518) [0x557ac63ec518] -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Re: doveadm crash on import
* Aki Tuomi : > What's process 37462? I'll need to reproduce. /root# doveadm import -u restore@backup.invalid mdbox:/home/copymail2/mdbox '' mailbox INBOX header Reply-To gmail.com doveadm(restore@backup.invalid): Panic: fcntl(/home/copymail2/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.log, write-lock, F_SETLKW) locking failed: Resource deadlock avoided (WRITE lock held by pid 41909) copymail 41909 2.3 0.1 156740 88020 ?S13:40 0:11 \_ dovecot/lmtp So it's an LMTP process that's writing to mdbox:/home/copymail2/mdbox -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
doveadm import uninterruptable?
I'm using % doveadm import -u restore@backup.invalid mdbox:/home/archive/mdbox "" mailbox INBOX header From $PATTERN sometimes, I mistype the pattern and immediately try to stop the doveadm command with CTRL-C - and this never succeeds. Is it inentional that I cannot interrupt the "doveadm import" command? Using 2.3.13 here. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Re: Dovecot v2.3.14 released
* Bjoern Franke : > Hi, > > > * Remove XZ/LZMA write support. Read support will be removed in future > > release. > > Will XZ/ZMA Read support be removed in the next release or just in some > future release? I'm a bit behind the curve: Why is it being removed at all? * reduce code size * better compression algorithms available * other -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de signature.asc Description: PGP signature
Re: [ext] Re: What is the state of SMTPUTF8 support?
> > It’s been some time since I last saw a mention of SMTPUTF8 here. Last > > time I heard about it, it was worked on. > > Does anybody have news about that? > > > > I didn’t get any answer. Does somebody know if there was any progress > in implementing the RFC 6531? http://www.postfix.org/SMTPUTF8_README.html -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Re: What is the state of SMTPUTF8 support?
* Ralf Hildebrandt : > > > It’s been some time since I last saw a mention of SMTPUTF8 here. Last > > > time I heard about it, it was worked on. > > > Does anybody have news about that? > > > > > > > I didn’t get any answer. Does somebody know if there was any progress > > in implementing the RFC 6531? > > http://www.postfix.org/SMTPUTF8_README.html Sorry, I was on the wrong list. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)
data_r=data_r@entry=0x7fffdc08, size_r=size_r@entry=0x7fffdc10, threshold=threshold@entry=1) at istream.c:745 #18 0x7734ba58 in i_stream_read_bytes (wanted=2, size_r=0x7fffdc10, data_r=0x7fffdc08, stream=) at ../../src/lib/istream.h:217 #19 message_parse_header_next (ctx=0x55869db0, hdr_r=hdr_r@entry=0x7fffdc70) at message-header-parser.c:85 #20 0x7734c432 in message_parse_header (input=, hdr_size=hdr_size@entry=0x0, flags=flags@entry=MESSAGE_HEADER_PARSER_FLAG_CLEAN_ONELINE, callback=callback@entry=0x776f1aa0 , context=context@entry=0x7fffdce0) at message-header-parser.c:392 #21 0x776f2561 in search_arg_match_text (ctx=0x55856fa0, args=0x558216d0) at index-search.c:759 #22 search_match_once (ctx=0x55856fa0) at index-search.c:1399 #23 0x776f385c in search_match_next (ctx=0x55856fa0) at index-search.c:1506 #24 search_more_with_mail (mail=, ctx=0x55856fa0) at index-search.c:1623 #25 search_more_with_prefetching (mail_r=, ctx=) at index-search.c:1705 #26 search_more (ctx=ctx@entry=0x55856fa0, mail_r=mail_r@entry=0x7fffde10) at index-search.c:1779 #27 0x776f404d in index_storage_search_next_nonblock (_ctx=0x55856fa0, mail_r=0x7fffdee0, tryagain_r=0x7fffde77) at index-search.c:1807 #28 0x77673f38 in mailbox_search_next_nonblock (ctx=0x55856fa0, mail_r=0x7fffdee0, tryagain_r=) at mail-storage.c:2307 #29 0x77673f9d in mailbox_search_next (ctx=0x55856fa0, mail_r=mail_r@entry=0x7fffdee0) at mail-storage.c:2292 #30 0x55586d52 in doveadm_mail_iter_next (iter=, mail_r=mail_r@entry=0x7fffdee0) at doveadm-mail-iter.c:160 #31 0x55585b13 in cmd_import_box (search_args=, info=0x5584e7b8, dest_user=, ctx=0x5581fdb8) at doveadm-mail-import.c:142 #32 cmd_import_run (_ctx=0x5581fdb8, user=0x558374b8) at doveadm-mail-import.c:202 #33 0x55580441 in doveadm_mail_next_user (ctx=ctx@entry=0x5581fdb8, error_r=error_r@entry=0x7fffe0c0) at doveadm-mail.c:462 #34 0x555810db in doveadm_mail_single_user (ctx=ctx@entry=0x5581fdb8, error_r=error_r@entry=0x7fffe0c0) at doveadm-mail.c:492 #35 0x555811c9 in doveadm_mail_cmd_exec (ctx=ctx@entry=0x5581fdb8, wildcard_user=wildcard_user@entry=0x0) at doveadm-mail.c:653 #36 0x5558209e in doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=) at doveadm-mail.c:1144 #37 0x555933ee in doveadm_cmd_run_ver2 (argc=10, argv=0x557f6bb8, cctx=cctx@entry=0x7fffe2b0) at doveadm-cmd.c:575 #38 0x55593447 in doveadm_cmd_try_run_ver2 (cmd_name=, argc=, argv=, cctx=0x7fffe2b0) at doveadm-cmd.c:497 #39 0x55570211 in main (argc=, argv=) at doveadm.c:395 (gdb) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Massive LMTP Problems with dovecot
Currently I'm having massive problems with LMTP delivery into dovcot. dovecot/lmtp processes are piling up, eas using considerable amounts of CPU: # ps auxwww|fgrep dove root 20537 0.0 0.0 18124 1196 ?Ss 15:18 0:00 /usr/sbin/dovecot -c /etc/dovecot/dovecot.conf dovecot 20541 0.0 0.0 9620 1084 ?S15:18 0:00 dovecot/anvil root 20542 0.0 0.0 9752 1264 ?S15:18 0:00 dovecot/log root 20544 0.0 0.0 21168 2276 ?S15:18 0:00 dovecot/config copymail 20580 72.8 0.0 39556 7036 ?R15:18 2:00 dovecot/lmtp dovecot 20582 0.0 0.0 18568 1756 ?S15:18 0:00 dovecot/auth copymail 20597 77.2 0.0 35688 5136 ?R15:18 2:06 dovecot/lmtp copymail 20598 39.3 0.0 38060 5596 ?R15:18 1:04 dovecot/lmtp copymail 20613 62.3 0.0 38036 5600 ?R15:18 1:41 dovecot/lmtp copymail 20619 56.4 0.0 37732 7448 ?R15:18 1:31 dovecot/lmtp copymail 20620 75.9 0.0 35872 5336 ?R15:18 2:03 dovecot/lmtp copymail 20627 37.8 0.0 36480 5892 ?R15:18 1:01 dovecot/lmtp copymail 20838 60.5 0.0 35640 5036 ?R15:19 0:59 dovecot/lmtp copymail 20840 66.3 0.0 35920 5296 ?R15:19 1:04 dovecot/lmtp copymail 20841 66.0 0.0 37456 6852 ?R15:19 1:04 dovecot/lmtp copymail 20842 64.5 0.0 36424 5808 ?R15:19 1:02 dovecot/lmtp copymail 20843 67.6 0.0 39612 7064 ?R15:19 1:05 dovecot/lmtp doveadm stop won't stop these, I have to use kill -9 on them. I already tried disabling fts (entirely), still things won't speed up. I can't strace: # strace -p 20841 Process 20841 attached (and that's it) # dpkg -l|grep dovecot ii dovecot-core2:2.2.25-1~auto+57amd64 secure POP3/IMAP server - core files ii dovecot-imapd 2:2.2.25-1~auto+57amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-lmtpd 2:2.2.25-1~auto+57amd64 secure POP3/IMAP server - LMTP server ii dovecot-lucene 2:2.2.25-1~auto+57amd64 secure POP3/IMAP server - Lucene support ii dovecot-sieve 2:2.2.25-1~auto+57amd64 secure POP3/IMAP server - Sieve filters support I also tried deleting the mdboxes, that also didn't change anything. Ideas? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Massive LMTP Problems with dovecot
> We'll need the `dovecot -n` output first.
Here we go:
> # 2.2.devel (933d16f): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.4.devel (63f9b42)
> # OS: Linux 3.13.0-98-generic x86_64 Ubuntu 14.04.5 LTS
> default_vsz_limit = 2 G
> lmtp_user_concurrency_limit = 1
> mail_attachment_dir = /home/copymail/attachments
> mail_location = mdbox:~/mdbox
> mail_plugins = zlib fts fts_lucene
> mdbox_rotate_size = 128 M
> 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 = username_format=%u /etc/dovecot/passwd
> driver = passwd-file
> }
> plugin {
> fts = lucene
> fts_autoindex = yes
> fts_languages = de,en
> fts_lucene = whitespace_chars=@.
> sieve = file:~/sieve;active=~/.dovecot.sieve
> zlib_save = gz
> zlib_save_level = 5
> }
> protocols = " imap lmtp"
> service imap-login {
> inet_listener imap {
> address = 127.0.0.1
> port = 143
> }
> inet_listener imaps {
> port = 993
> ssl = yes
> }
> }
> service lmtp {
> inet_listener lmtp {
> address = 141.42.1.208
> port = 1025
> }
> unix_listener /var/spool/postfix/private/dovecot-lmtp {
> group = postfix
> mode = 0660
> user = postfix
> }
> }
> ssl_ca = /etc/ssl/certs/ca-certificates.crt
> ssl_cert = ssl_cipher_list =
> EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!RC4
> ssl_key = # hidden, use -P to show it
> ssl_prefer_server_ciphers = yes
> ssl_protocols = !SSLv2 !SSLv3
> userdb {
> args = username_format=%u /etc/dovecot/passwd
> driver = passwd-file
> }
> protocol lmtp {
> mail_plugins = zlib fts fts_lucene
> }
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@charite.de | http://www.charite.de
Re: Massive LMTP Problems with dovecot
x7f3b1995e400 , v_modifiable = 0x7f3b1995e400
},
ignored_modseq_changes = 440968560, changed = 59, no_read_perm = 127}
default_save =
ret = 0
__FUNCTION__ = "mail_deliver_save"
#17 0x7f3b19759be3 in mail_deliver (ctx=ctx@entry=0x7ffc00bc2930,
storage_r=storage_r@entry=0x7ffc00bc2908) at mail-deliver.c:493
ret =
#18 0x7f3b19b8c24e in client_deliver (session=0x7f3b1a48a570,
src_mail=0x7f3b1a48b770, rcpt=0x7f3b1a44b748, client=0x7f3b1a4502d0)
at commands.c:890
set_parser =
line =
str =
mail_error = 440730320
ret =
input =
ns =
delivery_time_started = {tv_sec = 1476711940, tv_usec = 46227}
sets =
storage = 0x7f3b1a4907a0
mail_set =
username =
dctx = {pool = 0x7f3b1a48a550, set = 0x7f3b1a45df80, session =
0x7f3b1a48a570, timeout_secs = 30, session_time_msecs = 2,
delivery_time_started = {
tv_sec = 1476711940, tv_usec = 46227}, dup_ctx = 0x0, session_id =
0x7f3b1a44b4d0 "sl0sAgTWBFiZLwAAplP5LA", src_mail = 0x7f3b1a48b770,
src_envelope_sender = 0x7f3b1a44b4e8 "hartmut.xxx...@getinge.com",
dest_user = 0x7f3b1a470e40,
dest_addr = 0x7f3b1a44b788
"backup+alexander.x=charite.de@backup.invalid",
final_dest_addr = 0x7f3b1a44b788
"backup+alexander.x=charite.de@backup.invalid", dest_mailbox_name =
0x7f3b19b8f258 "INBOX",
dest_mail = 0x7f3b1a4cb700, var_expand_table = 0x0, tempfail_error =
0x0, tried_default_save = true, saved_mail = false, save_dest_mail = false,
mailbox_full = false, dsn = false}
lda_set =
error =
#19 client_deliver_next (session=0x7f3b1a48a570,
src_mail=0x7f3b1a48b770, client=0x7f3b1a4502d0) at commands.c:930
count =
#20 client_input_data_write_local (input=,
client=0x7f3b1a4502d0) at commands.c:1026
src_mail = 0x7f3b1a48b770
first_uid = 4294967295
session = 0x7f3b1a48a570
old_uid = 0
#21 client_input_data_write
(client=0x7f3b1a4502d0) at commands.c:1161
input = 0x7f3b1a4682f0
#22 client_input_data_handle (client=0x7f3b1a4502d0) at commands.c:1256
data =
size = 2366
ret =
#23 0x7f3b191a3e4c in
io_loop_call_io (io=0x7f3b1a421610) at ioloop.c:584
ioloop = 0x7f3b1a419750
t_id = 2
__FUNCTION__ = "io_loop_call_io"
#24 0x7f3b191a530a in
io_loop_handler_run_internal (ioloop=ioloop@entry=0x7f3b1a419750) at
ioloop-epoll.c:222
ctx = 0x7f3b1a41f3b0
io =
tv = {tv_sec = 299, tv_usec = 999727}
events_count =
msecs =
ret = 1
i = 0
j =
call =
__FUNCTION__ = "io_loop_handler_run_internal"
#25 0x7f3b191a3ed5 in io_loop_handler_run
(ioloop=ioloop@entry=0x7f3b1a419750) at ioloop.c:632
No locals.
#26 0x7f3b191a4078 in io_loop_run (ioloop=0x7f3b1a419750) at
ioloop.c:608
__FUNCTION__ = "io_loop_run"
#27 0x7f3b1912fbe3 in master_service_run
(service=0x7f3b1a4195f0, callback=) at
master-service.c:641
No locals.
#28 0x7f3b19b8a382 in main (argc=1, argv=0x7f3b1a419390) at
main.c:125
set_roots = {0x7f3b1995e400 ,
0x7f3b19d91580 , 0x0}
service_flags =
storage_service_flags =
c =
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@charite.de | http://www.charite.de
Re: Massive LMTP Problems with dovecot
* Ralf Hildebrandt : > I attached gdb top a long running LMTP process: > > #0 sha1_loop (ctxt=0x7f3b1a4d7fa0, input=0x7f3b1a524860, len=0) at sha1.c:216 >input_c = 0x7f3b1a524860 "\211PNG\r\n\032\n" >gaplen = >gapstart = >off = 0 >copysiz = > > #1 0x7f3b19195b29 in hash_format_loop (format=, > data=0x7f3b1a524860, size=0) at hash-format.c:150 >list = 0x7f3b1a4d7f80 It seems to loop in sha1_loop & hash_format_loop -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Massive LMTP Problems with dovecot
* Ralf Hildebrandt : > * Ralf Hildebrandt : > > I attached gdb top a long running LMTP process: > > > > #0 sha1_loop (ctxt=0x7f3b1a4d7fa0, input=0x7f3b1a524860, len=0) at > > sha1.c:216 > >input_c = 0x7f3b1a524860 "\211PNG\r\n\032\n" > >gaplen = > >gapstart = > >off = 0 > >copysiz = > > > > #1 0x7f3b19195b29 in hash_format_loop (format=, > > data=0x7f3b1a524860, size=0) at hash-format.c:150 > >list = 0x7f3b1a4d7f80 > > It seems to loop in sha1_loop & hash_format_loop The problem occurs in both 2.3 and 2.2 (I just updated to 2.3 to check). -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Massive LMTP Problems with dovecot
* Ralf Hildebrandt : > > It seems to loop in sha1_loop & hash_format_loop > > The problem occurs in both 2.3 and 2.2 (I just updated to 2.3 to check). I'm seeing the first occurence of that problem on the 10th of october! I was using (prior to the 10th) : 2.3.0~alpha0-1~auto+371 On the 10th I upgraded (16:04) to: 2.3.0~alpha0-1~auto+376 I'd think the change must have been introduced between 371 and 376 :) I then went back to, issues went away: 2.2.25-1~auto+49 and the issues reappeared with 2.2.25-1~auto+57 Does that help? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Lmtp Fatal Error
* Stephan Bosch : > Op 10/18/2016 om 10:28 PM schreef Sven Roellig: > > Hi,dovecot is create an Fatal Panik Error. > > : Fatal: master: service(lmtp): child 3369 killed > > with signal 6 (core dumps disabled) > > <1jx3DhuCBlg1DQAAWm89Cw>: Panic: file lda-sieve-plugin.c: line 447 > > (lda_sieve_execute_scripts): assertion failed: (script != NULL) > > <1jx3DhuCBlg1DQAAWm89Cw>: Error: Raw backtrace: > > /usr/lib/dovecot/libdovecot.so.0(+0x93fae) [0x7f547f6a3fae] -> > > /usr/lib/dovecot/libdovecot.so.0(+0x9409c) [0x7f547f6a409c] -> > > /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f547f63d56e] -> > > /usr/lib/dovecot/modules/lib90_sieve_plugin.so(+0x3ae8) [0x7f547d765ae8] -> > > /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x49) [0x7f547fc709a9] -> > > dovecot/lmtp(+0x7201) [0x7f54800a1201] -> > > /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x5f) [0x7f547f6b88bf] -> > > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x10a) > > [0x7f547f6b9d8a] -> > > /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7f547f6b8965] > > -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x30) [0x7f547f6b8b00] -> > > /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f547f643ac3] > > -> dovecot/lmtp(main+0x1c9) [0x7f548009f2c9] -> > > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f547f286b45] -> > > dovecot/lmtp(+0x53ae) [0x7f548009f3ae] > > > > Normal Mails are not deliverd but filterd mails are deliverd. > > System is Debian 8.6 Dovecot Core is 2%3a2.3.0-alpha0-1-auto+385 AMD64 > > Problem is known and fixed. New builds are currently blocked by an > unrelated build failure, which will be resolved soon. Ah, I was wondering about that. I tried rebuilding from source using your src packages and got an fatal error during make check :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Massive LMTP Problems with dovecot
* Timo Sirainen : > On 17 Oct 2016, at 17:31, Ralf Hildebrandt > wrote: > > > > * Ralf Hildebrandt : > > > >>> It seems to loop in sha1_loop & hash_format_loop > >> > >> The problem occurs in both 2.3 and 2.2 (I just updated to 2.3 to check). > > > > I'm seeing the first occurence of that problem on the 10th of october! > > > > I was using (prior to the 10th) : 2.3.0~alpha0-1~auto+371 > > On the 10th I upgraded (16:04) to: 2.3.0~alpha0-1~auto+376 > > > > I'd think the change must have been introduced between 371 and 376 :) > > > > I then went back to, issues went away: 2.2.25-1~auto+49 > > and the issues reappeared with 2.2.25-1~auto+57 > > https://github.com/dovecot/core/commit/9b5fa7fdd9b9f1f61eaddda48036df200fc5e56e > should fix this. Yes, fixed. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: User unknown in local recipient table
* Kalle Erlacher : > Hallo Liste, hallo Ralf, > > danke schon mal. Ja die Whitespaces sind beim Rauslöschen entstanden. > > Ich verstand das so, dass das nun durch die address_verify_map erledigt > würde. Muss ich dann entsprechend einfach auf die verweisen? Nein. > Ich versuchte gerade die > address_verify_map = btree:$data_directory/verify_cache > auf > local_recipient_maps = btree:$data_directory/verify_cache > verweisen zu lassen. Leider ohne Erfolg. Bisher ist verify_cache nämlich > leider noch unbefüllt. Entsprechend bekomme ich folgende Fehler: neee > Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: > btree:/var/lib/postfix/verify_cache is unavailable. open database > /var/lib/postfix/verify_cache.db: No such file or directory > Dec 1 16:16:29 test-mail postfix/smtpd[5550]: warning: > btree:/var/lib/postfix/verify_cache lookup error for "juergen @domain.org" > Dec 1 16:16:29 test-mail postfix/smtpd[5550]: NOQUEUE: reject: RCPT from > localhost[127.0.0.1]: 451 4.3.0 : Temporary lookup > failure; from= to= proto=ESMTP > helo= > > Auch ein plumpes touch auf /var/lib/postfix/verify_cache.db bringt danach den > selben Fehler. Das ist der falsche Ansatz! Die Domain ist eine relay_domain und du musst mit den relay_recipient_maps arbeiten ODER er muss recipient_verification gegen den LMTP des Dovecot machen. Ich weiss jetzt nicht was im Buch dazu steht -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: User unknown in local recipient table
* Sami Ketola : > Hi, > > Can you please keep this mailing list in english? Sorry, somebody crossposted this from a german language list :/ -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
Hi! I upgraded the 2.2 packages today (from 2:2.2.28-1~auto+5 to 2:2.2.28-1~auto+8) I now I'm getting an error: Mar 20 13:25:58 mproxy dovecot: auth: Error: imapc(email.charite.de:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) I checked, and alas, I had ssl_client_ca_dir = ssl_client_ca_file = So I set: ssl_client_ca_file = http://www.charite.de
Re: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Ralf Hildebrandt : > Hi! > > I upgraded the 2.2 packages today (from 2:2.2.28-1~auto+5 to > 2:2.2.28-1~auto+8) I now I'm getting an error: I was able to determine the last working version: 2:2.2.28-1~auto+6 and the first "broken" version: 2:2.2.28-1~auto+7 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Ralf Hildebrandt : > * Ralf Hildebrandt : > > Hi! > > > > I upgraded the 2.2 packages today (from 2:2.2.28-1~auto+5 to > > 2:2.2.28-1~auto+8) I now I'm getting an error: > > I was able to determine the last working version: 2:2.2.28-1~auto+6 > and the first "broken" version: 2:2.2.28-1~auto+7 2:2.2.28-1~auto+7 CHANGES file (http://xi.dovecot.fi/debian/pool/jessie-auto/dovecot-2.2/dovecot_2.2.28-1~auto+7_amd64.changes) says: New revision (a39b5b2852f2) in dovecot Git repository ... - lib-ssl-iostream: Ensure verify_remote_cert is true - lib-ssl-iostream: Fix ambiguity with SSL settings ... I think one of these two could be the culprit -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Aki Tuomi : > > > On 20.03.2017 14:30, Ralf Hildebrandt wrote: > > ssl_client_ca_file = > Leave the < out. It is misleading, I know, but it does say file. =) Makes no difference: # doveconf |fgrep ssl_client_ca ssl_client_ca_dir = ssl_client_ca_file = /etc/ssl/certs/ca-certificates.crt and with auto8 I still get: Mar 20 15:38:20 mproxy dovecot: auth: Error: imapc(exchange-imap.charite.de:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings) Mar 20 15:38:20 mproxy dovecot: auth: Error: imapc(exchange-imap.charite.de:993): No SSL context Mar 20 15:38:20 mproxy dovecot: auth: Error: imap(hildeb,141.42.206.36,): Disconnected from server Mar 20 15:38:20 mproxy dovecot: imap-login: Warning: Auth connection closed with 1 pending requests (max 0 secs, pid=52992, EOF) Mar 20 15:38:20 mproxy dovecot: auth: Fatal: master: service(auth): child 52990 killed with signal 11 (core dumped) going back to auto6 and everything is peachy again. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Aki Tuomi :
> Could you send us the gdb bt full backtrace for the core file?
Currently I can't get it to create coredumps
doveconf -n:
# 2.2.devel (3f97702): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.devel (023f391)
# OS: Linux 4.4.0-65-generic x86_64 Ubuntu 16.04.2 LTS
auth_mechanisms = plain login
default_vsz_limit = 1 G
imapc_host = exchange-imap.charite.de
imapc_port = 993
imapc_ssl = imaps
imapc_ssl_verify = no
listen = *,::
mail_gid = imapproxy
mail_home = /home/imapproxy/%u
mail_location = imapc:~/imapc
mail_plugins = mail_log notify
mail_uid = imapproxy
passdb {
args = host=exchange-imap.charite.de port=993 ssl=imaps
default_fields = userdb_imapc_user=%u userdb_imapc_password=%w
userdb_imapc_host=exchange-imap.charite.de userdb_imapc_ssl=imaps
userdb_imapc_port=993
driver = imap
}
plugin {
sieve = file:~/sieve;active=~/.dovecot.sieve
}
protocols = imap
service auth {
inet_listener {
address = 127.0.0.1
port = 12345
}
}
ssl = required
ssl_ca = http://www.charite.de
Re: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Ralf Hildebrandt :
> * Aki Tuomi :
>
> > Could you send us the gdb bt full backtrace for the core file?
>
> Currently I can't get it to create coredumps
Got a coredump and backtrace:
=
Mar 20 16:10:17 mproxy dovecot: master: Dovecot v2.2.devel (a39b5b2) starting
up for imap
Mar 20 16:10:26 mproxy dovecot: auth: Error:
imapc(exchange-imap.charite.de:993): Couldn't initialize SSL context: Can't
verify remote server certs without trusted CAs (ssl_client_ca_* settings)
Mar 20 16:10:26 mproxy dovecot: auth: Error:
imapc(exchange-imap.charite.de:993): No SSL context
Mar 20 16:10:26 mproxy dovecot: auth: Error:
imap(hildeb,141.42.206.36,): Disconnected from server
Mar 20 16:10:26 mproxy dovecot: imap-login: Warning: Auth connection closed
with 1 pending requests (max 0 secs, pid=1747, EOF)
Mar 20 16:10:26 mproxy dovecot: auth: Fatal: master: service(auth): child 1748
killed with signal 11 (core dumped)
and the backtrace:
# gdb -q /usr/lib/dovecot/auth 1748
Reading symbols from /usr/lib/dovecot/auth...Reading symbols from
/usr/lib/debug/.build-id/7a/66f9b5902485fd23f1f3dbab6479c1214f4ef1.debug...done.
done.
Attaching to program: /usr/lib/dovecot/auth, process 1748
ptrace: No such process.
[New LWP 1748]
Core was generated by dovecot/auth'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7f61e2af2226 in array_append_i (count=,
data=, array=) at ../../src/lib/array.h:168
168../../src/lib/array.h: No such file or directory.
(gdb) bt full
#0 0x7f61e2af2226 in array_append_i (count=,
data=, array=) at ../../src/lib/array.h:168
No locals.
#1 imapc_connection_abort_commands_array
(cmd_array=cmd_array@entry=0x557d24fbcea0,
dest_array=dest_array@entry=0x7ffef84bf690, only_box=only_box@entry=0x0,
keep_retriable=keep_retriable@entry=false)
at imapc-connection.c:289
cmd = 0x41
i = 0
#2 0x7f61e2af251a in imapc_connection_abort_commands (conn=0x557d24fbcdc0,
only_box=0x0, keep_retriable=) at imapc-connection.c:303
cmdp =
cmd =
tmp_array = {arr = {buffer = 0x557d24f82960, element_size = 8}, v =
0x557d24f82960, v_modifiable = 0x557d24f82960}
reply = {state = IMAPC_COMMAND_STATE_DISCONNECTED, resp_text_key = 0x0,
resp_text_value = 0x0, text_full = 0x7f61e2af6316 "Disconnected from server",
text_without_resp = 0x7f61e2af6316 "Disconnected from server"}
#3 0x7f61e39e6a92 in io_loop_call_io (io=0x557d24f9bcd0) at ioloop.c:599
ioloop = 0x557d24f8a810
t_id = 2
__FUNCTION__ = "io_loop_call_io"
#4 0x7f61e39e80ea in io_loop_handler_run_internal
(ioloop=ioloop@entry=0x557d24f8a810) at ioloop-epoll.c:223
ctx = 0x557d24f92310
io =
tv = {tv_sec = 29, tv_usec = 999177}
events_count =
msecs =
ret = 1
i = 0
j =
call =
__FUNCTION__ = "io_loop_handler_run_internal"
#5 0x7f61e39e6b2c in io_loop_handler_run
(ioloop=ioloop@entry=0x557d24f8a810) at ioloop.c:648
No locals.
#6 0x7f61e39e6cd8 in io_loop_run (ioloop=0x557d24f8a810) at ioloop.c:623
__FUNCTION__ = "io_loop_run"
#7 0x7f61e396e7d3 in master_service_run (service=0x557d24f8a6b0,
callback=) at master-service.c:641
No locals.
#8 0x557d2303f31e in main (argc=1, argv=0x557d24f8a390) at main.c:400
c =
(gdb)
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG, 80333 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
Re: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Ralf Hildebrandt : > Mar 20 16:10:17 mproxy dovecot: master: Dovecot v2.2.devel (a39b5b2) starting > up for imap > Mar 20 16:10:26 mproxy dovecot: auth: Error: > imapc(exchange-imap.charite.de:993): Couldn't initialize SSL context: Can't > verify remote server certs without trusted CAs (ssl_client_ca_* settings) > Mar 20 16:10:26 mproxy dovecot: auth: Error: > imapc(exchange-imap.charite.de:993): No SSL context > Mar 20 16:10:26 mproxy dovecot: auth: Error: > imap(hildeb,141.42.206.36,): Disconnected from server > Mar 20 16:10:26 mproxy dovecot: imap-login: Warning: Auth connection closed > with 1 pending requests (max 0 secs, pid=1747, EOF) > Mar 20 16:10:26 mproxy dovecot: auth: Fatal: master: service(auth): child > 1748 killed with signal 11 (core dumped) Still there in auto11 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Aki Tuomi : > > Still there in auto11 > > > Yes, we have not gotten round fixing it. Did you remove < from the path? Of course :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: help
* Pallissard, Matthew : > > What can i do to resolve this issue in dovecot v2.1.17 in Production > > environment? Kindly help > > Why don't you upgrade production and modify the settings as you did in test? I was wondering about this as well. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
How to query for headers by regexp?
I need to find all mails with a certain numerical range in my quarantine: X-Spam-Status: No, score=4.5 tagged_above=2 required=4.6 ... Assume I'd be looking for 4.5-6.0; so I tried searching for doveadm import -u restore mdbox:/home/quarantine/mdbox "" \ mailbox INBOX header X-Spam-Status "No, score=4.5" doveadm import -u restore mdbox:/home/quarantine/mdbox "" \ mailbox INBOX header X-Spam-Status "No, score=4.6" etc. Which would only return 2 Mails, with score score=4.5 What am I doing wrong here? Can I search using regular expressions? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: Dovecot 2.3 ?
* Reuben Farrelly : > Hi, > > Is anyone here running dovecot-2.3 from hg? I'm using the daily builds on a low traffic machine. It's proxying traffic to a Exchange IMAP server. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: Dovecot 2.3 ?
* Aki Tuomi : > > I'm using the daily builds on a low traffic machine. It's proxying > > traffic to a Exchange IMAP server. > > > > Please do not run it from hg, as we no longer provide hg repository. What I meant to say: I use the daily builds. Fair enough :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Bug with 2.2.29-1~auto+25 back to haunt me
After upgrading from 2.2.28-1~auto+45 to 2.2.29-1~auto+25 I'm gettings
this:
May 31 16:44:31 mproxy dovecot: auth: Fatal: passdb imap: Cannot verify
certificate without ssl_ca_dir or ssl_ca_file setting
May 31 16:44:31 mproxy dovecot: master: Error: service(auth): command startup
failed, throttling for 8 secs
May 31 16:44:31 mproxy dovecot: imap-login: Disconnected: Auth process broken
(disconnected before auth was ready, waited 2 secs): user=<>,
rip=141.42.206.36, lip=141.42.206.11, TLS, session=
# doveconf -n
# 2.2.devel (215fd61): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.devel (403042e)
# OS: Linux 4.4.0-71-generic x86_64 Ubuntu 16.04.2 LTS
auth_mechanisms = plain login
default_vsz_limit = 1 G
imapc_host = exchange-imap.charite.de
imapc_port = 993
imapc_ssl = imaps
imapc_ssl_verify = no
listen = *,::
mail_gid = imapproxy
mail_home = /home/imapproxy/%u
mail_location = imapc:~/imapc
mail_plugins = mail_log notify
mail_uid = imapproxy
passdb {
args = host=exchange-imap.charite.de port=993 ssl=imaps
default_fields = userdb_imapc_user=%u userdb_imapc_password=%w
userdb_imapc_host=exchange-imap.charite.de userdb_imapc_ssl=imaps
userdb_imapc_port=993
driver = imap
}
plugin {
sieve = file:~/sieve;active=~/.dovecot.sieve
}
protocols = imap
service auth {
inet_listener {
address = 127.0.0.1
port = 12345
}
}
ssl = required
ssl_ca = https://www.charite.de
Re: Bug with 2.2.29-1~auto+25 back to haunt me
* Ralf Hildebrandt : > So I added > ssl_ca_file = /etc/ssl/certs/ca-certificates.crt > > But alas: > May 31 16:50:24 mproxy dovecot: config: Warning: Obsolete setting in > /etc/dovecot/conf.d/10-ssl.conf:36: ssl_ca_file has been replaced by ssl_ca = > > Gnarf! As you can see I do HAVE ssl_ca in my doveconf -n output! > > ssl_ca = > So what gives? It seems to be similar to: https://www.dovecot.org/pipermail/dovecot/2017-March/107488.html "Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)" -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: Bug with 2.2.29-1~auto+25 back to haunt me
* Aki Tuomi : > > > So I added > > > ssl_ca_file = /etc/ssl/certs/ca-certificates.crt > > > > > > But alas: > > > May 31 16:50:24 mproxy dovecot: config: Warning: Obsolete setting in > > > /etc/dovecot/conf.d/10-ssl.conf:36: ssl_ca_file has been replaced by > > > ssl_ca = > > > > > Gnarf! As you can see I do HAVE ssl_ca in my doveconf -n output! > > > > > > ssl_ca = > > > > > So what gives? > > > > It seems to be similar to: > > https://www.dovecot.org/pipermail/dovecot/2017-March/107488.html > > > > "Can't verify remote server certs without trusted CAs (ssl_client_ca_* > > settings)" > > > > -- > > Ralf Hildebrandt > > Geschäftsbereich IT | Abteilung Netzwerk > > Charité - Universitätsmedizin Berlin > > Campus Benjamin Franklin > > Hindenburgdamm 30 | D-12203 Berlin > > Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 > > ralf.hildebra...@charite.de | https://www.charite.de > > > > Hi. > > passdb imap was changed to verify remote SSL cert by default (yeah, it > kinda didn't do this before). It requires a ssl_ca_file or ssl_ca_dir > setting in args. Or you can disable this behaviour with > allow_invalid_cert. I did specify "ssl_ca_file", but then dovecot said "ssl_ca_file has been replaced by ssl_ca = https://www.charite.de
Re: Bug with 2.2.29-1~auto+25 back to haunt me
* Aki Tuomi :
> I meant
>
> passdb {
> driver = imap
> args = ... ssl_ca_file=/path/to/ca
> }
That doesn't work:
passdb {
driver = imap
# Change the line below to reflect the IP address of your Exchange Server.
args = host=exchange-imap.charite.de port=993 ssl=imaps
ssl_ca=https://www.charite.de
Re: Bug with 2.2.29-1~auto+25 back to haunt me
* Ralf Hildebrandt :
> * Aki Tuomi :
>
> > I meant
> >
> > passdb {
> > driver = imap
> > args = ... ssl_ca_file=/path/to/ca
> > }
>
> That doesn't work:
>
> passdb {
> driver = imap
> # Change the line below to reflect the IP address of your Exchange Server.
> args = host=exchange-imap.charite.de port=993 ssl=imaps
> ssl_ca= ...
>
> or
> args = host=exchange-imap.charite.de port=993 ssl=imaps
> ssl_ca_file=/etc/ssl/certs/ca-certificates.crt
>
> both give me:
>
> Jun 2 17:38:19 mproxy dovecot: auth: Fatal: passdb imap: Unknown parameter:
> ssl_ca_file
>
> Jun 2 17:38:29 mproxy dovecot: auth: Fatal: passdb imap: Unknown parameter:
> ssl_ca
Working now with 2.2.30-1~auto+1:
args = host=exchange-imap.charite.de port=993 ssl=imaps
ssl_ca_file=/etc/ssl/certs/ca-certificates.crt
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@charite.de | https://www.charite.de
imapc bug (signal 6)
176625}' failed with BAD: 1321 Command Argument Error. 11 Sep 7 16:14:19 mproxy dovecot: imap(holtgrem)<2ZkfDZpYKKCsEIAI>: Error: imapc: APPEND failed: Command Argument Error. 11 Sep 7 16:14:19 mproxy dovecot: imap(holtgrem)<2ZkfDZpYKKCsEIAI>: IMAP session state is inconsistent, please relogin. in=42180017 out=220890 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=1 body_bytes=788 Sep 7 16:14:19 mproxy dovecot: imap-login: Login: user=, method=PLAIN, rip=172.16.128.8, lip=141.42.206.11, mpid=61072, TLS, session= Sep 7 16:14:19 mproxy dovecot: imap(holtgrem): imapc(exchange-imap.charite.de:993): Connected to 10.32.37.100:993 (local 141.42.206.11:58198) Sep 7 16:14:27 mproxy dovecot: imap(holtgrem): Connection closed (EXAMINE finished 8.029 secs ago) in=63 out=1372 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Sep 7 16:14:29 mproxy dovecot: imap(holtgrem): Connection closed (FETCH running for 112.511 + waiting input for 0.001 secs, 0.001 in locks, 28 B in + 127311+2054 B out, state=wait-input) in=105 out=128699 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Ubuntu packages for 22.04 LTS?
Hi! I recently updated from 20.04 -> 22.04 and wondered if packages specifically for 22.04 were available. https://doc.dovecot.org/installation_guide/dovecot_community_repositories/ubuntu_packages/ doesn't seem list any... Neiter does https://repo.dovecot.org -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
Re: [ext] Re: Ubuntu packages for 22.04 LTS?
* Aki Tuomi : > Ubuntu 22.04 support will be added for upcoming 2.4 CE release. yay! -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
doveadm: Error: Mailbox INBOX: Deleting corrupted cache: Cache file too large
Hi! Upon issuing a % doveadm import -u restore@backup.invalid mdbox:/home/storage/mdbox I'm getting a: doveadm(restore@backup.invalid): Error: Mailbox INBOX: Deleting corrupted cache: Cache file too largea doveadm(restore@backup.invalid): Error: Corrupted dbox file /home/restore/mdbox/storage/m.7 (around offset=41602004): msg header has bad magic value doveadm(restore@backup.invalid): Error: Corrupted dbox file /home/restore/mdbox/storage/m.8 (around offset=17193748): msg header has bad magic value message -- but the process keeps running! Should I worry? dovecot packages: 2.3.20-3+ubuntu20.04 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | https://www.charite.de
full text index "per user"?
Is there any way of disabling the creation of a full text index on a per user basis? -- [*] 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
LMTP error: Too many concurrent deliveries for user (in reply to end of DATA command)
I updated dovecot today and all over a sudden I'm getting: Mar 6 14:40:46 mail postfix/lmtp[3150]: 3kz95y3nX3zCtTS: to=, relay=127.0.0.1[private/dovecot-lmtp], delay=88, delays=87/0.94/0.01/0.01, dsn=4.3.0, status=deferred (host 127.0.0.1[private/dovecot-lmtp] said: 451 4.3.0 Too many concurrent deliveries for user (in reply to end of DATA command)) Why is that? Which setting must I tweak? -- [*] 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
Re: LMTP error: Too many concurrent deliveries for user (in reply to end of DATA command)
* Ralf Hildebrandt : > > I updated dovecot today and all over a sudden I'm getting: Old: dovecot-lmtpd:amd64 2:2.2.15-1~auto+136 New: dovecot-lmtpd:amd64 2:2.2.15-1~auto+148 >From Stephan Bosch's repos. -- [*] 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
Re: LMTP error: Too many concurrent deliveries for user (in reply to end of DATA command)
* Ralf Hildebrandt : > * Ralf Hildebrandt : > > > > I updated dovecot today and all over a sudden I'm getting: > > Old: > dovecot-lmtpd:amd64 2:2.2.15-1~auto+136 > > New: > dovecot-lmtpd:amd64 2:2.2.15-1~auto+148 > > From Stephan Bosch's repos. Found the issue: # doveconf |grep concurr lmtp_user_concurrency_limit = 0 -> not working # doveconf |grep concurr lmtp_user_concurrency_limit = 1 -> working again! I guess 0 should disable the limit. It doesn't (anymore). -- [*] 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
Re: LMTP error: Too many concurrent deliveries for user (in reply to end of DATA command)
* Reindl Harald : > lmtp_destination_concurrency_limit on postfix side It's not a postfix issue. postfix is merely reporting what Dovecot said. -- [*] 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
Re: v2.2.16 release candidate released
* Timo Sirainen : > + LMTP server: Added lmtp_user_concurrency_limit setting to limit how > many LMTP deliveries can be done concurrently for a single user. That's broken! 0 doesn't remove the limit :( -- [*] 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
Re: full text index "per user"?
* Ralf Hildebrandt : > Is there any way of disabling the creation of a full text index on a > per user basis? userdb lookup which returns "fts="! -- [*] 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
Crash in dovecot/auth with backtrace
I'm seeing this odd crash with
"USER\t531\t*@liquid-scan.de\tservice=quota-status"
Which looks like something is being tested against our quota-status --
but I fail to see why an NON LOCAL address is being tested
GNU gdb (GDB) 7.4.1-debian
Copyright (C) 2012 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 "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/local/dovecot-2.2/libexec/dovecot/auth...done.
[New LWP 2289]
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
Core was generated by `dovecot/auth'.
Program terminated with signal 6, Aborted.
#0 0xb7724424 in __kernel_vsyscall ()
#0 0xb7724424 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb74a0661 in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
resultvar =
pid = -1218617356
selftid = 2289
#2 0xb74a3a92 in *__GI_abort () at abort.c:92
act = {__sigaction_handler = {sa_handler = 0xbfd1c924,
sa_sigaction = 0xbfd1c924}, sa_mask = {__val = {3077760610,
3218196756, 3076712520, 3218196744, 3077843556, 0, 3074764848,
1, 0, 1, 3077716256, 145215752, 1097, 3077184659, 3, 145244200,
1, 128, 0, 3218196816, 3218196744, 3218196756, 3218196764,
3077716256, 0, 3077194863, 145215720, 3076749582, 3077199789,
3077686824, 1097, 3077686824}}, sa_flags = 0,
sa_restorer = 0xb76a5c2f }
sigs = {__val = {32, 0 }}
#3 0xb76a624e in default_fatal_finish (type=,
status=status@entry=0) at failures.c:202
backtrace = 0x8a7c8d8
"/usr/local/dovecot-2.2/lib/dovecot/libdovecot.so.0(+0x7825e) [0xb76a625e] ->
/usr/local/dovecot-2.2/lib/dovecot/libdovecot.so.0(+0x782e1) [0xb76a62e1] ->
/usr/local/dovecot-2.2/lib/dovecot/libdovecot."...
#4 0xb76a62e1 in i_internal_fatal_handler (ctx=0xbfd1c9f0,
format=0x807a0c4 "file %s: line %d (%s): assertion failed: (%s)",
args=0xbfd1ca14 "\257j\a\b\371\004") at failures.c:671
status = 0
#5 0xb76a6e5f in i_panic (
format=format@entry=0x807a0c4 "file %s: line %d (%s): assertion failed:
(%s)") at failures.c:276
ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0,
timestamp_usecs = 0}
args = 0xbfd1ca14 "\257j\a\b\371\004"
#6 0x0805873a in auth_request_set_login_username (request=0x8a945d8,
username=0x8a7c548 "", error_r=0xbfd1cad4) at auth-request.c:1273
master_passdb =
__FUNCTION__ = "auth_request_set_login_username"
#7 0x08054c44 in master_input_auth_request (conn=conn@entry=0x8aa18b8,
args=args@entry=0x8a941c1 "531\t*@liquid-scan.de\tservice=quota-status",
cmd=cmd@entry=0x8076925 "USER", request_r=request_r@entry=0xbfd1cad0,
error_r=error_r@entry=0xbfd1cad4) at auth-master-connection.c:209
auth_request = 0x8a945d8
list = 0x8a7c53c
name =
arg =
username = 0x8a7c504 "*@liquid-scan.de"
id = 531
#8 0x0805539c in master_input_user (
args=0x8a941c1 "531\t*@liquid-scan.de\tservice=quota-status",
conn=0x8aa18b8) at auth-master-connection.c:306
auth_request = 0x8a92e70
error = 0x8ab8e81 "31298"
ret =
#9 auth_master_input_line (
line=0x8a941bc "USER\t531\t*@liquid-scan.de\tservice=quota-status",
conn=0x8aa18b8) at auth-master-connection.c:615
No locals.
#10 master_input (conn=0x8aa18b8) at auth-master-connection.c:679
_data_stack_cur_id = 3
line =
ret = 40
#11 0xb76baf8b in io_loop_call_io (io=0x8a92ba8) at ioloop.c:501
ioloop = 0x8a844e8
t_id = 2
__FUNCTION__ = "io_loop_call_io"
#12 0xb76bc272 in io_loop_handler_run_internal (ioloop=ioloop@entry=0x8a844e8)
at ioloop-epoll.c:220
ctx = 0x8a8b500
events = 0x8f1
event = 0x8a8b558
list = 0x8a92be0
io =
tv = {tv_sec = 0, tv_usec = 999856}
events_count =
msecs =
ret = 3
i =
j =
call =
__FUNCTION__ = "io_loop_handler_run_internal"
#13 0xb76bb01c in io_loop_handler_run (ioloop=ioloop@entry=0x8a844e8)
at ioloop.c:548
No locals.
#14 0xb76bb0a8 in io_loop_run (ioloop=0x8a844e8) at ioloop.c:525
__FUNCTION__ = "io_loop_run"
#15 0xb76527ae in master_service_run (service=0x8a84418,
callback=0x8063df0 ) at
Re: Crash in dovecot/auth with backtrace
* Timo Sirainen : > On 23 Apr 2015, at 17:34, Ralf Hildebrandt > wrote: > > > > I'm seeing this odd crash with > > "USER\t531\t*@liquid-scan.de\tservice=quota-status" > > Which looks like something is being tested against our quota-status -- > > but I fail to see why an NON LOCAL address is being tested > > Oh, that's not very good. Fixed: > http://hg.dovecot.org/dovecot-2.2/rev/65f825a8cd0b Thanks a lot :) -- [*] 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
fts_languages setting is missing - disabling?
I don't find "fts_languages" in the documentation... What should I add there anbd where? doveadm(restore): Error: fts-dovecot: fts_languages setting is missing - disabling -- [*] 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
Re: fts_languages setting is missing - disabling?
* Ralf Hildebrandt : > I don't find "fts_languages" in the documentation... What should I add > there anbd where? fts_languages = de,en seems to do the trick. But I wonder if there's something like "all" and what exactly this setting does. -- [*] 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
Re: fts_languages setting is missing - disabling?
* Timo Sirainen : > On 24 Apr 2015, at 13:54, Ralf Hildebrandt wrote: > > > > * Ralf Hildebrandt : > >> I don't find "fts_languages" in the documentation... What should I add > >> there anbd where? > > > > fts_languages = de,en > > seems to do the trick. But I wonder if there's something like "all" > > and what exactly this setting does. > > That code shouldn't have run at all (unless you had configured fts_lucene = > use_libfts). It's still work in progress. I'll get rid of the errors. oops :) -- [*] 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
Quota question
http://wiki2.dovecot.org/Quota/Configuration
says:
concat('*:bytes=', quota_limit_bytes) AS quota_rule
and
concat('*:bytes=', quota_limit_bytes) AS userdb_quota_rule
but a generic quota_rule on the same page says:
plugin {
quota = maildir:User quota
quota_rule = *:storage=1G
quota_rule2 = Trash:storage=+100M
}
Are "bytes=" and "storage=" equivalent?
http://wiki2.dovecot.org/UserDatabase/ExtraFields
also shows "storage=":
user_query = SELECT home, uid, gid, \
'*:storage=100M' as quota_rule, mail_plugins, \
'gz' as `plugin/zlib_save` FROM users WHERE userid = '%u'
--
[*] 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
Re: Quota question
* Ralf Hildebrandt : > Are "bytes=" and "storage=" equivalent? Found it on http://wiki2.dovecot.org/Quota/Configuration, sorry: storage: Quota limit in kilobytes, 0 means unlimited. bytes: Quota limit in bytes, 0 means unlimited. -- [*] 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
Re: Error while executing dovecot
* Sachin Kulkarni1 : > Hello All, > > I am trying to execute dovecot by below command > > /opt/app/dovecot/latest/sbin/dovecot -c > /opt/app/dovecot/latest/etc/dovecot/dovecot.conf > > I am getting below error > > doveconf: Fatal: Error in configuration file > /opt/app/dovecot/latest/etc/dovecot/dovecot.conf: default_login_user doesn't > exist: dovenull > > please guide me to resolve this. Create the user dovenull! Dovecot uses two system users for internal purposes now by default: "dovenull" and "dovecot". You need to create the "dovenull" user or change default_login_user setting. "dovenull" user is used by completely untrustworthy processes, while "dovecot" user is used for slightly more trusted processes. If you want to be using something else than "dovecot" as the other user, you need to change default_internal_user setting. Just like with "dovecot" user, "dovenull" doesn't need a password, home directory or anything else (but it's good to give it its own private "dovenull" group). -- [*] 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
doveadm import - strange warning
I'm using the doveadm import command to extract mails from my backup:
% doveadm import -u restore@backup.invalid mdbox:/home/copymail/mdbox "" \
mailbox INBOX header Delivered-To backup+$SEARCHPATTERN@backup.invalid
This works like a charm, I'm getting all the mails, and I can access
the newly generated mailbox.
But when executing the command I'm getting an annoying warning:
doveadm(restore@backup.invalid): Error: chdir(/root/) failed: Permission denied
(euid=1001(copymail) egid=1001(copymail) missing +x perm: /root, dir owned by
0:0 mode=0700)
doveadm(restore@backup.invalid): Error: chdir(/root) failed: Permission denied
I'm using a file based authentication:
# cat passwd
restore@backup.invalid:{SHA}+/...the.hash...:1001:1001:(gecos):/home/restore::
So why is "restore@backup.invalid" being associated with /root?
I'm using 2:2.2.18-1~auto+91, but the warning has been around for ages
:)
--
[*] 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
Re: doveadm import - strange warning
Anybody seen this before? Seems easy to reproduce... * Ralf Hildebrandt : > I'm using the doveadm import command to extract mails from my backup: > > % doveadm import -u restore@backup.invalid mdbox:/home/copymail/mdbox "" \ >mailbox INBOX header Delivered-To backup+$SEARCHPATTERN@backup.invalid > > This works like a charm, I'm getting all the mails, and I can access > the newly generated mailbox. > > But when executing the command I'm getting an annoying warning: > > doveadm(restore@backup.invalid): Error: chdir(/root/) failed: Permission > denied (euid=1001(copymail) egid=1001(copymail) missing +x perm: /root, dir > owned by 0:0 mode=0700) > doveadm(restore@backup.invalid): Error: chdir(/root) failed: Permission denied -- [*] 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
Re: doveadm import - strange warning
* Daniel Tröder : > Just guessing… > > The signature of the command is: > doveadm [-Dv] import [-S socket_path] [-s] -u user source_location > dest_parent search_query > > You supply "" as dest_parent which I guess could mean ".", and that may > be "/root" when run as root. Try "INBOX" or "restore_folder" and see if > the error vanishes. With "INBOX", nothing changes on the output (although the script doesn't restore properly anymore) With ".", I get: doveadm(restore@backup.invalid): Error: chdir(/root/) failed: Permission denied (euid=1001(theid) egid=1001(theid) missing +x perm: /root, dir owned by 0:0 mode=0700) doveadm(restore@backup.invalid): Error: chdir(/root) failed: Permission denied doveadm(restore@backup.invalid): Error: Couldn't create mailbox ./INBOX: Invalid mailbox name: Contains '.' part I still think this is an obscure bug :) -- [*] 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
Re: doveadm import - strange warning
> I think there are two independent errors. > First: > >doveadm(restore@backup.invalid): Error: chdir(/root/) failed: Permission > >denied (euid=1001(theid) egid=1001(theid) missing +x perm: /root, dir owned > >by 0:0 mode=0700) > >doveadm(restore@backup.invalid): Error: chdir(/root) failed: Permission > >denied > Here I think doveadm import tries to do a chdir to the users HOME Directory > and does it wrong. It uses the bash environment variable $HOME instead of > the users home information as shown by doveadm user. > > Why do I think so, because if I manually export the bash environment HOME to > the Home Directory of the user I want to import to I don't receive this > error anymore. > > Example: > export HOME="/mailhome/userA" > doveadm import -u userA maildir:/backup/userA Backup ALL; > -> No Error > export HOME="/root" > doveadm import -u userA maildir:/backup/userA Backup ALL; > -> Error as seen above. Yes, this was my actual problem. So doveadm is really doing something wrong. > Second: That was not my original problem :) > If the first error is a bug or a feature I don't know, but doveadm import > works correct with or without this error shown. At least for the things I > have done. Yes, it works. But personally I think it shouldn't emit errors if everything works as expected... I'll just work around it. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Which mail does a certain attachment belong to?
I'm seeing this:
./17/3c/173c81da2aab91f225f8eb5e8fcc87119be4eff0-b38d990442316a54a90c8f4649af:
SecuriteInfo.com.TR.Kryptik.180736.5155.16748.22498.UNOFFICIAL FOUND
./17/3c/173c81da2aab91f225f8eb5e8fcc87119be4eff0-bc70851b03216a54483f8f4649af:
SecuriteInfo.com.TR.Kryptik.180736.5155.16748.22498.UNOFFICIAL FOUND
When scanning the "attachments" directory of my mdbox. How can I find
out WHICH EMAIL these two attachments belong to?
mail_location = mdbox:~/mdbox
mail_plugins = zlib fts fts_lucene
mdbox_rotate_size = 128M
mdbox_rotate_interval = 0
mail_attachment_dir = /some/path/attachments
mail_attachment_min_size = 128k
mail_attachment_fs = sis posix
mail_attachment_hash = %{sha1}
--
[*] 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
Re: doveadm import - strange warning
* Ralf Hildebrandt : > I'm using 2:2.2.18-1~auto+91, but the warning has been around for ages > :) Gone at least since 2:2.2.21-1~auto+18 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
crash after out of memory?
We're encountering a crash when proxying to an Exchange server:
Mar 30 10:40:47 mproxy dovecot: imap-login: Login: user=,
method=PLAIN, rip=10.39.76.71, lip=141.42.206.11, mpid=18556, TLS,
session=
Mar 30 10:40:49 mproxy dovecot: imap(xxxbxxx): Fatal: block_alloc(134217728):
Out of memory
Mar 30 10:40:49 mproxy dovecot: imap(xxxbxxx): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(+0x85afe) [0x7fb0b829eafe] ->
/usr/lib/dovecot/libdovecot.so.0(+0x85bec) [0x7fb0b829ebec] ->
/usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7fb0b824373a] ->
/usr/lib/dovecot/libdovecot.so.0(+0x9f284) [0x7fb0b82b8284] ->
/usr/lib/dovecot/libdovecot.so.0(+0x9f2c3) [0x7fb0b82b82c3] ->
/usr/lib/dovecot/libdovecot.so.0(+0x9f357) [0x7fb0b82b8357] ->
/usr/lib/dovecot/libdovecot.so.0(+0x81a6d) [0x7fb0b829aa6d] ->
/usr/lib/dovecot/libdovecot.so.0(buffer_write+0x6c) [0x7fb0b829acdc] ->
/usr/lib/dovecot/libdovecot.so.0(+0x6ea54) [0x7fb0b8287a54] ->
/usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fb0b82a8ee3] ->
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_copy_from_parent+0x118)
[0x7fb0b82a96a8] ->
/usr/lib/dovecot/libdovecot-storage.so.0(+0xc00ba) [0x7fb0b85e10ba] ->
/usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fb0b82a8ee3] ->
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fb0b82a991d] ->
/usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x72)
[0x7fb0b828d2a2] ->
/usr/lib/dovecot/libdovecot.so.0(+0x6e919) [0x7fb0b8287919] ->
/usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fb0b82a8ee3] ->
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fb0b82a991d] ->
/usr/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x72)
[0x7fb0b828d2a2] ->
/usr/lib/dovecot/libdovecot.so.0(+0x6e919) [0x7fb0b8287919] ->
/usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fb0b82a8ee3] ->
/usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fb0b82a991d] ->
/usr/lib/dovecot/libdovecot.so.0(message_get_header_size+0x74) [0x7fb0b8290e34]
->
/usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x317)
[0x7fb0b8609f37] ->
dovecot/imap [xxxbxxx 10.39.76.71 UID fetch](+0x1f1de) [0x7fb0b8a9a1de] ->
dovecot/imap [xxxbxxx 10.39.76.71 UID fetch](+0x1d60c) [0x7fb0b8a9860c] ->
dovecot/imap [xxxbxxx 10.39.76.71 UID fetch](imap_fetch_more+0x3a)
[0x7fb0b8a9970a] ->
dovecot/imap [xxxbxxx 10.39.76.71 UID fetch](cmd_fetch+0x354) [0x7fb0b8a8b954]
Mar 30 10:40:49 mproxy dovecot: imap(xxxbxxx): Fatal: master: service(imap):
child 18556 returned error 83 (Out of memory (service
imap { vsz_limit=256 MB }, you may need to increase it) - set CORE_OUTOFMEM=1
environment to get core dump)
It happens for this user ONLY. Using the automatic bosch build:
2.2.21-1~auto+152
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@charite.de | http://www.charite.de
Re: crash after out of memory?
* Timo Sirainen : >The user has an email that contains a huge >100MB header line? I hope not :) I "solved" the problem by setting the vsz_limit_default to 1G >I think there's something in here that could use fixing. It shouldn't be >that easy to make Dovecot use up that much memory. Some istream buffer >size limit is missing somewhere I think.. The attached patch might help? Is it in the official tree? I'm using the autobuilds nowadays. Could tell you tomorrow! -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Recent update causes segfault in proxy mode
I'm using the auto builds (2:2.2.24-1~auto+3) for Ubuntu/Debian. The recent upgrade to 2.2.24 cause the follwoing error to appear: I can log in to a mailbox via dovecot I can delete emails Upon expunge, dovecot crashes: Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142514, msgid=, size=10086 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142519, msgid=, size=1232 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142520, msgid=, size=1232 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142521, msgid=, size=1240 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142522, msgid=, size=1239 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142523, msgid=, size=1239 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142524, msgid=, size=6662 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142525, msgid=, size=5342 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142527, msgid=, size=9718 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142528, msgid=, size=3019 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142529, msgid=, size=7625 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142530, msgid=, size=31900 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142531, msgid=, size=4827 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142532, msgid=, size=4096 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142533, msgid=, size=7100 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142534, msgid=, size=4422 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142535, msgid=, size=10856 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142536, msgid=, size=13305 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142574, msgid=, size=3113 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142575, msgid=, size=4155 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142576, msgid=, size=5114 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142577, msgid=, size=3266 Apr 29 11:05:30 mproxy dovecot: imap(hildeb): Fatal: master: service(imap): child 12393 killed with signal 11 (core dumped) Unfortunately, I'm not getting a backtrace :( -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Recent update causes segfault in proxy mode
* Ralf Hildebrandt : > Apr 29 11:05:30 mproxy dovecot: imap(hildeb): Fatal: master: service(imap): > child 12393 killed with signal 11 (core dumped) > > Unfortunately, I'm not getting a backtrace :( Got a core dump, but I need to find out where to get the debug symbols for the packages on http://xi.dovecot.fi/debian/ ... -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Recent update causes segfault in proxy mode
* Ralf Hildebrandt :
> Unfortunately, I'm not getting a backtrace :(
got it:
# gdb /usr/lib/dovecot/imap 16784
GNU gdb (Ubuntu 7.11-0ubuntu1) 7.11
Copyright (C) 2016 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".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/lib/dovecot/imap...Reading symbols from
/usr/lib/debug/.build-id/5a/15dc6951744d026af424747e7b72a4fb550c6b.debug...done.
done.
Attaching to program: /usr/lib/dovecot/imap, process 16784
ptrace: No such process.
[New LWP 16784]
Core was generated by `dovecot/imap'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 buffer_delete (_buf=0x0, pos=0, size=0) at buffer.c:213
213 buffer.c: No such file or directory.
(gdb) bt full
#0 buffer_delete (_buf=0x0, pos=0, size=0) at buffer.c:213
buf = 0x0
end_size =
#1 0x7febcad5407e in array_delete_i (count=1, idx=1992,
array=0x7febcd4b7b68) at ../../../../src/lib/array.h:200
No locals.
#2 imapc_untagged_expunge (reply=, mbox=0x7febcd4b77f0) at
imapc-mailbox.c:473
msgmap = 0x7febcd4b9320
lseq = 3444200800
uid = 142578
rseq = 1993
#3 0x7febcad56632 in imapc_storage_client_untagged_cb
(reply=0x7ffe117d5500, context=0x7febcd483080) at imapc-storage.c:204
mcb__foreach_end = 0x7febcd4b7f48
client = 0x7febcd483080
mbox = 0x7febcd4b77f0
cb =
mcb = 0x7febcd4b7f28
#4 0x7febcad5c90a in imapc_connection_input_untagged
(conn=conn@entry=0x7febcd4a5560) at imapc-connection.c:1144
imap_args = 0x7febcd4a9b08
data =
size = 140650738261000
name = 0x7febcd4a9c08 "EXPUNGE"
value =
parser = 0x7febcd4a57b0
reply = {name = 0x7febcd4a9c08 "EXPUNGE", num = 1993, args =
0x7febcd4a9b08, file_args = 0x7febcd4a7470, file_args_count = 0, resp_text_key
= 0x0, resp_text_value = 0x0,
untagged_box_context = 0x7febcd4b77f0}
ret =
#5 0x7febcad5e7d9 in imapc_connection_input_one (conn=0x7febcd4a5560) at
imapc-connection.c:1398
tag = 0x7febcd4a9bf8 "*"
ret = -1
#6 imapc_connection_input_pending (conn=0x7febcd4a5560) at
imapc-connection.c:1766
_data_stack_cur_id = 6
ret = 1
conn = 0x7febcd4a5560
#7 0x7febcad5e82a in imapc_connection_input (conn=0x7febcd4a5560) at
imapc-connection.c:1438
errstr =
str =
ret =
#8 0x7febcaa5905c in io_loop_call_io (io=0x7febcd4bd3d0) at ioloop.c:564
ioloop = 0x7febcd4babc0
t_id = 5
__FUNCTION__ = "io_loop_call_io"
#9 0x7febcaa5a4c1 in io_loop_handler_run_internal
(ioloop=ioloop@entry=0x7febcd4babc0) at ioloop-epoll.c:220
ctx = 0x7febcd4bac90
io =
tv = {tv_sec = 299, tv_usec = 999605}
events_count =
msecs =
ret = 1
i = 0
j =
call =
__FUNCTION__ = "io_loop_handler_run_internal"
#10 0x7febcaa590e5 in io_loop_handler_run
(ioloop=ioloop@entry=0x7febcd4babc0) at ioloop.c:612
No locals.
#11 0x7febcaa59288 in io_loop_run (ioloop=0x7febcd4babc0) at ioloop.c:588
__FUNCTION__ = "io_loop_run"
#12 0x7febcad59b7a in imapc_client_run_pre (client=0x7febcd483250,
client=0x7febcd483250) at imapc-client.c:173
connp = 0x7febcd4833e8
prev_ioloop = 0x7febcd467740
#13 imapc_client_run (client=0x7febcd483250) at imapc-client.c:192
No locals.
#14 0x7febcad575e0 in imapc_mailbox_run_nofetch
(mbox=mbox@entry=0x7febcd4b77f0) at imapc-storage.c:143
No locals.
#15 0x7febcad57612 in imapc_mailbox_run (mbox=mbox@entry=0x7febcd4b77f0) at
imapc-storage.c:137
No locals.
#16 0x7febcad59178 in imapc_sync_index (ctx=0x7febcd4bd010) at
imapc-sync.c:405
mbox = 0x7febcd4b77f0
sync_rec = {uid1 = 142578, uid2 = 142578, type =
MAIL_INDEX_SYNC_TYPE_EXPUNGE, add_flags = 254 '\376', remove_flags = 127
'\177', keyword_idx = 0,
guid_128 = "^kK\r2U\277\357\225`\030\220\257\330\a\t"}
seq1 = 1993
seq2 = 1993
#17 imapc_sync_begin (force=, ctx_r=,
mbox=0x7febcd4b77f0) at imapc-sync.c:481
ctx =
sync_flags =
ret =
#18 imapc_sync (mbox=0x7febcd4b77f0) at imapc-sync.c:537
Backtrace:dovecot/imap
(client=client@entry=0x7f572c11be50,
box=, imap_flags=IMAP_SYNC_FLAG_SAFE,
flags=MAILBOX_SYNC_FLAG_EXPUNGE) at imap-sync.c:229
__FUNCTION__ = "imap_sync_init"
#22 0x7f572a17ef97 in cmd_sync_client (sync_cmd=0x7f572c127a90)
at imap-sync.c:737
ctx =
flags =
client = 0x7f572c11be50
imap_flags =
no_newmail =
#23 cmd_sync_delayed_real (client=0x7f572c11be50) at imap-sync.c:856
cmd =
first_expunge =
first_nonexpunge =
#24 cmd_sync_delayed (client=client@entry=0x7f572c11be50) at imap-sync.c:864
_data_stack_cur_id = 3
#25 0x7f572a1726d8 in client_handle_input (client=0x7f572c11be50)
at imap-client.c:1088
remove_io =
handled_commands =
client = 0x7f572c11be50
#26 0x7f572a172b65 in client_input (client=0x7f572c11be50)
at imap-client.c:1119
cmd = 0x27284
output = 0x7f572c11d080
bytes = 153
__FUNCTION__ = "client_input"
#27 0x7f572977a05c in io_loop_call_io (io=0x7f572c1198c0) at ioloop.c:564
ioloop = 0x7f572c0db740
t_id = 2
__FUNCTION__ = "io_loop_call_io"
#28 0x7f572977b4c1 in io_loop_handler_run_internal (
ioloop=ioloop@entry=0x7f572c0db740) at ioloop-epoll.c:220
ctx = 0x7f572c0dd250
io =
tv = {tv_sec = 1739, tv_usec = 992115}
events_count =
msecs =
ret = 1
i = 0
j =
call =
__FUNCTION__ = "io_loop_handler_run_internal"
#29 0x7f572977a0e5 in io_loop_handler_run (
ioloop=ioloop@entry=0x7f572c0db740) at ioloop.c:612
No locals.
#30 0x7f572977a288 in io_loop_run (ioloop=0x7f572c0db740) at ioloop.c:588
__FUNCTION__ = "io_loop_run"
#31 0x7f572970fe63 in master_service_run (service=0x7f572c0db5e0,
callback=) at master-service.c:640
No locals.
#32 0x7f572a165b32 in main (argc=1, argv=0x7f572c0db390) at main.c:460
set_roots = {0x7f572a38f700 ,
0x7f5729f2e400 , 0x0}
login_set = {auth_socket_path = 0x7f572c0d3048 "\001",
postlogin_socket_path = 0x0, postlogin_timeout_secs = 60,
callback = 0x7f572a17f9d0 ,
failure_callback = 0x7f572a17f2e0 ,
request_auth_token = 1}
service_flags =
storage_service_flags =
username = 0x0
auth_socket_path = 0x7f572a18834e "auth-master"
c =
- End forwarded message -
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@charite.de | http://www.charite.de
Re: Backtrace:dovecot/imap
* Timo Sirainen : > Oh, imapc expunges were broken when imapc_features didn't have > "modseq". > https://github.com/dovecot/core/commit/de8fc9d21460bf0369d671e9ba9361592379a7c5 Fixed, thanks! -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
segfault in imap "Warning: Timeout leak: 0x7fd584e8e050 (line 399)"
Corresponding log entry:
Apr 29 17:14:07 mproxy dovecot: imap(v**d): copy from INBOX: box=Trash,
uid=512, msgid=, size=error
Apr 29 17:14:07 mproxy dovecot: imap(v**d): expunge: box=INBOX, uid=3322,
msgid=, size=22485
Apr 29 17:14:19 mproxy dovecot: imap(v**d): copy from INBOX: box=Trash,
uid=513, msgid=, size=error
Apr 29 17:14:19 mproxy dovecot: imap(v**d): expunge: box=INBOX, uid=3288,
msgid=, size=60236
Apr 29 17:14:19 mproxy dovecot: imap(v**d): Warning: Timeout leak:
0x7fd584e8e050 (line 399)
Apr 29 17:14:19 mproxy dovecot: imap(v**d): Connection closed (IDLE running
for 0.043 + waiting input for 6654.979 secs, 2 B in + 10+10 B out,
state=wait-input) in=7582 out=5928297
Apr 29 17:14:19 mproxy dovecot: imap(v**d): Fatal: master: service(imap):
child 30554 killed with signal 11 (core dumped)
Backtrace:
Reading symbols from /usr/lib/dovecot/imap...Reading symbols from
/usr/lib/debug/.build-id/5a/15dc6951744d026af424747e7b72a4fb550c6b.debug...done.
done.
[New LWP 30554]
Core was generated by `dovecot/imap'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x7fd584b8daa7 in timeout_remove (_timeout=0x7fd5875b5048)
at ioloop.c:307
#0 0x7fd584b8daa7 in timeout_remove (_timeout=0x7fd5875b5048)
at ioloop.c:307
timeout = 0x7fd5875b8720
ioloop = 0x0
#1 0x7fd584e8df0b in imapc_client_mailbox_close (
_box=_box@entry=0x7fd5875b3b38) at imapc-client.c:362
box = 0x7fd5875b5030
connp =
#2 0x7fd584e8c3af in imapc_mailbox_close (box=0x7fd5875b3850)
at imapc-storage.c:651
mbox = 0x7fd5875b3850
#3 0x7fd584e411aa in mailbox_close (box=0x7fd5875b5048)
at mail-storage.c:1242
No locals.
#4 0x7fd584e41233 in mailbox_free (_box=_box@entry=0x7fd5875a3f00)
at mail-storage.c:1262
box = 0x7fd5875b3850
#5 0x7fd585584f74 in client_default_destroy (client=0x7fd5875a3e60,
reason=) at imap-client.c:367
cmd = 0x0
#6 0x7fd584b8e06c in io_loop_call_io (io=0x7fd5875a18d0) at ioloop.c:564
ioloop = 0x7fd587563740
t_id = 2
__FUNCTION__ = "io_loop_call_io"
#7 0x7fd584b8f4d1 in io_loop_handler_run_internal (
ioloop=ioloop@entry=0x7fd587563740) at ioloop-epoll.c:220
ctx = 0x7fd587565250
io =
tv = {tv_sec = 4, tv_usec = 738842}
events_count =
msecs =
ret = 1
i = 0
j =
call =
__FUNCTION__ = "io_loop_handler_run_internal"
#8 0x7fd584b8e0f5 in io_loop_handler_run (
ioloop=ioloop@entry=0x7fd587563740) at ioloop.c:612
No locals.
#9 0x7fd584b8e298 in io_loop_run (ioloop=0x7fd587563740) at ioloop.c:588
__FUNCTION__ = "io_loop_run"
#10 0x7fd584b23e63 in master_service_run (service=0x7fd5875635e0,
callback=) at master-service.c:640
No locals.
#11 0x7fd585577b32 in main (argc=1, argv=0x7fd587563390) at main.c:460
set_roots = {0x7fd5857a1700 ,
0x7fd585340400 , 0x0}
login_set = {auth_socket_path = 0x7fd58755b048 "\001",
postlogin_socket_path = 0x0, postlogin_timeout_secs = 60,
callback = 0x7fd5855919d0 ,
failure_callback = 0x7fd5855912e0 ,
request_auth_token = 1}
service_flags =
storage_service_flags =
username = 0x0
auth_socket_path = 0x7fd58559a34e "auth-master"
c =
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Charité - Universitätsmedizin Berlin
Campus Benjamin Franklin
Hindenburgdamm 30 | D-12203 Berlin
Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962
ralf.hildebra...@charite.de | http://www.charite.de
Re: Automatic packages for Dovecot v2.3
* Stephan Bosch : > Hi, > > The Xi repository for v2.3 is now public. The information is updated here: > > http://wiki2.dovecot.org/PrebuiltBinaries#Automatically_Built_Packages Just made an upgrade from 2.2 to 2.3 and it's working ok (imapc, proxy setup) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: Disabling passdb pam in local.conf
* Edgar Pettijohn : > > Only /etc/dovecot/local.conf should be changed. > > > So you want the standard files to remain unchanged from default settings and > override them with your settings in local.conf? Exactly (he said that in his initial mail). -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: Disabling passdb pam in local.conf
* Patrick Ben Koetter :
> Greetings,
>
> I'm trying to create a configuration that leaves every config file deployed by
> an install process or paket management software untouched. The goal is to put
> every configuration required into /etc/dovecot/local.conf.
>
> I've come quite far, but I fail to disable pam as passdb service in
> local.conf. What I get if I run doveconf -n is this section:
>
> passdb {
> driver = pam
> }
It seems that there is no way of saying something like:
remove passdb
Adding new passdb entries is no problem, but removing existing ones is
hard.
What is the actual problem? System accounts shouldn't be able to
log-in? System accounts shouldn't be valid mailboxes?
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Schleißheimer Straße 26/MG, 80333 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
"anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup@backup.invalid"
I updated to 2.3.0 today, and now I'm getting these entries in my log: Jul 7 14:26:20 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17687 + ident lmtp/backup@backup.invalid Jul 7 14:26:20 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup@backup.invalid Jul 7 14:26:21 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17654 + ident lmtp/backup@backup.invalid Jul 7 14:26:22 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup@backup.invalid Jul 7 14:26:22 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17687 + ident lmtp/backup@backup.invalid Jul 7 14:26:23 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup@backup.invalid lmtp on the other seems to be working ok -- I'm not seeing any mails queueing up... Jul 7 14:28:01 mail-cbf dovecot: lmtp(17659): Connect from local Jul 7 14:28:01 mail-cbf dovecot: anvil: Error: connect limit: disconnection for unknown pid 17659 + ident lmtp/backup@backup.invalid Jul 7 14:28:01 mail-cbf dovecot: lmtp(17659): Disconnect from local: Successful quit -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
2.3.0~alpha0-1~auto+197: Crash when openening a message via IMAP
>From the log: Jul 11 13:12:42 mproxy dovecot: imap-login: Login: user=, method=PLAIN, rip=141.42.206.36, lip=141.42.206.11, mpid=27254, TLS, session= Jul 11 13:12:44 mproxy dovecot: imap(hildeb): Panic: file imap-client.c: line 854 (client_check_command_hangs): assertion failed: ((io_loop_find_fd_conditions(current_ioloop, client->fd_out) & IO_WRITE) != 0) Jul 11 13:12:44 mproxy dovecot: imap(hildeb): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x8e09e) [0x7efd1d3a309e] -> /usr/lib/dovecot/libdovecot.so.0(+0x8e18c) [0x7efd1d3a318c] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7efd1d34169e] -> dovecot/imap [hildeb 141.42.206.36 UID FETCH - 8192 bytes waiting corked](+0x1ad42) [0x55649b35cd42] -> dovecot/imap [hildeb 141.42.206.36 UID FETCH - 8192 bytes waiting corked](client_output+0x118) [0x55649b35ce68] -> /usr/lib/dovecot/libdovecot.so.0(+0xaf370) [0x7efd1d3c4370] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x4c) [0x7efd1d3b715c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x101) [0x7efd1d3b85b1] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x25) [0x7efd1d3b71e5] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x30) [0x7efd1d3b7380] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7efd1d347c13] -> dovecot/imap [hildeb 141.42.206.36 UID FETCH - 8192 bytes waiting corked](main+0x322) [0x55649b34faf2] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7efd1cf6c830] -> dovecot/imap [hildeb 141.42.206.36 UID FETCH - 8192 bytes waiting corked](+0xdc6f) [0x55649b34fc6f] Jul 11 13:12:44 mproxy dovecot: imap(hildeb): Fatal: master: service(imap): child 27254 killed with signal 6 (core dumped) # 2.3.0.alpha0 (3aae884) [XI:2:2.3.0~alpha0-1~auto+197]: /etc/dovecot/dovecot.conf -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: 2.3.0~alpha0-1~auto+197: Crash when openening a message via IMAP
* Aki Tuomi :
> Did you forget to include doveconf -n?
# 2.3.0.alpha0 (e84ffeb) [XI:2:2.3.0~alpha0-1~auto+200]:
/etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.0.alpha0 (66b7c14)
# OS: Linux 4.4.0-24-generic x86_64 Ubuntu 16.04 LTS
auth_mechanisms = plain login
default_vsz_limit = 1 G
imapc_host = email.charite.de
imapc_port = 993
imapc_ssl = imaps
imapc_ssl_verify = no
listen = *,::
mail_gid = imapproxy
mail_home = /home/imapproxy/%u
mail_location = imapc:~/imapc
mail_plugins = mail_log notify
mail_uid = imapproxy
passdb {
args = host=email.charite.de port=993 ssl=imaps
default_fields = userdb_imapc_user=%u userdb_imapc_password=%w
userdb_imapc_host=email.charite.de userdb_imapc_ssl=imaps
userdb_imapc_port=993
driver = imap
}
plugin {
sieve = file:~/sieve;active=~/.dovecot.sieve
}
protocols = imap
service auth {
inet_listener {
address = 127.0.0.1
port = 12345
}
}
ssl = required
ssl_ca = http://www.charite.de
Re: 2.3.0~alpha0-1~auto+197: Crash when openening a message via IMAP
* Timo Sirainen :
> On 11 Jul 2016, at 14:15, Ralf Hildebrandt
> wrote:
> >
> > From the log:
> >
> > Jul 11 13:12:42 mproxy dovecot: imap-login: Login: user=,
> > method=PLAIN, rip=141.42.206.36, lip=141.42.206.11, mpid=27254, TLS,
> > session=
> > Jul 11 13:12:44 mproxy dovecot: imap(hildeb): Panic: file
> > imap-client.c: line 854 (client_check_command_hangs): assertion failed:
> > ((io_loop_find_fd_conditions(current_ioloop, client->fd_out) & IO_WRITE) !=
> > 0)
>
> Could you gdb the core and print some outputs:
>
> fr 5 (or whichever frame number has client_check_command_hangs)
> p *client
> p *client->command_queue
> p *client->command_queue->next
> p *client->command_queue->next->next
> (etc, until it fails)
> p *current_ioloop
> p *current_ioloop->io_files
> p *current_ioloop->io_files->next
> p *current_ioloop->io_files->next->next
> (etc, until it fails)
Here it goes:
Core was generated by 'dovecot/imap'.
Program terminated with signal SIGABRT, Aborted.
#0 0x7f6fa260d418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
54 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x7f6fa260d418 in __GI_raise (sig=sig@entry=6) at
../sysdeps/unix/sysv/linux/raise.c:54
#1 0x7f6fa260f01a in __GI_abort () at abort.c:89
#2 0x7f6fa2a2f226 in default_fatal_finish (type=,
status=status@entry=0) at failures.c:201
#3 0x7f6fa2a2f31c in i_internal_fatal_handler (ctx=0x7ffc8041e430,
format=, args=) at failures.c:670
#4 0x7f6fa29cd6ce in i_panic (format=format@entry=0x558b2197ce00 "file %s:
line %d (%s): assertion failed: (%s)") at failures.c:275
#5 0x558b2196bd42 in client_check_command_hangs (client=0x558b21bf7030) at
imap-client.c:854
#6 client_continue_pending_input (client=0x558b21bf7030) at imap-client.c:919
#7 0x558b2196be68 in client_output (client=0x558b21bf7030) at
imap-client.c:1233
#8 0x7f6fa2a50500 in stream_send_io (fstream=0x558b21be5bb0) at
ostream-file.c:478
#9 0x7f6fa2a432ec in io_loop_call_io (io=0x558b21bfdf00) at ioloop.c:564
#10 0x7f6fa2a44741 in io_loop_handler_run_internal
(ioloop=ioloop@entry=0x558b21ba3740) at ioloop-epoll.c:221
#11 0x7f6fa2a43375 in io_loop_handler_run
(ioloop=ioloop@entry=0x558b21ba3740) at ioloop.c:612
#12 0x7f6fa2a43510 in io_loop_run (ioloop=0x558b21ba3740) at ioloop.c:588
#13 0x7f6fa29d3c43 in master_service_run (service=0x558b21ba35e0,
callback=) at master-service.c:650
#14 0x558b2195eaf2 in main (argc=1, argv=0x558b21ba3390) at main.c:460
(gdb) fr 5
#5 0x558b2196bd42 in client_check_command_hangs (client=0x558b21bf7030) at
imap-client.c:854
854 imap-client.c: No such file or directory.
(gdb) p *client
$1 = {prev = 0x0, next = 0x0, v = {state_export = 0x558b219763a0
, state_import = 0x558b219768f0
, destroy = 0x558b2196c290
},
session_id = 0x558b21bf71d8 "qsZiv2w3uLWNKs4k", userdb_fields =
0x558b21bf7400, fd_in = 7, fd_out = 7, io = 0x558b21be5cf0, input =
0x558b21be5a60, output = 0x558b21be5c40, to_idle = 0x558b21be5d50,
to_idle_output = 0x558b21bfe020, to_delayed_input = 0x0, pool =
0x558b21bf7010, service_user = 0x558b21baa020, set = 0x558b21baa7f0,
lda_set = 0x558b21baa930, capability_string = 0x558b21bf7258,
user = 0x558b21bb8360, mailbox = 0x558b21bfa060, keywords = {names =
0x558b21bfb0f8, announce_count = 1}, sync_counter = 1, messages_count
= 1443, recent_count = 0, uidvalidity = 58,
enabled_features = (unknown: 0), last_input = 1468315092,
last_output = 1468315092, bad_counter = 0, free_parser = 0x0,
command_pool = 0x558b21bf7820, command_queue = 0x558b21bf7840,
command_queue_size = 1, sync_last_full_modseq = 12854,
highest_fetch_modseq = 0, fetch_hdr_count = 0, fetch_body_count = 1,
fetch_hdr_bytes = 0, fetch_body_bytes = 369600, deleted_count = 0,
expunged_count = 0, trashed_count = 0, search_saved_uidset = {arr =
{buffer = 0x0, element_size = 0}, v = 0x0, v_modifiable = 0x0},
search_updates = {arr = {buffer = 0x0, element_size = 0}, v = 0x0,
v_modifiable = 0x0}, notify_ctx = 0x0, notify_uidnext = 157276,
input_lock = 0x0, output_cmd_lock = 0x558b21bf7840,
mailbox_change_lock = 0x0, urlauth_ctx = 0x0, module_contexts = {arr = {
buffer = 0x558b21bf71f0, element_size = 8}, v = 0x558b21bf71f0,
v_modifiable = 0x558b21bf71f0}, sync_seen_deletes = false,
disconnected = false, destroyed = false, handling_input = false,
syncing = false, id_logged = false, mailbox_examined = false,
anvil_sent = true, tls_compression = false, input_skip_line = false,
modseqs_sent_since_sync = false, notify_immediate_expunges = false,
notify_count_changes = true, notify_flag_changes = true,
imap_metadata_enabled = false, nonpermanent_modseqs = false,
state_import_bad_idle_done = false, state_import_idle_continue
[Dovecot] BUG: Unknown internal error
With a recent checkout of dovecot-2 I'm getting a few "BUG: Unknown internal error" messages. The log for one such incident: Jul 21 10:21:38 postamt dovecot: imap(ikurzweg): copy from INBOX: box=INBOX.Trash, uid=6385, msgid=<4DA3E334.05.02956@ILONA-PC>, size=90980 Jul 21 10:21:38 postamt dovecot: imap(ikurzweg): copy from INBOX: box=INBOX.Trash, uid=6386, msgid=<4DA3ECDD.08.02956@ILONA-PC>, size=103191 Jul 21 10:21:38 postamt dovecot: imap(ikurzweg): delete: box=INBOX, uid=5426, msgid=<4DA3E334.05.02956@ILONA-PC>, size=90980 Jul 21 10:21:38 postamt dovecot: imap(ikurzweg): delete: box=INBOX, uid=5427, msgid=<4DA3ECDD.08.02956@ILONA-PC>, size=103191 Jul 21 10:21:38 postamt dovecot: imap(ikurzweg): expunge: box=INBOX, uid=5426, msgid=<4DA3E334.05.02956@ILONA-PC>, size=90980 Jul 21 10:21:38 postamt dovecot: imap(ikurzweg): expunge: box=INBOX, uid=5427, msgid=<4DA3ECDD.08.02956@ILONA-PC>, size=103191 Jul 21 10:21:53 postamt dovecot: imap(ikurzweg): Error: Corrupted index cache file /home/i/k/ikurzweg/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 4433 Jul 21 10:21:53 postamt dovecot: imap(ikurzweg): Disconnected: BUG: Unknown internal error bytes=5689/114139 What's up here? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] BUG: Unknown internal error
* Leander S. : > Index is corrupt. Dovecot seems only to see 5689 of actually indexed 114139 > bytes as far as I understand the log. > > Hardware fine / HDD is fine? No 'cold' shutdowns? FS out of Space? FS/User > Quota over limit? Nothing like that :) > Dovecot usually uses internal "self-healing" feature to fixe broken > indexes ... For testing purposes you could try to entierly delete Users > root mailfolder and recreate it or let it recreate by Dovecot and see > what happens ... obviously it would make sense to back up old root > mailfoder in case there is important data ... -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] BUG: Unknown internal error
* Robert Schetterer : > as i understood , its a recent checkout version from latest dove hg > i looked if i found equal errors in mine stable version, > so the problem might be anywhere in the patches since the last stable ? Yes; I just upgraded to see if it's gone :) -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] BUG: Unknown internal error
* Ralf Hildebrandt : > * Robert Schetterer : > > > as i understood , its a recent checkout version from latest dove hg > > i looked if i found equal errors in mine stable version, > > so the problem might be anywhere in the patches since the last stable ? > > Yes; I just upgraded to see if it's gone :) Let me rephrase this: * the error was there before installing the latest checkout * the error was still there AFTER installing the latest checkout It's not really critical, I was just wondering if the index is broken OR the maildir files itself... -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
[Dovecot] libtoolize warnings when building
When building the HG checkout, I'm getting: ... libtoolize: Consider adding AC_CONFIG_MACRO_DIR([m4])' to configure.in and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding -I m4' to ACLOCAL_AMFLAGS in Makefile.am.a Making distclean in doc My build command looks like this: hg pull hg update ./autogen.sh make -j distclean ./configure --prefix=/usr/local --enable-maintainer-mode make -j 4 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] libtoolize warnings when building
* Timo Sirainen : > On 31.7.2011, at 21.14, Ralf Hildebrandt wrote: > > > When building the HG checkout, I'm getting: > > > > ... > > libtoolize: Consider adding AC_CONFIG_MACRO_DIR([m4])' to configure.in and > > libtoolize: rerunning libtoolize, to keep the correct libtool macros > > in-tree. > > libtoolize: Consider adding -I m4' to ACLOCAL_AMFLAGS in Makefile.am.a > > Yeah, I've considered it, but I'm not entirely sure if I should do as it > says. So far I haven't. Just asking. Usually I'm doing something wrong in these kinds of cases. Thanks for the info. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
[Dovecot] Message flags
How do I set message flags in sieve rules in such a way that e.g. Thunderbird is displaying the mail as "important"? Is there a list of hwo flags are interpreted by different IMAP clients? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] 64.31.19.48 attempt to break into my computer
* Rick Baartman : > From my secure log: > > Sep 19 01:16:44 lin12 dovecot-auth: pam_unix(dovecot:auth): check pass; user > unknown > Sep 19 01:16:44 lin12 dovecot-auth: pam_unix(dovecot:auth): authentication > failure; logname= uid=0 euid=0 tty=dovecot ruser= rhost=:::64.31.19.48 > Sep 19 01:16:44 lin12 dovecot-auth: pam_succeed_if(dovecot:auth): error > retrieving information about user aaron > Sep 19 01:16:45 lin12 dovecot-auth: pam_unix(dovecot:auth): check pass; user > unknown > Sep 19 01:16:45 lin12 dovecot-auth: pam_unix(dovecot:auth): authentication > failure; logname= uid=0 euid=0 tty=dovecot ruser= rhost=:::64.31.19.48 > Sep 19 01:16:45 lin12 dovecot-auth: pam_succeed_if(dovecot:auth): error > retrieving information about user abby > > etc. Literally, 30,000 user names attempted. And? Any success? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
