Re: Header caching not working

2009-06-15 Thread Brendan Cully
On Saturday, 13 June 2009 at 19:46, John Magolske wrote:
> Hi,
> 
> I'm running Mutt on Debian unstable and have not been able to get
> header caching to work. I've created a directory "mutt-headercache"
> in $HOME:
> 
> % ls -ld ~/mutt-headercache
> drwxrwxr-x 2 me me 4096 2009-03-21 22:19 /home/me/mutt-headercache/
> 
> and put this in my ~/.muttrc:
> 
> set header_cache = ~/mutt-headercache/
> set header_cache_pagesize = '32000'
> 
> ":set ?header_cache" returns "header_cache=~/mutt-headercache/"
> 
> But this directory remains completely empty at all times. 
> 
> I'm using pop3, mbox & ext3.
> 
> TIA for any suggestions on how to get this working,

Mutt doesn't cache headers for mbox mailboxes. For pop3 it should if
and only if you're using pop:// access. Downloading pop into a local
mbox with pop_host and fetch-mail means you're using mbox to read your
mail and won't need header caching.


Header caching not working

2009-06-13 Thread John Magolske
Hi,

I'm running Mutt on Debian unstable and have not been able to get
header caching to work. I've created a directory "mutt-headercache"
in $HOME:

% ls -ld ~/mutt-headercache
drwxrwxr-x 2 me me 4096 2009-03-21 22:19 /home/me/mutt-headercache/

and put this in my ~/.muttrc:

set header_cache = ~/mutt-headercache/
set header_cache_pagesize = '32000'

":set ?header_cache" returns "header_cache=~/mutt-headercache/"

But this directory remains completely empty at all times. 

I'm using pop3, mbox & ext3.

TIA for any suggestions on how to get this working,

John




More info:

# tune2fs -l /dev/hda1
  ...
Filesystem features:has_journal resize_inode dir_index filetype
needs_recovery sparse_super large_file


% mutt -v
mutt: /usr/lib/libidn.so.11: no version information available (required by mutt)
Mutt 1.5.19 (2009-01-05)
Copyright (C) 1996-2009 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.

System: Linux 2.6.26-grml (i686)
ncurses: ncurses 5.7.20081115 (compiled with 5.7)
libidn: 1.10 (compiled with 1.14)
hcache backend: GDBM version 1.8.3. 10/15/2002 (built Aug 27 2008 09:23:18)
Compile options:
-DOMAIN
+DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  +USE_FCNTL  -USE_FLOCK
+USE_POP  +USE_IMAP  +USE_SMTP
-USE_SSL_OPENSSL  +USE_SSL_GNUTLS  +USE_SASL  +USE_GSS  +HAVE_GETADDRINFO
+HAVE_REGCOMP  -USE_GNU_REGEX
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM
+CRYPT_BACKEND_CLASSIC_PGP  +CRYPT_BACKEND_CLASSIC_SMIME  +CRYPT_BACKEND_GPGME
-EXACT_ADDRESS  -SUN_ATTACHMENT
+ENABLE_NLS  -LOCALES_HACK  +COMPRESSED  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET 
 +HAVE_LANGINFO_YESEXPR
+HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  +USE_HCACHE
-ISPELL
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/etc"
EXECSHELL="/bin/sh"
MIXMASTER="mixmaster"
To contact the developers, please mail to .
To report a bug, please visit http://bugs.mutt.org/.

patch-1.5.13.cd.ifdef.2
patch-1.5.18.rr.compressed.1


-- 
John Magolske
http://B79.net/contact


Re: Header caching not working

2008-12-04 Thread Szymek
On Thu, Dec 04, 2008 at 04:03:07PM +0100, Sander Smeenk wrote:
> Quoting Szymek ([EMAIL PROTECTED]):
> 
> > > | +HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  +USE_HCACHE
> > The only difference is, that I dont have libidn enabled.
> > Is this setting relevant?
> 
> No. IDN is used for domainnames containing s??l ??rrs. It 
> has
> nothing to do with headercaching. Also, your mutt -v output does not
> have to match ours, it's just about the +USE_HCACHE bit.
> 
> > I have only one config file, .muttrc. When I type while being in
> > mutt: :set ?header_cache, I get a correct result 
> > (/home/szymek/mail/hcache/).
> > I can create files and dirs in ~/mail/hcache.
> 
> In that case, i'm at a loss too. It should just work. To really find out
> what's happening, you'd have to start using strace, gdb and maybe even
> dig around in the source.
> 
> > I read somewhere, that libidn for mutt is an optional dependency
> > and has something to do with domain names.
> 
> Correct.
> 
> -Sndr.
> -- 
> | He had a photographic memory which was never developed.  
> | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D
> 

Hi

Thanks all of your folks for the help. I dont have actually the time and the
skills to manage such a task like deubugging, so I will leve it the way it is.
There are not so many mails in my folders (three hundert is most), so I can
live without header caching, too.

Best regards
Szymon


Re: Header caching not working

2008-12-04 Thread Sander Smeenk
Quoting Szymek ([EMAIL PROTECTED]):

> > | +HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  +USE_HCACHE
> The only difference is, that I dont have libidn enabled.
> Is this setting relevant?

No. IDN is used for domainnames containing sρεςιαl ςλαrαςτεrs. It has
nothing to do with headercaching. Also, your mutt -v output does not
have to match ours, it's just about the +USE_HCACHE bit.

> I have only one config file, .muttrc. When I type while being in
> mutt: :set ?header_cache, I get a correct result (/home/szymek/mail/hcache/).
> I can create files and dirs in ~/mail/hcache.

In that case, i'm at a loss too. It should just work. To really find out
what's happening, you'd have to start using strace, gdb and maybe even
dig around in the source.

> I read somewhere, that libidn for mutt is an optional dependency
> and has something to do with domain names.

Correct.

-Sndr.
-- 
| He had a photographic memory which was never developed.  
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D


Re: Header caching not working

2008-12-04 Thread Szymek
On Thu, Dec 04, 2008 at 08:55:22AM +0100, Sander Smeenk wrote:
> Quoting Kyle Wheeler ([EMAIL PROTECTED]):
> 
> > >Could it be, that I have to compile with use_imap option?
> > Nah, it should work with other things (e.g. Maildir and POP3).
> > Well, I'm stumped. Anyone else have an idea?
> 
> Works for me(TM)
> 
> | Mutt 1.5.17+20080114 (2008-01-14)
> | ...
> | +HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  +USE_HCACHE
> | ...
> 
> And this is in my config:
> 
> | set header_cache=/home/sanders/.mutt/header_cache/
> 
> Does the OP use one monolithic configuration file? 
> Is he sure this value is set correctly?
> Typing ':set ?header_cache' should give results.
> Are the permissions on the directory okay?
> Can his user create files and/or directories there?
> 
> -Sndr.
> -- 
> | Someone who thinks logically provides a nice contrast to the real world.
> | 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D

The only difference is, that I dont have libidn enabled. Is this setting
relevant? I have only one config file, .muttrc. When I type while being in
mutt: :set ?header_cache, I get a correct result (/home/szymek/mail/hcache/).
I can create files and dirs in ~/mail/hcache.
I read somewhere, that libidn for mutt is an optional dependency and has
something to do with domain names.

Thanks
Szymon 


Re: Header caching not working

2008-12-03 Thread Sander Smeenk
Quoting Kyle Wheeler ([EMAIL PROTECTED]):

> >Could it be, that I have to compile with use_imap option?
> Nah, it should work with other things (e.g. Maildir and POP3).
> Well, I'm stumped. Anyone else have an idea?

Works for me(TM)

| Mutt 1.5.17+20080114 (2008-01-14)
| ...
| +HAVE_ICONV  -ICONV_NONTRANS  +HAVE_LIBIDN  +HAVE_GETSID  +USE_HCACHE
| ...

And this is in my config:

| set header_cache=/home/sanders/.mutt/header_cache/

Does the OP use one monolithic configuration file? 
Is he sure this value is set correctly?
Typing ':set ?header_cache' should give results.
Are the permissions on the directory okay?
Can his user create files and/or directories there?

-Sndr.
-- 
| Someone who thinks logically provides a nice contrast to the real world.
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D


signature.asc
Description: Digital signature


Re: Header caching not working

2008-12-03 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Wednesday, December  3 at 01:19 PM, quoth Szymek:
>+USE_HCACHE

Hmm, okay, so... it's got it...

>Could it be, that I have to compile with use_imap option?

Nah, it should work with other things (e.g. Maildir and POP3).

Well, I'm stumped. Anyone else have an idea?

~Kyle
- -- 
I have not failed. I've just found 10,000 ways that won't work.
   -- Thomas Edison
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkk2rYAACgkQBkIOoMqOI16MzwCgz433jDTPnYHZ3AvsFNtVBUK9
IQcAnRg0NOU1CvD0KQaM88Y6wzz1NMQl
=i8sv
-END PGP SIGNATURE-


Re: Header caching not working

2008-12-03 Thread Szymek
Hi

I just have pasted the output of mutt -v in wrong way, here it is again:

-DOMAIN
-DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  
+USE_FCNTL  -USE_FLOCK   -USE_INODESORT   
-USE_POP  -USE_IMAP  -USE_GSS  -USE_SSL  -USE_GNUTLS  -USE_SASL  -USE_SASL2  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  
-CRYPT_BACKEND_CLASSIC_PGP  -CRYPT_BACKEND_CLASSIC_SMIME  -CRYPT_BACKEND_GPGME

-BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  -LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET 
+HAVE_LANGIN   
FO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  -HAVE_LIBIDN  +HAVE_GETSID  -HAVE_GETADDRINFO 
+USE_HCACHE  
ISPELL="/usr/bin/ispell"
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/usr/etc"
EXECSHELL="/bin/sh"
-MIXMASTER


Could it be, that I have to compile with use_imap option?

BTW, I am an engineer:)


On Tue, Dec 02, 2008 at 04:12:17PM -0600, Kyle Wheeler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On Tuesday, December  2 at 10:42 PM, quoth Szymek:
> >That's the output of mutt -v:
> 
> Now that is *really* weird. I think there's either something wrong 
> with the way you compiled it, or your source is corrupt. And I say 
> that because your mutt spit out that full thing *twice*, and it's not 
> supposed to do that. (Notice that from -DOMAIN through to ISPELL=... 
> is duplicated.)
> 
> Are you using any patches besides the MDN patch?
> 
> Try doing a `make clean` and then build mutt again.
> 
> ~Kyle
> - -- 
> Arguing with an engineer is like wrestling with a pig in mud, after a 
> while you realize the pig is enjoying it.
>  -- Unknown
> -BEGIN PGP SIGNATURE-
> Comment: Thank you for using encryption!
> 
> iEYEARECAAYFAkk1ssEACgkQBkIOoMqOI17gnwCg4TUbHRoflIE/1cnQkpIP6H1K
> 2+4An3Z/rR8ZATeSfvh78QaEhkCGSRnZ
> =SjZh
> -END PGP SIGNATURE-
> 


Re: Header caching not working

2008-12-02 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday, December  2 at 10:42 PM, quoth Szymek:
>That's the output of mutt -v:

Now that is *really* weird. I think there's either something wrong 
with the way you compiled it, or your source is corrupt. And I say 
that because your mutt spit out that full thing *twice*, and it's not 
supposed to do that. (Notice that from -DOMAIN through to ISPELL=... 
is duplicated.)

Are you using any patches besides the MDN patch?

Try doing a `make clean` and then build mutt again.

~Kyle
- -- 
Arguing with an engineer is like wrestling with a pig in mud, after a 
while you realize the pig is enjoying it.
 -- Unknown
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkk1ssEACgkQBkIOoMqOI17gnwCg4TUbHRoflIE/1cnQkpIP6H1K
2+4An3Z/rR8ZATeSfvh78QaEhkCGSRnZ
=SjZh
-END PGP SIGNATURE-


Re: Header caching not working

2008-12-02 Thread Szymek
On Tue, Dec 02, 2008 at 11:02:42AM -0600, Kyle Wheeler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On Tuesday, December  2 at 05:57 PM, quoth Szymek:
> > Yes, I forgot to make a test:) But there is no difference, still no 
> > files in hcache folder.
> 
> Hmm. When you run `mutt -v`, do you see +USE_HCACHE in there?
> 
> ~Kyle
> - -- 
> I have not failed. I've just found 10,000 ways that won't work.
>-- Thomas Edison
> -BEGIN PGP SIGNATURE-
> Comment: Thank you for using encryption!
> 
> iEYEARECAAYFAkk1ajIACgkQBkIOoMqOI164+gCgzX2q+sakaXwlfchbgGcNRo9S
> af8AoO9MQDYElq4uL6CLORlAW2bwRL6R
> =ua8S
> -END PGP SIGNATURE-
> 
That's the output of mutt -v:

-DOMAIN
-DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  
+USE_FCNTL  -USE_FLOCK   -USE_INODESORT   
-USE_POP  -USE_IMAP  -USE_GSS  -USE_SSL  -USE_GNUTLS  -USE_SASL  -USE_SASL2  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  
-CRYPT_BACKEND_CLASSIC_PGP  -CRYPT_BACKEND_CLASSIC_SMIME  -CRYPT_BACKEND_GPGME
 -BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  -LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET 
+HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  -HAVE_LIBIDN  +HAVE_GETSID  -HAVE_GETADDRINFO 
+USE_HCACHE  
ISPELL="/usr/bin/ispell"
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE  
+USE_FCNTL  -USE_FLOCK   -USE_INODESORT   
-USE_POP  -USE_IMAP  -USE_GSS  -USE_SSL  -USE_GNUTLS  -USE_SASL  -USE_SASL2  
+HAVE_REGCOMP  -USE_GNU_REGEX  
+HAVE_COLOR  +HAVE_START_COLOR  +HAVE_TYPEAHEAD  +HAVE_BKGDSET  
+HAVE_CURS_SET  +HAVE_META  +HAVE_RESIZETERM  
-CRYPT_BACKEND_CLASSIC_PGP  -CRYPT_BACKEND_CLASSIC_SMIME  -CRYPT_BACKEND_GPGME
 -BUFFY_SIZE -EXACT_ADDRESS  -SUN_ATTACHMENT  
+ENABLE_NLS  -LOCALES_HACK  +HAVE_WC_FUNCS  +HAVE_LANGINFO_CODESET 
+HAVE_LANGINFO_YESEXPR  
+HAVE_ICONV  -ICONV_NONTRANS  -HAVE_LIBIDN  +HAVE_GETSID  -HAVE_GETADDRINFO 
+USE_HCACHE  
ISPELL="/usr/bin/ispell"
SENDMAIL="/usr/sbin/sendmail"
MAILPATH="/var/mail"
PKGDATADIR="/usr/share/mutt"
SYSCONFDIR="/usr/etc"
EXECSHELL="/bin/sh"
-MIXMASTER

patch-1.5.8.g10.mdn.3


I think, that everything is ok with compilation, or is there maybe another
option, which I have to pass to configure script? Maybe this mutt version is
not ready for maildir with header caching?


best regards to all mutters


Re: Header caching not working

2008-12-02 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday, December  2 at 05:57 PM, quoth Szymek:
> Yes, I forgot to make a test:) But there is no difference, still no 
> files in hcache folder.

Hmm. When you run `mutt -v`, do you see +USE_HCACHE in there?

~Kyle
- -- 
I have not failed. I've just found 10,000 ways that won't work.
   -- Thomas Edison
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkk1ajIACgkQBkIOoMqOI164+gCgzX2q+sakaXwlfchbgGcNRo9S
af8AoO9MQDYElq4uL6CLORlAW2bwRL6R
=ua8S
-END PGP SIGNATURE-


Re: Header caching not working

2008-12-02 Thread Szymek
On Tue, Dec 02, 2008 at 09:45:27AM -0600, Kyle Wheeler wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On Tuesday, December  2 at 03:03 PM, quoth Szymek:
> > There are no files created in the hcache folder, why? Do I have to 
> > put a slash at the end of the line in .muttrc?
> 
> Yup.
> 
> You probably could have even tested that yourself! ;)
> 
> ~Kyle


Yes, I forgot to make a test:) But there is no difference, still no files in
hcache folder.


Re: Header caching not working

2008-12-02 Thread Kyle Wheeler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday, December  2 at 03:03 PM, quoth Szymek:
> There are no files created in the hcache folder, why? Do I have to 
> put a slash at the end of the line in .muttrc?

Yup.

You probably could have even tested that yourself! ;)

~Kyle
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkk1WBEACgkQBkIOoMqOI14ongCeOTxXhvER1vp+xa/BO/DwsgpT
n9QAoLJahTsiEafBgtFzQgB3UmmHTrY4
=lWFT
-END PGP SIGNATURE-


Header caching not working

2008-12-02 Thread Szymek
Hello

I have some problems with header caching in mutt. I have set the following
variable in .muttrc: set header_cache=$HOME/mail/hcache

My mail is organized like that:

$HOME/mail
   -> box1
   -> box2
   -> box3
   -> hcache

There are no files created in the hcache folder, why? Do I have to put a slash
at the end of the line in .muttrc? All of my mailboxes are in maildir format,
I have mutt version 1.5.8i with mdn-patch and the header-cache option passed
to configure during building. What could be wrong? I didn't use a separate
patch for hcache.


Best regards
Szymon