Re: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)

2017-03-23 Thread Ralf Hildebrandt 
* Ralf Hildebrandt <r...@sys4.de>:

> 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)

2017-03-20 Thread Ralf Hildebrandt 
* Ralf Hildebrandt <ralf.hildebra...@charite.de>:
> 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)

2017-03-20 Thread Ralf Hildebrandt 
* Ralf Hildebrandt <ralf.hildebra...@charite.de>:
> * Ralf Hildebrandt <ralf.hildebra...@charite.de>:
> > 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

Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)

2017-03-20 Thread 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:

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)

2017-03-20 Thread Ralf Hildebrandt 
* Aki Tuomi <aki.tu...@dovecot.fi>:
> 
> 
> 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)

2017-03-20 Thread Ralf Hildebrandt 
* Ralf Hildebrandt <dovecot@dovecot.org>:
> * Aki Tuomi <aki.tu...@dovecot.fi>:
> 
> > 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)

2017-03-20 Thread 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

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: help

2017-04-20 Thread Ralf Hildebrandt 
* Pallissard, Matthew <dove...@pallissard.net>:
> > 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?

2017-04-23 Thread Ralf Hildebrandt 
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 ?

2017-04-24 Thread Ralf Hildebrandt 
* Reuben Farrelly <reuben-dove...@reub.net>:
> 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 ?

2017-04-24 Thread Ralf Hildebrandt 
* Aki Tuomi <aki.tu...@dovecot.fi>:

> > 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

Re: Bug with 2.2.29-1~auto+25 back to haunt me

2017-05-31 Thread Ralf Hildebrandt 
* Ralf Hildebrandt <ralf.hildebra...@charite.de>:

> 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

2017-06-02 Thread 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=https://www.charite.de

Re: Bug with 2.2.29-1~auto+25 back to haunt me

2017-06-01 Thread Ralf Hildebrandt 
* Aki Tuomi <aki.tu...@dovecot.fi>:

> > > 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 = <file" -- so I used that and it wouldn't work
either!

-- 
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

2017-06-06 Thread Ralf Hildebrandt 
* Ralf Hildebrandt <ralf.hildebra...@charite.de>:
> * Aki Tuomi <aki.tu...@dovecot.fi>:
> 
> > 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

Bug with 2.2.29-1~auto+25 back to haunt me

2017-05-31 Thread Ralf Hildebrandt 
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

imapc bug (signal 6)

2017-09-07 Thread Ralf Hildebrandt 
 imap(holtgrem)<2ZkfDZpYKKCsEIAI>: Error: 
imapc(exchange-imap.charite.de:993): Command '1321 APPEND "INBOX" (\Seen) 
"29-Aug-2017 11:36:49 +0200" {42176625}' 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

Panic: file imap-client.c: line 1204 (client_handle_input): assertion failed: (o_stream_is_corked(client->output))

2017-12-14 Thread Ralf Hildebrandt 
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: lmtp panic with many recipients

2018-05-09 Thread Ralf Hildebrandt 
* Stephan Bosch <step...@rename-it.nl>:
> 
> 
> 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

2018-05-09 Thread Ralf Hildebrandt 
* Olaf Hopp <olaf.h...@kit.edu>:

> Seems to be. There is a
> =?iso-8859-1?Q?s=2Ev=F6gele=40X=2Ede?= <s.vög...@x.de>
> 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?

2018-05-30 Thread Ralf Hildebrandt 
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

Re: [ext] v2.2.34 released

2018-03-01 Thread Ralf Hildebrandt 
* Timo Sirainen <t...@iki.fi>:
> 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

2018-03-01 Thread Ralf Hildebrandt 
* Aki Tuomi <aki.tu...@dovecot.fi>:

> > 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

Re: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))

2018-03-03 Thread Ralf Hildebrandt 
> 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))

2018-03-05 Thread Ralf Hildebrandt 
> 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))

2018-03-05 Thread Ralf Hildebrandt 
* A.L.E.C <a...@alec.pl>:
> On 03/02/2018 03:32 PM, Ralf Hildebrandt wrote:
> > The address causing the error is:
> > 
> > From: =?utf-8?Q?Dorit_M=C3=BCller?= <d.mül...@jomec.de>
> > 
> > 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))

2018-03-05 Thread 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?

-- 
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))

2018-03-05 Thread Ralf Hildebrandt 
* Ralf Hildebrandt <ralf.hildebra...@charite.de>:
> > 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))

2018-03-05 Thread Ralf Hildebrandt 
x0
input_local = 0x56239bde26b8
inputs = {0x0, 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: [ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))

2018-03-05 Thread Ralf Hildebrandt 
* John Fawcett <j...@voipsupport.it>:

> 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

Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))

2018-03-02 Thread Ralf Hildebrandt 
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?= <d.mül...@jomec.de>

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

QUERY string clarification

2018-12-09 Thread Ralf Hildebrandt 
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

Panic: file mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)

2020-01-10 Thread Ralf Hildebrandt 
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

Re: [ext] Crash during "doveadm import"

2020-07-27 Thread Ralf Hildebrandt 
* 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

Crash during "doveadm import"

2020-07-27 Thread Ralf Hildebrandt 
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"

2020-07-27 Thread Ralf Hildebrandt 
* 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

Re: [ext] Re: doveadm crash on import

2020-12-01 Thread Ralf Hildebrandt 
* 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 crash on import

2020-12-01 Thread Ralf Hildebrandt 
% 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: What is the state of SMTPUTF8 support?

2021-03-14 Thread Ralf Hildebrandt 
* 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

Re: [ext] Re: What is the state of SMTPUTF8 support?

2021-03-14 Thread 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

-- 
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

2021-03-08 Thread Ralf Hildebrandt 
* 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

doveadm import uninterruptable?

2021-02-16 Thread Ralf Hildebrandt 
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

Ubuntu packages for 22.04 LTS?

2023-02-06 Thread Ralf Hildebrandt 
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?

2023-02-06 Thread Ralf Hildebrandt 
* 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

2023-02-09 Thread Ralf Hildebrandt 
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

Re: [ext] Dovecot Wiki: Please disable edit on double click

2019-03-20 Thread Ralf Hildebrandt via dovecot 
* Michael Goth via dovecot :

> could you maybe disable the 'edit on doubleclick' feature on
> wiki2.dovecot.org?
> 
> Everytime I try to select a word by double clicking on it, I end up in
> editing mode. It's just a minor thing, but maybe I'm not the only one who's
> annoyed by this ;)

Amen to that. I never bothered to ask, but it annoys the shit out of me!

-- 
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: expunge not removing attachments?

2019-02-12 Thread Ralf Hildebrandt via dovecot 
* @lbutlr via dovecot :
 
> I had problems with this a few years ago, and resorted to simply using find 
> to remove the files from the file system 
> 
> /usr/bin/find /usr/local/virtual/*/.Junk*/{cur,new} -type f -mtime +7 -name 
> “*=*" -delete 2> /dev/null
> /usr/bin/find /usr/local/virtual/*/.Trash/{cur,new} -type f -mtime +7 -name 
> “*=*" -delete 2> /dev/null

I'm not using Maildir. I suspect the SIS is broken somehow.

-- 
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] expunge not removing attachments?

2019-02-12 Thread Ralf Hildebrandt via dovecot 
* Ralf Hildebrandt :
> 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.

I retried this today (2:2.3.4.1-1~bionic):

# find attachments/ -type f -ctime +5 | wc -l
193121
# find attachments/ -type f | wc -l
301885

193121 of 301885 (64%) are older (ctime) than 5 days, although I just purged 
everything older than 4 days?


# /home/copymail# find attachments/ -type f -mtime +5 | wc -l
201629
# /home/copymail# find attachments/ -type f | wc -l
301900

201629 of 301900 (66.7%) files are modified (mtime) more than 5 days ago, 
although I just purged everything older than 4 days?

-- 
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)

2019-05-24 Thread Ralf Hildebrandt via dovecot 
ffdc50) at message-header-parser.c:85
#20 0x77357dd2 in message_parse_header (input=, 
hdr_size=hdr_size@entry=0x0,flags=flags@entry=MESSAGE_HEADER_PARSER_FLAG_CLEAN_ONELINE,
 
callback=callback@entry=0x776f2310 , 
context=context@entry=0x7fffdcc0) at message-header-parser.c:392
#21 0x776f2dae in search_arg_match_text (ctx=0x5583dd20, 
args=0x55809690) at index-search.c:760
#22 search_match_once (ctx=0x5583dd20) at index-search.c:1400
#23 0x776f40ac in search_match_next (ctx=0x5583dd20) at 
index-search.c:1507
#24 search_more_with_mail (mail=, ctx=0x5583dd20) at 
index-search.c:1624
#25 search_more_with_prefetching (mail_r=, ctx=) 
at index-search.c:1706
#26 search_more (ctx=ctx@entry=0x5583dd20, 
mail_r=mail_r@entry=0x7fffddf0) at index-search.c:1780
#27 0x776f48bd in 
index_storage_search_next_nonblock(_ctx=0x5583dd20, mail_r=0x7fffdec0, 
tryagain_r=0x7fffde57) at index-search.c:1808
#28 0x776752e8 in mailbox_search_next_nonblock (ctx=0x5583dd20, 
mail_r=0x7fffdec0, tryagain_r=) at mail-storage.c:2141
#29 0x7767534d in mailbox_search_next (ctx=0x5583dd20, 
mail_r=mail_r@entry=0x7fffdec0) at mail-storage.c:2126
#30 0x55586682 in doveadm_mail_iter_next (iter=, 
mail_r=mail_r@entry=0x7fffdec0) at doveadm-mail-iter.c:160
#31 0x55585443 in cmd_import_box (search_args=, 
info=0x55832118, dest_user=, ctx=0x55807d78) at 
doveadm-mail-import.c:142
#32 cmd_import_run (_ctx=0x55807d78, user=0x5581c688) at 
doveadm-mail-import.c:202 
#33 0x5557fdb1 in doveadm_mail_next_user (ctx=ctx@entry=0x55807d78, 
error_r=error_r@entry=0x7fffe0a0) at doveadm-mail.c:462
#34 0x55580a0b in doveadm_mail_single_user 
(ctx=ctx@entry=0x55807d78, error_r=error_r@entry=0x7fffe0a0) at 
doveadm-mail.c:492
#35 0x55580af9 in doveadm_mail_cmd_exec (ctx=ctx@entry=0x55807d78, 
wildcard_user=wildcard_user@entry=0x0) at doveadm-mail.c:653
#36 0x555819ce in doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=) at doveadm-mail.c:1144
#37 0x55592b7e in doveadm_cmd_run_ver2 (argc=12, argv=0x557f5ae8, 
cctx=cctx@entry=0x7fffe290) at doveadm-cmd.c:574
#38 0x55592bd7 in doveadm_cmd_try_run_ver2 (cmd_name=, 
argc=, argv=, cctx=0x7fffe290) at 
doveadm-cmd.c:496
#39 0x5556fec1 in main (argc=, argv=) at 
doveadm.c:391

-- 
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 mail-index-util.c: line 10 (mail_index_uint32_to_offset): assertion failed: (offset < 0x40000000)

2019-05-24 Thread Ralf Hildebrandt via dovecot 
* Aki Tuomi via dovecot :
> Known issue when folder cache is too big. Try rm -rf dovecot.index.cache
> for the folder.

-rw--- 1 mail mail 1746959712 May 24 14:37 dovecot.index.cache

yes, it is quite big :) 1.746.959.712

-- 
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

2.3.7 slower than 2.3.6?

2019-07-15 Thread Ralf Hildebrandt via dovecot 
We're using dovecot (via LMTP) as a backup for all incoming mail.

I upgraded from 2.3.6 to 2.3.7 on the 12th:
2019-07-12 14:35:44 upgrade dovecot-imapd:amd64 2:2.3.6-2~bionic 
2:2.3.7-8~bionic

and it seems that 2.3.7 is slower than 2.3.6 -- mail to the backup
IMAP box is suddenly taking quite some time to get delivered and is piling up
in the queue.

doveconf -n:


default_vsz_limit = 2 G
lmtp_user_concurrency_limit = 1
mail_attachment_dir = /home/copymail/attachments
mail_fsync = never
mail_location = mdbox:~/mdbox
mail_plugins = zlib fts
mdbox_rotate_size = 128 M
... namespaces ...
plugin {
  fts_autoindex = yes
  fts_languages = de,en
  zlib_save = gz
  zlib_save_level = 5
}
protocols = " imap lmtp"
userdb {
  args = username_format=%u /etc/dovecot/passwd
  driver = passwd-file
}
protocol lmtp {
  mail_plugins = zlib fts
}
  

-- 
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] 2.3.7 slower than 2.3.6?

2019-07-17 Thread Ralf Hildebrandt via dovecot 
> > All of the data is an /dev/sda1
> 
> What filesystem is this?

ext4
 
> I did a bunch of testing, and after initially thinking I saw an
> increase it was just due to bad testing because the new TCP_NODELAY
> changes allowed imaptest to do more work. So I can't see that there is
> any disk IO difference.
> 
> There are a few intentional changes to lib-index and also mdbox
> code. One of those is that dovecot.index.cache files are being
> recreated more often now. In some cases they were wasting a lot of
> disk space because expunged mails hadn't been removed from them. I
> guess it's a possibility that all the disk IO was because in your
> system Dovecot started recreating all those files at the same time.
> Maybe you could try upgrading again during slower hours and see if the
> disk IO normalizes after a while?

Still running 2.3.7. 

Looking at the disk IO graphs today's IO usage looks OK!

I restarted dovecot yesterday after fixing the FTS settings:
Jul 16 10:14:45 mail-cbf dovecot: master: Dovecot v2.3.7 (494d20bdc) starting 
up for imap, lmtp (core dumps disabled)

after that I saw quite a bit of IO on sda1 (a bit of data read, lot of write),
which subsided at11:30

After that diskio was low, up to the present day.

-- 
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] 2.3.7 slower than 2.3.6?

2019-07-15 Thread Ralf Hildebrandt via dovecot 
* Ralf Hildebrandt via dovecot :
> We're using dovecot (via LMTP) as a backup for all incoming mail.
> 
> I upgraded from 2.3.6 to 2.3.7 on the 12th:
> 2019-07-12 14:35:44 upgrade dovecot-imapd:amd64 2:2.3.6-2~bionic 
> 2:2.3.7-8~bionic
> 
> and it seems that 2.3.7 is slower than 2.3.6 -- mail to the backup
> IMAP box is suddenly taking quite some time to get delivered and is piling up
> in the queue.

And alas, I had a look at the monitoring and found that disk IO has
increase A LOT after the update: 
https://www.arschkrebs.de/images/dovecot-disk-io-increase.png

I zoomed in and found that the sudden increace in IO coincides with
the update to 2.3.7 (14:35): https://www.arschkrebs.de/images/dovecot-io-2.png

-- 
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] 2.3.7 slower than 2.3.6?

2019-07-16 Thread Ralf Hildebrandt via dovecot 
* Timo Sirainen via dovecot :

> > And alas, I had a look at the monitoring and found that disk IO has
> > increase A LOT after the update: 
> > https://www.arschkrebs.de/images/dovecot-disk-io-increase.png
> > 
> > I zoomed in and found that the sudden increace in IO coincides with
> > the update to 2.3.7 (14:35): 
> > https://www.arschkrebs.de/images/dovecot-io-2.png 
> > <https://www.arschkrebs.de/images/dovecot-io-2.png>
> 

> Do the different disks have different kinds of data? 

All of the data is an /dev/sda1

> Like you seem to be using external attachments and fts? 

Jup, using that, but on one disk

> Also your doveconf -n
> doesn't show what fts backend you're using. Or is it just
> half-configured and not really used?

I used to use lucene, but then I had issues building it
and commented it out. 

Looking now, it turns out that your packages come with lucene support...
Reenabling:

mail_plugins = zlib fts fts_lucene

...

plugin {
  fts = lucene
  fts_autoindex = yes
  fts_languages = de,en
  fts_lucene = whitespace_chars=@.
  zlib_save = gz
  zlib_save_level = 5
}



-- 
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] dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

2019-10-01 Thread Ralf Hildebrandt via dovecot 
* Ralf Hildebrandt via dovecot :

> But why is that? Why would the index file be updated so often?

BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from back in 
July.

dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

2019-10-01 Thread Ralf Hildebrandt via dovecot 
I set up system copying all mails to a backup system.

This used to work without a hitch - now in the last few days mails
would pile up in the Postfix Queue, waiting to be delivered using the
lmtp transport into dovecot.

So dovecot was being slow, but why? After all, nothing changed.

After reading some articles on stackoverflow I found a way of finding
out which file gets the most IO:

% sysdig -c topfiles_bytes;

This command quickly pointed to 
~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp
That file was written excessively. 

I then put ~/mdbox/mailboxes/INBOX/dbox-Mails/ into tmpfs and alas, the queue 
would drain quickly.

But why is that? Why would the index file be updated so often?

This is dovecot 2.3.7.2-1~bionic

# 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf
# OS: Linux 5.0.0-29-generic x86_64 Ubuntu 18.04.3 LTS 
default_vsz_limit = 2 G
lmtp_user_concurrency_limit = 1
mail_attachment_dir = /home/copymail/attachments
mail_attachment_hash = %{sha256}
mail_fsync = never
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_languages = de,en
  fts_lucene = whitespace_chars=@.
}
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 = 10.0.5.208
port = 1025
  }
  process_min_avail = 5
  unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
  }
}
ssl_ca = /etc/ssl/certs/ca-certificates.crt
ssl_cert = https://www.charite.de

sis-queue: Parent filesystem not given as parameter

2019-09-26 Thread Ralf Hildebrandt via dovecot 
I tried to change:
mail_attachment_fs = sis posix
to
mail_attachment_fs = sis-queue posix

and immediately failed with:

Failed to initialize user: Namespace '': mdbox: mail_attachment_fs: sis-queue: 
Parent filesystem not given as parameter

Where do I specify the "Parent filesystem"?

-- 
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 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

2019-10-01 Thread Ralf Hildebrandt via dovecot 
> > This command quickly pointed to 
> > ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp
> > That file was written excessively. 
> 

> Was it one user's dovecot.index.tmp or for a lot of users?

There's just one user. All mail goes to one mailbox.

> This
> means that dovecot.index is being rewritten, which should happen only
> once in a while, but now it sounds like it's happening maybe for every
> mail delivery.

Yes, it seems to be that way.

> If it's still happening, could you send me one folder's
> dovecot.index and dovecot.index.log files? (They don't contain
> anything sensitive other than maybe message flags.)

I can send the files.

> > This is dovecot 2.3.7.2-1~bionic
> 
> So you had been running this version already for a while, and then it just 
> suddenly started getting slow?

Yes. Initially I threw away the whole mailbox after it got slow, but
after a few days the performance started to degrade. Admittedly, it
contains a lot of mails :)

> I tried to reproduce this with imaptest and Dovecot that is patched
> to log when dovecot.index is being rewritten, but there doesn't seem
> to be any difference with v2.2.36, v2.3.7 or git master.
 
-- 
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] dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

2019-10-16 Thread Ralf Hildebrandt via dovecot 
* Aki Tuomi via dovecot :

> 2.3.7 does not generate DH keys. It's been removed since 2.3.0

Yes, it was the only periodic process I could think/knew of.

> Is it possible for you to track and find out which process is causing the 
> peak?

Will try. Next hour :)

-- 
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] dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

2019-10-16 Thread Ralf Hildebrandt via dovecot 
* Ralf Hildebrandt via dovecot :
> * Timo Sirainen :
> 
> > > BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from 
> > > back in July.
> > 
> > Fixed by 
> > https://github.com/dovecot/core/commit/5e9e09a041b318025fd52db2df25052b60d0fc98
> >  and will be in the soon-to-be-released v2.3.8.
> 
> I stopped 2.3.7, copied over the index files from the ramdisk into
> the physical "realm" and restarted with a fresh 2.3.8. It probably
> takes a few days to be absolutely sure.

So, in general the performance issues are gone.

But... 

I'm seeing odd hourly spikes almost every hour, on the hour.
You might say: Well yes, that's a cronjob sending lots of mails. But
it isn't. There's not more or less mail coming in at that very moment.

I suspect something in dovecot running every hour (DH key regeneration?)

-- 
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 do I search for "greetings of the day"

2019-10-29 Thread Ralf Hildebrandt via dovecot 
My users say that "greetings of the day" occurs in academic spam a lot.
Since I don't trust my users, I opted to verify this bold claim.

But how do I search for a sequence of multiple words?

doveadm import -u restore@backup.invalid mdbox:/home/copymail/mdbox "" mailbox 
INBOX BODY "Greetings of the day"
doveadm import -u restore@backup.invalid mdbox:/home/copymail/mdbox "" mailbox 
INBOX TEXT "Greetings of the day"
(what's the difference betweeen BODY and TEXT?)

Is it even possible, given that "the" and "of" are probably stop words?
-- 
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] dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

2019-10-07 Thread Ralf Hildebrandt via dovecot 
* Timo Sirainen :

> >> But why is that? Why would the index file be updated so often?
> > 
> > BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from 
> > back in July.
> 
> Fixed by 
> https://github.com/dovecot/core/commit/5e9e09a041b318025fd52db2df25052b60d0fc98
>  
> <https://github.com/dovecot/core/commit/5e9e09a041b318025fd52db2df25052b60d0fc98>
>  and will be in the soon-to-be-released v2.3.8.

Thanks. I will test this (once it's been released) by moving the index files 
back to
conventional storage. 

-- 
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] dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

2019-10-08 Thread Ralf Hildebrandt via dovecot 
* Timo Sirainen :

> > BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from 
> > back in July.
> 
> Fixed by 
> https://github.com/dovecot/core/commit/5e9e09a041b318025fd52db2df25052b60d0fc98
>  and will be in the soon-to-be-released v2.3.8.

I stopped 2.3.7, copied over the index files from the ramdisk into
the physical "realm" and restarted with a fresh 2.3.8. It probably
takes a few days to be absolutely sure.

-- 
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: The future of SIS

2023-11-02 Thread Ralf Hildebrandt via dovecot 
* Pedro Ribeiro via dovecot :
> Hello everyone!
> I'm reviving the topic just to add that after reconstructing our storage with
> SIS disabled the occupied space increased from 5.3TB to 9.6TB, almost 
> doubling!
> It's a feature promoting storage efficiency, I think it demands some
> ponderation the advantages of keeping or improving the module.

Amen to that. I think the deduplication is a useful, storage efficient
way -- especially in large environments with lots of users (who get
the same mails :) )

-- 
Ralf Hildebrandt
  Geschäftsbereich IT | Abteilung Netz | Netzwerk-Administration
  Invalidenstraße 120/121 | D-10115 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
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

Re: [ext] dovecot 2.0 supports EC private key?

2023-10-24 Thread Ralf Hildebrandt via dovecot 
* Marc :
> 
> Does dovecot 2.0 supports EC private key?

Yes:

# Certbot RSA
ssl_cert = https://www.charite.de

___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org

<    2   3   4   5   6   7