Displaying 20 results from an estimated 100 matches similar to: "crash with "The specified message set is invalid.""
2017 Sep 07
0
imapc bug (signal 6)
Running 2.3.0~alpha0-1~auto+1045, basically as a proxy between MUA and
Exchange (IMAP):
Sep 7 16:10:32 mproxy dovecot: imap-login: Login: user=<holtgrem>, method=PLAIN, rip=172.16.128.8, lip=141.42.206.11, mpid=61031, TLS, session=<fp3JBZpYop+sEIAI>
Sep 7 16:10:32 mproxy dovecot: imap(holtgrem)<fp3JBZpYop+sEIAI>: imapc(exchange-imap.charite.de:993): Connected to
2016 Apr 29
4
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,
2014 Aug 25
0
IMAP Proxying to an Exchange Server
We're proxying IMAP to an Exchange server. One of my colleagues is
getting this when trying to save a message as "Draft" OR as "Sent
items":
Aug 25 13:45:41 mproxy dovecot: imap(froemmel): Error: imapc(exchange-imap.charite.de:993): Command '7 APPEND "Entw&APw-rfe" (\Draft) {232572}' timed out, disconnecting
Aug 25 13:45:41 mproxy dovecot:
2017 Mar 23
2
Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Ralf Hildebrandt <r at 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:
2014 May 16
1
imapc Proxy to IMAPS Exchangeserver?
I'm trying to adapt http://wiki2.dovecot.org/HowTo/ImapcProxy
to our Exchange Server, which has LOGINDISABLED on Port 143, and I
offering LOGIN on Port 993.
How do I go about this?
Simply changing imapc_port to:
imapc_port = 993
doesnt work:
Connected to localhost.
Escape character is '^]'.
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS
2017 Mar 20
4
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:
2017 Mar 23
0
Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
On 23.03.2017 11:59, Ralf Hildebrandt wrote:
> * Ralf Hildebrandt <r at 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_*
2017 Mar 20
0
Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Ralf Hildebrandt <dovecot at dovecot.org>:
> * Aki Tuomi <aki.tuomi at 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
2017 Mar 20
2
Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Aki Tuomi <aki.tuomi at dovecot.fi>:
>
>
> On 20.03.2017 14:30, Ralf Hildebrandt wrote:
> > ssl_client_ca_file = </etc/ssl/certs/ca-certificates.crt
>
> 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
2017 Mar 20
0
Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
On 20.03.2017 16:40, Ralf Hildebrandt wrote:
> * Aki Tuomi <aki.tuomi at dovecot.fi>:
>>
>> On 20.03.2017 14:30, Ralf Hildebrandt wrote:
>>> ssl_client_ca_file = </etc/ssl/certs/ca-certificates.crt
>> Leave the < out. It is misleading, I know, but it does say file. =)
> Makes no difference:
>
> # doveconf |fgrep ssl_client_ca
>
2016 Mar 30
2
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=<xxxbxxx>, method=PLAIN, rip=10.39.76.71, lip=141.42.206.11, mpid=18556, TLS, session=<H98xGkAvfvMKJ0xH>
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
2017 May 31
2
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
2017 Dec 14
0
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 = <redacted>.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 {
2016 Jul 11
4
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=<hildeb>, method=PLAIN, rip=141.42.206.36, lip=141.42.206.11, mpid=27254, TLS, session=<TGwoO1o3id+NKs4k>
Jul 11 13:12:44 mproxy dovecot: imap(hildeb)<TGwoO1o3id+NKs4k>: Panic: file imap-client.c: line 854 (client_check_command_hangs): assertion failed: ((io_loop_find_fd_conditions(current_ioloop,
2017 Jun 02
0
Bug with 2.2.29-1~auto+25 back to haunt me
* Aki Tuomi <aki.tuomi at 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=</etc/ssl/certs/ca-certificates.crt
...
or
args =
2017 Jun 02
2
Bug with 2.2.29-1~auto+25 back to haunt me
> On June 1, 2017 at 1:42 PM Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> wrote:
>
>
> * Aki Tuomi <aki.tuomi at 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
2017 May 31
2
Bug with 2.2.29-1~auto+25 back to haunt me
> On May 31, 2017 at 6:10 PM Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> wrote:
>
>
> * Ralf Hildebrandt <Ralf.Hildebrandt at 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
2017 May 31
0
Bug with 2.2.29-1~auto+25 back to haunt me
* Ralf Hildebrandt <Ralf.Hildebrandt at 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 = <file
>
> Gnarf! As you can see I do HAVE ssl_ca in my doveconf -n output!
>
>
2017 Jun 01
0
Bug with 2.2.29-1~auto+25 back to haunt me
* Aki Tuomi <aki.tuomi at 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 = <file
> > >
> > > Gnarf! As you can
2014 Jun 16
1
SIGSEGV in 2.2.13 with IMAP Proxying to an Exchange Server
100% reproducible. User is using alpine to write an email.
Continue postponed composition (answering "No" won't erase it)?
y -> [>Empty folder! No messages really postponed!<]
Can't delete {mproxy.charite.de/ssl/novalidate-cert/user=theusername}postponed-msgs
Setup:
======
http://wiki2.dovecot.org/HowTo/ImapcProxy
coredump available for further inspection
Full