Your message dated Tue, 1 Jan 2008 20:57:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#458447: dovecot-imapd: Can't connect to dovecot since 
1.0.9 (from 1.0.5)
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: dovecot-imapd
Version: 1:1.0.5-1
Severity: grave
Justification: renders package unusable

Since I updated dovecot from 1.0.5-1 to 1.0.9-1 I can't connect to my imapd 
with mutt
and roundcube anymore.

I get this error with mutt :
tls_socket_read (A TLS packet with unexpected length was received.)

I didn't change anything in the conf.

Please notice that I recompiled it from source and I modified the debian/rules 
script to enable vpopmail.


-- System Information:
Debian Release: 4.0
  APT prefers stable
  APT policy: (990, 'stable'), (500, 'proposed-updates'), (450, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.22-2-686
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages dovecot-imapd depends on:
ii  dovecot-common         1:1.0.5-1         secure mail server that supports m
ii  libc6                  2.3.6.ds1-13etch4 GNU C Library: Shared libraries
ii  libssl0.9.8            0.9.8c-4etch1     SSL shared libraries

dovecot-imapd recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Hello,

* 2008-01-01 16:55, Victor NOEL wrote:
> I am sorry, in fact it was my error, I was using a plugin I compiled
> myself and there was a problem with it, it caused this error and I
> couldn't find anything in the log (but there should be a place if I look
> carefully where there is an error :)

Let's close the bug report, then.

Happy new year!

-- 
Fabio Tranchitella                         http://www.kobold.it
Free Software Developer and Consultant     http://www.tranchitella.it
_____________________________________________________________________
1024D/7F961564, fpr 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564


--- End Message ---

Reply via email to