Debian Bug report logs - #195068
mutt-1.5.4i: imap in config file generates errors

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: kapil@imsc.res.in

To: submit@bugs.guug.de, submit@bugs.debian.org

Subject: mutt-1.5.4i: imap in config file generates errors

Date: Wed, 28 May 2003 18:33:52 +0530

Package: mutt
Version: 1.5.4-1
Severity: normal

-- Please type your report below this line

Setting the "folder" variable to "imaps://hostname/" in .muttrc
causes an error with the message:

	"tls_socket_read (A TLS packet with unexpected length was received.)"

Setting the same variable to the same value after starting a session without setting
this variable in .muttrc causes no errors. 

In case this helps in debugging, the remote server is running uw-imapd-ssl (stable).

Thanks and regards,

Kapil.


-- System Information
System Version: Linux nmlinux47 2.4.20-1-686 #1 Sat Mar 22 13:16:21 EST 2003 i686 GNU/Linux

-- Build environment information

Debian "sarge" build downloaded from raff.debian.org

Using "libgnutls5" Version: 0.8.6-4 from the same source.

--- Begin /home/kapil/.muttrc
set mbox_type = maildir
set pgp_sign_as = 0xFED1D08D
set postponed = ~/Mail/postponed
set wait_key = no
set pipe_decode = no
set use_domain = yes
set mime_forward = ask-yes
set mime_forward_decode = yes
folder-hook . set sort=date-received
folder-hook backup set sort=date-received
folder-hook . set mh_purge=no
folder-hook spam set mh_purge=yes
set record = ~/Mail/backup
ignore *
--- End /home/kapil/.muttrc

Message #10 received at 195068@bugs.debian.org (full text, mbox, reply):

From: "Kapil Hari Paranjape" <kapil@imsc.res.in>

To: 195068@bugs.debian.org

Subject: Problem causedd by user's config file

Date: Thu, 29 May 2003 10:04:28 +0530

Hello,

I found the reason for the error. It was caused by a

	set folder="imap://host/Mail"
	mailboxes +foo +bar

Configuration commands which advertantly got left out of the earlier
transcript.

Apparently the use of mailboxes which are "imap folders" is incompatible
with the use of  "set folder imap://host/Mail".

Is this documented somewhere?

Sorry for the mistaken config file. Enclosed is the real one

Kapil.

----.muttrc--------
set folder="imap://user@host/Mail"
set spoolfile = +inbox
set imap_list_subscribed = yes
set mbox_type = maildir
set postponed = ~/Mail/postponed
set wait_key = no
set pipe_decode = no
set use_domain = yes
set alias_file = ~/Mail/aliases
set mime_forward = ask-yes
set mime_forward_decode = yes
#set sort_browser = reverse-date
set record = ~/Mail/backup
source ~/Mail/aliases

mailboxes ! +foo +bar 
----.muttrc--------

--

Message #15 received at 195068@bugs.debian.org (full text, mbox, reply):

From: "Kapil Hari Paranjape" <kapil@imsc.res.in>

To: 195068@bugs.debian.org

Subject: Error in imapd not mutt

Date: Fri, 30 May 2003 20:18:15 +0530

Package: uw-imapd-ssl
Version: 4:2001adebian-6
Severity: normal

-- Comments Follow

Hello,

Found that the bug was not in mutt after all.

I ran the imapd under strace by using a mutt "tunnel" and found that the
problem is with the um-imapd handling of "maildir" style folders. The
imapd was dying with a segmentation fault whenever it is asked to check
for new mail when it has mailboxes which are maildir style folders
(as configured with ~/.mailboxes).

So I am re-asigning this bug to uw-imapd-ssl in the next control.

Regards,

Kapil.


-- System Information
System Version: Linux banyan 2.2.19 #1 Thu Nov 8 17:07:29 IST 2001 i686 unknown
Debian Version: stable/woody

--

Message #22 received at 195068-done@bugs.debian.org (full text, mbox, reply):

From: "Kapil Hari Paranjape" <kapil@imsc.res.in>

To: 195068-done@bugs.debian.org

Subject: Seems to be fixed in Version: 6:2003debian0.0304182231-1

Date: Sat, 31 May 2003 10:42:31 +0530

Hello,

Seems I'm the only one commenting on my own bug!

Anyway, it seems that the problem is fixed with the current version
of uw-imapd Version: 6:2003debian0.0304182231-1 in "testing/sarge".

Since there is a SEGV crash for the stable version I guess we should
point it out to the security team.

Regards,

Kapil.

-- 
Research is to see what everybody else has seen, and think what nobody
else has thought.
--

Send a report that this bug log contains spam.