IMAP folder separator oddness

Hello, yesterdays changes to tip seem to cause the wrong IMAP folder separator to be printed in "New mail in ..." notifications, in the browser, and in "Open mailbox ..." dialogs (when using the `change-folder' command): I suddenly see a slash instead of a dot when reading mail from a Cyrus IMAP s

regression: attaching files from command line fails

Hello, since I updated Mutt to the latest tip a few days ago, sending a message with attached files from the command line fails: $ echo test >file $ mutt -a file [EMAIL PROTECTED]

Re: regression: attaching files from command line fails

Aron Griffis --> mutt-dev (2008-10-23 10:50:05 -0400): > Aron Griffis wrote: [Thu Oct 23 2008, 10:07:02AM EDT] > > What OS is this? There are some patches recently in mutt that > > affect cmdline processing, but your example works for me. > > My mistake, your example doesn't work for me. The re

regression between revisions 5546 and 5554

Hello, I'm seeing some recently introduced problems with Mutt, mainly regarding browsing IMAP folders (on Cyrus 2.1 and 2.2 IMAP servers; I didn't try other IMAP servers). Up to revision 5546 everything worked for me as expected. Starting with revision 5547 and up to 5553, browsing IMAP folders w

Re: regression between revisions 5546 and 5554

Jukka Salmi --> mutt-dev (2008-11-08 14:01:08 +0100): > Hello, > > I'm seeing some recently introduced problems with Mutt, mainly regarding > browsing IMAP folders (on Cyrus 2.1 and 2.2 IMAP servers; I didn't try > other IMAP servers). > > Up to revision 5546 ev

Re: IMAP folder separator oddness

Brendan Cully --> mutt-dev (2008-11-16 21:06:14 -0800): > On Tuesday, 21 October 2008 at 10:17, Jukka Salmi wrote: > > Hello, > > > > yesterdays changes to tip seem to cause the wrong IMAP folder separator > > to be printed in "New mail in ..." notific

Mutt hangs while reading message headers

Hello, my Mutt from hg tip hangs while reading the headers of [1]this message, printing Fetching message headers... 0/15 (0%) and using up almost all the CPU time. Running Mutt with -d2 prints: [...] 4< * 2 FETCH (FLAGS () UID 1498 INTERNALDATE "17-Nov-2008 03:43:15 +0100" RFC822.SIZE

service name in smtp_url

Hello, I just noticed that Mutt seems not to accept service names (as opposed to numbers) in smtp_url. Thus something like set smtp_url="smtp://example.org:submission/" doesn't work (and uses the default port instead), but set smtp_url="smtp://example.org:587/" does. Glancing

Re: service name in smtp_url

Rocco Rutte --> mutt-dev (2009-04-16 17:36:27 +0200): > Yes, see http://dev.mutt.org/doc/manual.html#url-syntax. For some > protocols, it uses getservbyname() to determine the port if none is > given in the URL. For using the submission port you'll have to specify > the numeric port number as mu

IMAP regression after rev 5024

Hi, with Mutt built using today's sources (rev 5034) I see the following behaviour (I use IMAP mailboxes exclusively): after being started Mutt seems to correctly determine which mailboxes contain new messages, i.e. `change-folder' presents a list of mailboxes containing new messages. But after I'

IMAP: UNSEEN not honoured until first mail_check

Hi, if none of the mailboxes which Mutt checks for new messages contain new messages, but some of them contain unseen ones, these mailboxes are not shown when issuing `change-folder' from the index menu right after starting Mutt, i.e. until Mutt checks for new mail for the first time. Only after $

Re: IMAP: UNSEEN not honoured until first mail_check

Jukka Salmi --> mutt-dev (2007-04-04 14:26:54 +0200): > Hi, > > if none of the mailboxes which Mutt checks for new messages contain > new messages, but some of them contain unseen ones, these mailboxes > are not shown when issuing `change-folder' from the index menu righ

BDB4 from pkgsrc

Hi, when installing BDB4 from [1]pkgsrc, include files end up in .../include/db4/ while libraries go to .../lib/. The current configure script needs the attached patch to detect this correctly. Regards, Jukka P.S.: I ignored correct indentation to make the patch more concise. [1] http://www.pk

Re: BDB4 from pkgsrc

Fabian Groffen --> mutt-dev (2007-04-07 14:17:41 +0200): [...] > > 2) My suspicions are that after this patch my segfaults in hcache are > >back again. I think the reason is the following: > > [snip] > > > Includes are taken from db4.3, while the final linking is done against > > db-4.5. So

Re: BDB4 from pkgsrc

Hi, Fabian Groffen --> mutt-dev (2007-04-07 16:27:41 +0200): > On 07-04-2007 16:10:30 +0200, Jukka Salmi wrote: [..] > > Which bdb versions do you have installed? Which are the paths to the > > include files and to the libraries? > > sys-libs/db > selected: 4.

Re: Mutt and Berkely DB, the results of the cruisade

Matthias Andree --> mutt-dev (2007-04-07 22:24:02 +0200): [...] > and this I got: > > $ egrep '^((C|CPP|LD)FLAGS|LIBS).*=' Makefile > CFLAGS = -Wall -pedantic -g -O2 > CPPFLAGS = -I/usr/local/BerkeleyDB.4.3/include// -I$(top_srcdir)/intl > LDFLAGS = > LIBS = -lidn -L/usr/local/BerkeleyDB.4.3/lib

Re: BDB4 from pkgsrc

Fabian Groffen --> mutt-dev (2007-04-09 12:59:20 +0200): > On 07-04-2007 18:15:17 +0200, Jukka Salmi wrote: > > > Additionally I have a symlink usr/include/db.h pointing to db4.5/db.h. > > > Similar usr/lib/libdb.so is pointing to libdb-4.5.so. For Darwin this > > &

segfault in imap_hcache_open()

Hi, the latest Mutt (1.5.15 (2007-04-10)) crashes quite reproducibly when using IMAP folders: $ gdb mutt mutt.core [...] Core was generated by `mutt'. Program terminated with signal 11, Segmentation fault. #0 0x080c6ce7 in imap_hcache_open (idata=0x8138400, path=0x8138609 "INBOX") at util.c:86

Re: segfault in imap_hcache_open()

BTW, this seems to have been introduced somewhere after rev 5110. Jukka Salmi --> mutt-dev (2007-04-11 14:27:55 +0200): > Hi, > > the latest Mutt (1.5.15 (2007-04-10)) crashes quite reproducibly when > using IMAP folders: > > $ gdb mutt mutt.core > [...] >

Re: segfault in imap_hcache_open()

Brendan Cully --> mutt-dev (2007-04-11 07:40:17 -0700): > Whoops, silly bug. I think 5121:29faa739ed01 should fix it. It does. Thanks! Regards, Jukka -- bashian roulette: $ ((RANDOM%6)) || rm -rf ~

Re: some oddities with latest CVS HEAD Mutt

Jukka Salmi --> mutt-dev (2006-07-12 17:19:04 +0200): [...] > Sometimes Mutt seems to forget marking messages as read. Most of the > time it works fine, but every now and then I read a newly received > message, close Mutt, start it again, and the message I had just read > still has

Re: some oddities with latest CVS HEAD Mutt

Brendan Cully --> mutt-dev (2007-04-18 07:20:52 -0400): > The 'Seen' flag is usually managed by the server, and automatically > set by it when you read a message. The only time mutt explicitly sets > it is if you use the set/clear flag function. So it sounds to me as > though it's your IMAP server

Re: Mutt ignoring Reply-To

[moving from mutt-users] Jukka Salmi --> mutt-users (2007-08-02 13:41:13 +0200): > Rado S --> mutt-users (2007-08-01 19:34:48 +0200): > > =- Jukka Salmi wrote on Wed 1.Aug'07 at 11:53:41 +0200 -= > > > > > I'm using Mutt 1.5.16. When replying to a mail

segfault in mx_update_context()

Hello, some days ago Mutt crashed as follows: $ gdb /usr/local/bin/mutt mutt.core GNU gdb 6.5 [...] Core was generated by `mutt'. Program terminated with signal 11, Segmentation fault. #0 0x080807f7 in mx_update_context (ctx=0xbb629380, new_messages=6) at mx.c:1561 1561 h->security =