Re: How to get default "From:" to work
No, the maildir folders are not nested, here is the structure: ~/mail-> ->firstbox ->secondbox ->thirdbox ->fourthbox I compiled mutt by myself, maybe there is a specific option to pass to configure? I had previously the same config in Slackware, and it worked like a charm. On Sat, Nov 22, 2008 at 09:48:03AM -0800, Michael Elkins wrote: > On Sat, Nov 22, 2008 at 04:31:57PM +0100, [EMAIL PROTECTED] wrote: > > folder-hook . 'set from="[EMAIL PROTECTED]" realname="Blabla"' > > folder-hook secondbox 'set from="[EMAIL PROTECTED]" realname="BlaBla"' > > folder-hook thirdbox 'set from="[EMAIL PROTECTED]" realname="BlaBla"' > > folder-hook fourthbox 'set from="[EMAIL PROTECTED]" realname="Blabla"' > > > > Now, when I go into the mail folder secondbox, thirdbox or fourthbox, > > everything is alright and I get the right address in "From:"-header, > > regardless whether I send new emails or reply. But in the firstbox (which > > should be my default) I always get the email-address from the secondbox in > > the > > From-header, even if I change the period in the first folder-hook to the > > name of the first (default) box. What am I doing > > wrong? > > Do you happen to be using nested maildir folders? I'm wondering if > maybe you need to specify the full pathname, or use $ at the end of the > folder regular expression. > > me
Re: How to get default "From:" to work
On Sun, Nov 23, 2008 at 08:02:34PM +0100, Szymek wrote: > No, the maildir folders are not nested, here is the structure: > > ~/mail-> > ->firstbox > ->secondbox > ->thirdbox > ->fourthbox > > I compiled mutt by myself, maybe there is a specific option to pass to > configure? > > I had previously the same config in Slackware, and it worked like a charm. > > > > > On Sat, Nov 22, 2008 at 09:48:03AM -0800, Michael Elkins wrote: > > On Sat, Nov 22, 2008 at 04:31:57PM +0100, [EMAIL PROTECTED] wrote: > > > folder-hook . 'set from="[EMAIL PROTECTED]" realname="Blabla"' > > > folder-hook secondbox 'set from="[EMAIL PROTECTED]" > > > realname="BlaBla"' > > > folder-hook thirdbox 'set from="[EMAIL PROTECTED]" realname="BlaBla"' > > > folder-hook fourthbox 'set from="[EMAIL PROTECTED]" > > > realname="Blabla"' > > > > > > Now, when I go into the mail folder secondbox, thirdbox or fourthbox, > > > everything is alright and I get the right address in "From:"-header, > > > regardless whether I send new emails or reply. But in the firstbox (which > > > should be my default) I always get the email-address from the secondbox > > > in the > > > From-header, even if I change the period in the first folder-hook to the > > > name of the first (default) box. What am I doing > > > wrong? > > > > Do you happen to be using nested maildir folders? I'm wondering if > > maybe you need to specify the full pathname, or use $ at the end of the > > folder regular expression. > > > > me Yes, now it works. I did append an $ to the end of the folder names, like that: folder-hook secondbox$ 'set from="[EMAIL PROTECTED]" realname="BlaBla"' I didn't wrote the dollar sign for the default, period marked mailbox. Now everything works fine. Thanks a lot for your help. One more thin, can you tell me, why it is working, now that I have the dollar sign appended?
Re: How to get default "From:" to work
On Tue, Nov 25, 2008 at 08:32:37AM -0800, Michael Elkins wrote: > On Tue, Nov 25, 2008 at 12:21:05PM +0100, Szymek wrote: > > Yes, now it works. I did append an $ to the end of the folder names, like > > that: > > > > folder-hook secondbox$ 'set from="[EMAIL PROTECTED]" realname="BlaBla"' > > > > I didn't wrote the dollar sign for the default, period marked mailbox. Now > > everything works fine. Thanks a lot for your help. One more thin, can you > > tell > > me, why it is working, now that I have the dollar sign appended? > > Suppose you have the following set of mailboxes in ~/Mail: > > foobar > foo > bar > > and the following folder-hooks: > > folder-hook foobar '...' > folder-hook foo '...' > folder-hook bar '... > > The second folder hook will match both foo and foobar. In order to > prevent this match, you need to use an anchor ($) in the regular > expression to match the end of the word right after foo: > > folder-hook foo$ '...' > > me > Now I understand. So, I need to specify the exact name of the box. I could give an absolute path to the mailbox instead, /home/szymon/mail/firstbox, for example... Thanks a lot!
Header caching not working
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
Re: Header caching not working
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
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
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
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
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
