Re: mutt and plaintext passwords : muttrc encryption ?

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday, July 28 at 10:13 PM, quoth Michele Martone:
>ehm. one more thing.
>how would you deal with the MTA with the wrapper-based solution ?

Personally? I'd compile mutt with smtp support and be done with it.

>i know only of :
>
>using nbsmtp, in a dangerous way:
>set sendmail="nbsmtp -P password ..."
>
>using ssmtp , in a dangerous way:
>set sendmail="ssmtp -ap password ..."

Well, yes, those are the most obvious.

If you're game for a temp file, you could use gpg (with gpg-agent) to 
quickly decrypt a version of their config file for use, and then 
delete it... but that'll require an MTA wrapper too (this is as 
complex and undesirable a solution as they get, eh?). For example:

 #!/bin/sh
 gpg --decrypt ~/.msmtprc.gpg -o ~/.msmtprc
 msmtp "$@"
 retval=$?
 rm ~/.msmtprc
 exit $retval

Nothing else leaps to mind.

~Kyle
- -- 
I know God will not give me anything I can't handle. I just wish that 
He didn't trust me so much.
  -- Mother Theresa
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkiOOpoACgkQBkIOoMqOI17/ZQCeJGqFahZMeg0U1KrYHvUiZUxx
3JkAoMRLeUHAOiPoVdyMxrvDi7b7edkf
=a0aJ
-END PGP SIGNATURE-

Re: mutt and plaintext passwords : muttrc encryption ?

[Michael Kjorling]

On 28 Jul 2008 21:53 +0100, by [EMAIL PROTECTED] (Michele Martone):
> still I can't stand the need of a wrapper.. if only one could use
> multi line shell expansion, and place that `gpg --decrypt` straight into
> the muttrc.

I haven't tried it, but I can't get it out of my head... wouldn't
sourcing through a pipe something that sets the sensitive stuff work?

Something like this:

source "gpg -d sensitivestuff.gpg |"

and sensitivestuff being just another muttrc snippet.

It would only execute the pipe once, so you avoid the problem of
needing to type your passphrase multiple times, and it *should* not
write anything to disk in plain text.

Since nobody has suggested this approach - what is wrong with it?

-- 
Michael Kjörling .. [EMAIL PROTECTED] .. http://michael.kjorling.se
* . No bird soars too high if he soars with his own wings . *
* ENCRYPTED email preferred -- OpenPGP key ID: 0x 758F8749 BDE9ADA6 *
* ASCII Ribbon Campaign: Against HTML mail, proprietary attachments *



signature.asc
Description: Digital signature

Re: mutt and plaintext passwords : muttrc encryption ?

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday, July 28 at 09:53 PM, quoth Michele Martone:
> this seems almost perfect to me. marvelous, elegant, general, thanks ! 
> (so i do not dare to quote a piece of your email ..)

Happy to help!

> still I can't stand the need of a wrapper.. if only one could use 
> multi line shell expansion, and place that `gpg --decrypt` straight 
> into the muttrc.

Well, I thought about that. We can solve it, but there are drawbacks 
(such as needing other software, or using a temporary file).

For example, if you use gpg-agent to store your passphrase, then you 
can encrypt each password as its own file:

 echo password | gpg --encrypt -o ~/.acct1_pass
 echo password2 | gpg --encrypt -o ~/.acct2_pass

Then put this into your muttrc:

 set my_acct1_pass=`gpg --decrypt ~/.acct1_pass`
 set my_acct2_pass=`gpg --decrypt ~/.acct2_pass`

 account-hook account2 'set imap_pass=$my_acct2_pass'

The key to making that convenient, though, is using gpg-agent to store 
your passphrase (so you don't have to enter it multiple times). 

If mutt could pass $my_* variables into shell escapes (or could 
directly manipulate its own variables the way that bash can (e.g. 
${my_acctpwds#*:})), then you could try using a separator character in 
your passwords (such as a colon) and then figure them out within the 
muttrc. For example, you could create the encrypted file like so:

 echo password1:password2 | gpg --encrypt -o ~/.acctpwds

Then put this in your muttrc:

 set my_acctpwds=`gpg --decrypt ~/.acctpwds`
 set my_acct1_pass=`echo $my_acctpwds | cut -d: -f1`
 set my_acct2_pass=`echo $my_acctpwds | cut -d: -f2`

But, of course, since you can't do that... c'est la vie. :)

Now, it's also possible to use a temporary file to do this:

 set my_acctpwds=`gpg --decrypt ~/.acctpwds > ~/tmp/acctpwds`
 set my_acct1_pass=`cut -d: -f1 ~/tmp/acctpwds`
 set my_acct2_pass=`cut -d: -f2 ~/tmp/acctpwds ; rm ~/tmp/acctpwds`

But that's obviously suboptimal if you're trying to avoid ever having 
that stuff on disk in plain text. It may be more acceptable if you 
have a memory-only filesystem somewhere (such as tempfs on Linux), but 
we're getting into the realm of specialized software again.

~Kyle
- -- 
I am ready to meet my Maker. Whether my Maker is ready for the great 
ordeal of meeting me is another matter.
   -- Winston Churchill
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkiOOPYACgkQBkIOoMqOI17KYwCeKXdZMcTLvL/yDoLib7TrQXR9
BasAoJxchtRVq0yZfSs77uX5nUMRYk1v
=EBqZ
-END PGP SIGNATURE-

Re: mutt and plaintext passwords : muttrc encryption ?

[Michele Martone]

ehm. one more thing.
how would you deal with the MTA with the wrapper-based solution ?

i know only of :

using nbsmtp, in a dangerous way:
set sendmail="nbsmtp -P password ..."

using ssmtp , in a dangerous way:
set sendmail="ssmtp -ap password ..."

or using msmtp with 'password' fields unset in the .msmtprc file,
waiting for prompting (never worked to me though)

On [EMAIL PROTECTED]:53, Michele Martone wrote:
> this seems almost perfect to me. marvelous, elegant, general, thanks !
> ..

Re: mutt and plaintext passwords : muttrc encryption ?

[Michele Martone]

this seems almost perfect to me. marvelous, elegant, general, thanks !
(so i do not dare to quote a piece of your email ..)

and is immensely less overkill than the solution I proposed.

still I can't stand the need of a wrapper.. if only one could use
multi line shell expansion, and place that `gpg --decrypt` straight into
the muttrc.

but Gandalf's advice is appropriated - this is enough for now :)

On [EMAIL PROTECTED]:58, Kyle Wheeler wrote:
> On Monday, July 28 at 05:12 PM, quoth Michele Martone:
> > I was wondering about some way to protect the passwords potentially 
> > stored in the mutt rc files (i have multiple acccounts, and I feel 
> > unconfortable remembering and typing all of them each time using 
> > mutt) on my Linux laptop.
> 
> The obvious answer is: don't store them in the mutt rc files. Instead, 
> store them somewhere in encrypted form and extract them when mutt is 
> loaded. For example:
> 
> set imap_pass=`getpassword [EMAIL PROTECTED]
> 
> Programs that can be used to do this include pwsafe 
> (http://nsd.dyndns.org/pwsafe/) and passwords 
> (http://passwords.sourceforge.net/).
> 
> But you can do it even more simply than that! For example, you can use  
> gpg to encrypt a file that looks like this:
> 
>  export ACCT1_PASS=thepassword
>  export ACCT2_PASS=theotherpassword
>  export ACCT3_PASS=yetanotherpassword
> 
> Then, once you've encrypted it, you can create a wrapper command for 
> mutt that will decrypt it and use it to put those passwords into 
> mutt's environment:
> 
>  #!/bin/sh
>  pwds=`gpg --decrypt ~/.passwords`
>  eval "$pwds"
>  exec mutt "$@"
> 
> And finally, in your muttrc, you can simply have things like this:
> 
>  set imap_pass=$ACCT1_PASS
> 
> or:
> 
>  account-hook account2 'set imap_pass=$ACCT2_PASS'
> 
> Thus, you will be prompted once for a passphrase when mutt loads, and 
> after that mutt will use those passwords as it needs them without 
> additional overhead. Nothing will be stored in plaintext on disk, your 
> encryption is guaranteed to be world-class, and best of all: it will 
> work on virtually any Unix machine.
> 
> > But how about storing a whole encrypted muttrc file and letting mutt 
> > to decrypt it with some passphrase ?
> 
> That seems like overkill to me.
> 
> ~Kyle
> -- 
> All we have to decide is what to do with the time that is given us.
> -- Gandalf the Grey

Re: mutt and plaintext passwords : muttrc encryption ?

[Michele Martone]

On [EMAIL PROTECTED]:35, Justin Mazzola Paluska wrote:
> ...
> 2.  On my home machine, I use GPG to decrypt the password part of the
>     muttrc.

uhm. could you give some examples for this solution ?

it seems to require no external workarounds at all, so it seems neat!

i experimented with 

`gpg -d muttrc.gpg`

inside a muttrc file, but I noticed only the first line of 
`gpg -d muttrc.gpg` gets interpreted by mutt; the other lines are
discarded.

Re: mutt and plaintext passwords : muttrc encryption ?

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday, July 28 at 05:12 PM, quoth Michele Martone:
> I was wondering about some way to protect the passwords potentially 
> stored in the mutt rc files (i have multiple acccounts, and I feel 
> unconfortable remembering and typing all of them each time using 
> mutt) on my Linux laptop.

The obvious answer is: don't store them in the mutt rc files. Instead, 
store them somewhere in encrypted form and extract them when mutt is 
loaded. For example:

set imap_pass=`getpassword [EMAIL PROTECTED]

Programs that can be used to do this include pwsafe 
(http://nsd.dyndns.org/pwsafe/) and passwords 
(http://passwords.sourceforge.net/).

But you can do it even more simply than that! For example, you can use  
gpg to encrypt a file that looks like this:

 export ACCT1_PASS=thepassword
 export ACCT2_PASS=theotherpassword
 export ACCT3_PASS=yetanotherpassword

Then, once you've encrypted it, you can create a wrapper command for 
mutt that will decrypt it and use it to put those passwords into 
mutt's environment:

 #!/bin/sh
 pwds=`gpg --decrypt ~/.passwords`
 eval "$pwds"
 exec mutt "$@"

And finally, in your muttrc, you can simply have things like this:

 set imap_pass=$ACCT1_PASS

or:

 account-hook account2 'set imap_pass=$ACCT2_PASS'

Thus, you will be prompted once for a passphrase when mutt loads, and 
after that mutt will use those passwords as it needs them without 
additional overhead. Nothing will be stored in plaintext on disk, your 
encryption is guaranteed to be world-class, and best of all: it will 
work on virtually any Unix machine.

> But how about storing a whole encrypted muttrc file and letting mutt 
> to decrypt it with some passphrase ?

That seems like overkill to me.

~Kyle
- -- 
All we have to decide is what to do with the time that is given us.
-- Gandalf the Grey
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkiOCKgACgkQBkIOoMqOI14JMACgvaPBdVSUqbnPjYXpz21FrlvM
K98An2uqhZ3eZ0o4FTZfwoduMLuvEZ9B
=TVF/
-END PGP SIGNATURE-

Re: mutt and plaintext passwords : muttrc encryption ?

[Justin Mazzola Paluska]

On Mon, Jul 28, 2008 at 05:12:50PM +0100, Michele Martone wrote:
> Has anybody thought or heard of a solution like this, or similar ?

I have two solutions that I’m using (on two different machines):

1.  On my work GNOME machine, I have some python scripts that query
the GNOME Keyring for my passwords.

2.  On my home machine, I use GPG to decrypt the password part of the
    muttrc.

In both cases, my .mutt/muttrc is in plaintext, which sources the
output of either the GNOME Keyring script or the GPG script.
—Justin

mutt and plaintext passwords : muttrc encryption ?

[Michele Martone]

Hello.
I was wondering about some way to protect the passwords potentially 
stored in the mutt rc files (i have multiple acccounts, and I feel
unconfortable remembering and typing all of them each time using
mutt) on my Linux laptop.

My main concern is about them being stored in plaintext, which is a
little dangerous when using a laptop and traveling: there is  identity
theft potential.

A widely solution would be to encrypt the filesystem on which the
configuration files reside.
This, however is IMHO a little oversized solution in the case the main
privacy concern, like in my case, is about a bunch of text files.

So lately I'm experimenting a more gentle approach, namely using a
file (stored in my home directory) encrypted with LUKS, containing a
directory containing the important data (a passwords-only .muttrc, a
.msmtprc, a .fetchmailrc, and an .isyncrc).

Setting some sudo stuff, and configuring my bash aliases, I get this 
mini-filesystem mounted with ease - namely obtaining a 'lightweight
personal solution' for mail passwords protection.


But how about storing a whole encrypted muttrc file and letting mutt 
to decrypt it with some passphrase ?

Say, using the vim encryption algorithm (the one you trigger when 
saving a file with :X in the vim inner commandline), one would get a
quite simple and lightweight security measure, without the need of
filesystem messing and getting a 'natural' way of editing the muttrc.
I reported the Vim encryption solution because it sounds 'simple' and
'natural' to me, (and Vim encrypted files can be 'recognized' by 
having a "VimCrypt" signature in the first bytes)
But I know, vim is not the only text editor around here :) .

Has anybody thought or heard of a solution like this, or similar ?

--
Michele Martone
http://claudius.ce.uniroma2.it/~martone

Re: .muttrc

[Ravi Uday]

Rocco,

In that link I didn't find a way to add this request.. If anyone can
add the care ticket request that would be great !

Thanks,
Ravi

On Fri, Jul 25, 2008 at 8:36 AM, Rocco Rutte <[EMAIL PROTECTED]> wrote:
> Hi,
>
> * Michelle Konzack wrote:
>
>> I wish, there was a function which dump the actuell running config...
>
> Please add this wish to http://dev.mutt.org/trac/ticket/3064. Maybe it'll be
> easy to implement another command such as "save" that will print the
> contents to a file rather then a paged menu.
>
> Rocco
>

Re: .muttrc

[Sertaç Ö . Yıldız]

* Ravi Uday [22.Tem.08 11:31 -0700]:
> If there is a way to retrieve your ~/.muttrc from a existing mutt
> session, please let me know. That would help too as my
> .muttrc is deleted :(

Attach gdb to your mutt process with:

gdb /proc/$PPID/exe $PPID

And inside gdb dump the variables like so:

call mutt_dump_variables()

Then parse the output.

-- 
~sertac

Re: .muttrc

[Rocco Rutte]

Hi,

* Michelle Konzack wrote:


I wish, there was a function which dump the actuell running config...


Please add this wish to http://dev.mutt.org/trac/ticket/3064. Maybe 
it'll be easy to implement another command such as "save" that will 
print the contents to a file rather then a paged menu.


Rocco

Re: .muttrc

[Michelle Konzack]

Am 2008-07-22 11:31:28, schrieb Ravi Uday:
> Just to add to this,
> 
> If there is a way to retrieve your ~/.muttrc from a existing mutt
> session, please let me know. That would help too as my
> .muttrc is deleted :(

I wish, there was a function which dump the actuell running config...

Thanks, Greetings and nice Day/Evening
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
+49/177/935194750, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

.muttrc

[Ravi Uday]

Hi folks,

I screwed up my .muttrc and its lost..
I had the file at  ~/.muttrc

I did a mv ~/ ~/.muttrc

instead of

mv ~/ ~/.mutt/

and now its gone.. :(
Is there a way to retrieve my ~/.muttrc back on Sun ?

Thanks in advance,
Ravi

Re: .muttrc

[Ravi Uday]

Just to add to this,

If there is a way to retrieve your ~/.muttrc from a existing mutt
session, please let me know. That would help too as my
.muttrc is deleted :(

TIA,
Ravi

On Tue, Jul 22, 2008 at 11:23 AM, Ravi Uday <[EMAIL PROTECTED]> wrote:
> Hi folks,
>
> I screwed up my .muttrc and its lost..
> I had the file at  ~/.muttrc
>
> I did a mv ~/ ~/.muttrc
>
> instead of
>
> mv ~/ ~/.mutt/
>
> and now its gone.. :(
> Is there a way to retrieve my ~/.muttrc back on Sun ?
>
> Thanks in advance,
> Ravi
>

Re: ":source ~/.muttrc" command weirdly moves message around in

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Friday, June 20 at 01:19 AM, quoth Russell Hoover:
> I've never actually once ever had any matching I didn't want on
>
> <|cv|dm
>
> in the line
>
> folder-hook   '<|cv|dm''set index_format="%3C %Z %[%m/%d]  %-22.22F \ 
> %?l?%4l&%4c?   %s"'
>
> The "cv" and "dm" folders don't ever get mail sent directly to them.

Well, that's beside the point. The reason you haven't had any false 
positive matches is that none of your other folders have the strings 
cv or dm in their title. And if you can be assured that you never 
will, then it doesn't matter.

Of course, a false-positive match will only manifest itself as a 
slightly incorrect index_format; hardly a serious problem, of course.

~Kyle
- -- 
Nonsense. Space is blue and birds fly through it.
  -- Heisenberg
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhbuD0ACgkQBkIOoMqOI14rYwCfbrit6d8PVi+DNFY4g1UQ5s6w
kpUAnjGGaZsU/7KNAsZblUCOcDqjf/WN
=mNxB
-END PGP SIGNATURE-

Re: ":source ~/.muttrc" command weirdly moves message around in

[Russell Hoover]

On Tue 06/17/08 at 02:30 AM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote:

> Use whatever works for you; I just recommend using a tighter pattern
> when possible. Your original pattern of just two lowercase letters
> seems to be just begging to match things you don't intend.


I've never actually once ever had any matching I didn't want on

 <|cv|dm

in the line

folder-hook   '<|cv|dm''set index_format="%3C %Z %[%m/%d]  %-22.22F \
%?l?%4l&%4c?   %s"'

The "cv" and "dm" folders don't ever get mail sent directly to them.  The
only way any messages ever get into them is when I save them to there from
my inbox, and messages I *send* to the persons (whose initials those are)
get saved to there instead of to my "sent-mail" folder.

Given that, do I still need to be concerned about false matches?  I would
think there's nothing that could ever get erroneously matched to them.

-- 
 // [EMAIL PROTECTED] //
It is only when we step away from the actual and begin
 to explore the possible that life's infinities begin
to reveal themselves to us.  -- James Kent


pgpEyfqITIGpX.pgp
Description: PGP signature

Re: ":source ~/.muttrc" command weirdly moves message around in

[Rocco Rutte]

Hi,

* Kyle Wheeler wrote:

On Tuesday, June 17 at 02:48 AM, quoth Russell Hoover:

I originally had this:



   <|cv|dm



and you suggested this:



   '(<|=cv|=dm)$'



but the only two things that works are these:



   <|cv|dm   and   '<|cv|dm'



No other combination lets it read the%cto the right of the line.


Hm. I just tested it. It seems like mutt doesn't want to do more than 
one shortcut substitution per pattern (I haven't checked the source to 
double-check, but that's how it seems to behave). I learned something 
new about mutt! Thanks!


When expanding paths, mutt looks at the first character for a shortcut 
only, much like ~-expansion in the shell. That means that


  <|cv|dm

will be expanded to

  foobar|cv|dm

before being compiled as a regex. In

  (<|=cv|=dm)$

there won't be any expansion at all since '(' isn't special at all. To 
match mailboxes 'foo' and 'bar' below $folder, something like this could 
work:


  =(foo|bar)

Rocco

Re: ":source ~/.muttrc" command weirdly moves message around in

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday, June 17 at 02:48 AM, quoth Russell Hoover:
> I originally had this:
>
><|cv|dm
>
> and you suggested this:
>
>'(<|=cv|=dm)$'
>
> but the only two things that works are these:
>
><|cv|dm   and   '<|cv|dm'
>
> No other combination lets it read the%cto the right of the line.

Hm. I just tested it. It seems like mutt doesn't want to do more than 
one shortcut substitution per pattern (I haven't checked the source to 
double-check, but that's how it seems to behave). I learned something 
new about mutt! Thanks!

I still think you should make your patterns a little tighter, but 
making them bulletproof won't be as elegant looking.

Adding the $ to the end will tighten the pattern without hurting:

 '(<|cv|dm)$'

It's not bulletproof, but that will prevent a lot of false-positives. 
Another thing you can do is add a separator matcher, so that you can 
make sure you only match folders of that name, like so:

 '(<|[./]cv|[./]dm)$'

And that should work pretty well also. Finally, for something *really* 
bulletproof, but much more ugly, you can use $folder directly (rather 
than the shortcut), because mutt substitutes variables as often as 
necessary, unlike (apparently) shortcuts. Also, you'd have to use 
double-quotes, to get mutt to do the right substitution. So, something 
like this:

 "(<|$folder[./]cv|$folder[./]dm)$"

Use whatever works for you; I just recommend using a tighter pattern 
when possible. Your original pattern of just two lowercase letters 
seems to be just begging to match things you don't intend.

~Kyle
- -- 
The purpose of computing is insight, not numbers.
  -- Richard W. Hamming
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhXaAUACgkQBkIOoMqOI17L9QCguwQjBsTDV09W1DCeutzp+MS/
GJ8An2st6P8z1WG+oTpH5G3pS6MrhOli
=Cshb
-END PGP SIGNATURE-

Re: ":source ~/.muttrc" command weirdly moves message around in

[Russell Hoover]

On Mon 06/16/08 at 09:38 PM +0200,
Christian Brabandt <[EMAIL PROTECTED]> wrote:

> Have you tried something like the following format: (%?l?%4l&%4c?)

> This will display the line number if available otherwise it will print
> the byte size.

This is perfect.  It's amazing how mutt has a solution for almost
everything if you're persistent with what can sometimes seem like
its formidable setup complexities.

-- 
 // [EMAIL PROTECTED] //

Re: ":source ~/.muttrc" command weirdly moves message around in

[Russell Hoover]

On Mon 06/16/08 at 02:30 PM -0500,
Kyle Wheeler <[EMAIL PROTECTED]> wrote:

> Hmmm... so it's not matching? Interesting. Try deconstructing it, to
> see what's breaking the match. For example, remove the $ off the end,
> and see if that helps.

I originally had this:

<|cv|dm

and you suggested this:

'(<|=cv|=dm)$'

but the only two things that works are these:

<|cv|dm   and   '<|cv|dm'

No other combination lets it read the%cto the right of the line.

So for now, at least, I'm using the quoted version, with the notation
Christian suggested for line numbers / byte size.

-- 
 // [EMAIL PROTECTED] //



pgphNglQFKsjb.pgp
Description: PGP signature

Re: ":source ~/.muttrc" command weirdly moves message around in

[Christian Brabandt]

Hi Russell!

On Mon, 16 Jun 2008, Russell Hoover wrote:

> How can I keep the form you've suggested and also get the results of 
> %c instead of %3l ?

Have you tried something like the following format: (%?l?%4l&%4c?)

This will display the line number if available otherwise it will print 
the byte size.


regards,
Christian

Re: ":source ~/.muttrc" command weirdly moves message around in

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday, June 16 at 03:15 PM, quoth Russell Hoover:
>On Sun 06/15/08 at 09:40 PM -0500,
>Kyle Wheeler <[EMAIL PROTECTED]> wrote:
>
>> [...] that you use something more like this:
>>  folder-hook '(<|=cv|=dm)$' 'set index_format="whatever"'
>
>
>The only problem I'm having with this:
>
>   '(<|=cv|=dm)$'

Hmmm... so it's not matching? Interesting. Try deconstructing it, to 
see what's breaking the match. For example, remove the $ off the end, 
and see if that helps.

~Kyle
- -- 
Only a mediocre person is always at his best.
-- Somerset Maugham
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhWv0YACgkQBkIOoMqOI15IiACgrdR/NPO+dCqt3Ip3ZAQuYbZG
DYAAnjJ7fIWPC4PFwVF1WWbqsuCKgBsV
=fS6x
-END PGP SIGNATURE-

Re: ":source ~/.muttrc" command weirdly moves message around in

[Russell Hoover]

On Sun 06/15/08 at 09:40 PM -0500,
Kyle Wheeler <[EMAIL PROTECTED]> wrote:

> [...] that you use something more like this:
>  folder-hook '(<|=cv|=dm)$' 'set index_format="whatever"'


The only problem I'm having with this:

'(<|=cv|=dm)$'

instead of this:

'<|cv|dm'

in this:

folder-hook '(<|=cv|=dm)$'  'set index_format="%3C %Z %[%m/%d] %-22.22F %c %s"'

is that with

'(<|=cv|=dm)$'

these three folders don't show, in their index, the result of %c above,
but rather the result of %3l in the following line (which is a few lines
above in my.muttrc):

folder-hook .  'set index_format="%3C %Z %[%m/%d]  %-20.20n  %3l   %s"'

And that of course gives me an index-view that shows the number of lines in
the message (some of which are "0" since I use maildirs)  instead of the
message's size in bytes.

How can I keep the form you've suggested and also get the results of %c
instead of %3l ?

-- 
 // [EMAIL PROTECTED] //
 To do:  1) Get VIM for Linux.  2) Get VIM for NetBSD
   3) Get VIM for Solaris.  4) Get VIM for the Mac.
 5) Get VIM for Windows.  6) Laugh at non-VIM users.


pgp1sDjbhVyNG.pgp
Description: PGP signature

Re: ":source ~/.muttrc" command weirdly moves message around in

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sunday, June 15 at 11:29 PM, quoth Russell Hoover:
>On Sun 06/15/08 at 11:15 PM -0400, Russell Hoover <[EMAIL PROTECTED]> wrote:
>
>> Absolutely.  Though I'm partial to the plus-sign, so I used that
>> instead of "=".
>
>> folder-hook   '(<|+cv|+dm)$''set index_format="whatever"'
>^   ^
>
>Looks like I'm better off with the equal-sign (instead of those
>pluses) after all.  The pluses caused a "repetition-operator
>operand invalid" error message.

;)

Remember, you're dealing with a regular expression here, not just a 
folder name - the plus-sign has significance to regular expressions. I 
haven't checked the dev archives, but I'd wager a pretty strong guess 
that that's the reason that mutt provides both symbols as a shortcut 
for $folder, while most other shortcut characters don't have 
alternates.

~Kyle
- -- 
Computers are useless. They can only give you answers.
   -- Pablo Picasso
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhV38AACgkQBkIOoMqOI17lNQCePMkOaha4M+HD3uakOKQoFcap
jmwAn1CYL9LUOzG7oor0WbnGIfTirHvq
=KlYY
-END PGP SIGNATURE-

Re: ":source ~/.muttrc" command weirdly moves message around in

[Russell Hoover]

On Sun 06/15/08 at 11:15 PM -0400, Russell Hoover <[EMAIL PROTECTED]> wrote:

> Absolutely.  Though I'm partial to the plus-sign, so I used that
> instead of "=".

> folder-hook   '(<|+cv|+dm)$''set index_format="whatever"'
^   ^

Looks like I'm better off with the equal-sign (instead of those
pluses) after all.  The pluses caused a "repetition-operator
operand invalid" error message.

-- 
 // [EMAIL PROTECTED] //



pgpAVsAMeb348.pgp
Description: PGP signature

Re: ":source ~/.muttrc" command weirdly moves message around in

[Russell Hoover]

On Sun 06/15/08 at 09:40 PM -0500,
Kyle Wheeler <[EMAIL PROTECTED]> wrote:

> [...] that "sent" string in the original pattern will also match folders
> named "abSENT" and "SENTimental" and "esSENTial". So it was entirely
> possible that the "sent" string was not redundant, and was actually
> intentional.

Ah.  Definitely.  What you're talking about is finally sinking in.

> >if I want the three folders, "<" "cv" and "dv", all to have
> >the same index format, yes?

> That's still a bad regular expression for that purpose, because it's
> still excessively general. It will match against things like
> "advocacy" and "inadvertent" and "advisor".

Damn.  Of course.

> I suggest, at the very least, that you use something more like this:

>  folder-hook '(<|=cv|=dm)$' 'set index_format="whatever"'

Absolutely.  Though I'm partial to the plus-sign, so I used that
instead of "=".

folder-hook   '(<|+cv|+dm)$''set index_format="whatever"'

Thanks for the fine-tuning.

-- 
 // [EMAIL PROTECTED] //



pgpwTHsA74SbS.pgp
Description: PGP signature

Re: ":source ~/.muttrc" command weirdly moves message around in

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sunday, June 15 at 09:54 PM, quoth Russell Hoover:
>I mean, what I need is surely this:
>
> folder-hook   <|cv|dm'set index_format="whatever"

Yes, that is more succinct, assuming that the only reason "sent" was 
in there was to match against $record. However, like I said, that 
"sent" string in the original pattern will also match folders named 
"abSENT" and "SENTimental" and "esSENTial". So it was entirely 
possible that the "sent" string was not redundant, and was actually 
intentional.

>if I want the three folders, "<" "cv" and "dv", all to have the same 
>index format, yes?

That's still a bad regular expression for that purpose, because it's 
still excessively general. It will match against things like 
"advocacy" and "inadvertent" and "advisor". I suggest, at the very 
least, that you use something more like this:

 folder-hook '(<|=cv|=dm)$' 'set index_format="whatever"'

...assuming that cv and dm are folders within $folder (which is what = 
means).

~Kyle
- -- 
It has been my experience that folks who have no vices have very few 
virtues.
 -- Abraham Lincoln
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhV0oUACgkQBkIOoMqOI15fAACeJcZckM72SWXw7TTCZIbl3f6c
h5AAoOz2WV+OMfavWvIqC2gEk1YtUo6g
=2cf8
-END PGP SIGNATURE-

Re: ":source ~/.muttrc" command weirdly moves message around in

[Russell Hoover]

On Sun 06/15/08 at 07:22 PM -0500,
Kyle Wheeler <[EMAIL PROTECTED]> wrote:

[that I wrote]
> >folder-hook <|sent|cv|dm|fabio'set index_format= etc
> >   ^^^
> > . . . duplication of sent-folder names.

> Well, not necessarily. Remember, you're providing a *pattern*, so that 
> pattern you have there will match against folders named:
> 
>  sentimental
>  madmen
>  admission
>  windmill
>  grandma
>  Redmond
>  absent
>  essential
> 
> ...and lots more.


Howver, given that I have:

  set  record=+sent

and that I haven't overwritten this in any of the ways it's possible to,
and that the manual states:

 < -- refers to your $record file

wouldn't this mean that "<" indicates my sent-mail folder, and that

   <|sent|etc

(as above) is a duplication of the naming of the sent-mail folder?

I mean, what I need is surely this:

 folder-hook   <|cv|dm'set index_format="whatever"

and not this:

 folder-hook   <|sent|cv|dm   'set index_format="whatever"

if I want the three folders, "<" "cv" and "dv", all to have the same index
format, yes?

-- 
 // [EMAIL PROTECTED] //



pgpgvbLUm1GRR.pgp
Description: PGP signature

Re: ":source ~/.muttrc" command weirdly moves message around in

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sunday, June 15 at 08:11 PM, quoth Russell Hoover:
>On Sun 06/15/08 at 02:50 PM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote:
>> Think of it this way:
>>  mutt reads your muttrc (sort=date)
>>  mutt opens your inbox (hook triggered, sort=threads)
>>  you tell mutt to re-read the muttrc (sort=date)
>>  you tell mutt to re-open your inbox (hook triggered, sort=threads)
>
>
>Thanks -- my problem was I'd "set sort=mailbox-order" at some point.
>I restored that to "date-sent" -- that's how I'd always had it before.

Cool - thought so. :)

>Another mistake I had to see up on the list before I could really see 
>it was:
>
>folder-hook <|sent|cv|dm|fabio'set index_format= etc
>   ^^^
> . . . duplication of sent-folder names.

Well, not necessarily. Remember, you're providing a *pattern*, so that 
pattern you have there will match against folders named:

 sentimental
 madmen
 admission
 windmill
 grandma
 Redmond
 absent
 essential

...and lots more.

~Kyle
- -- 
Do what you can, with what you have, where you are.
  -- Theodore Roosevelt
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhVsl8ACgkQBkIOoMqOI1430wCg4BFHQmTupU/uEZfh2VawxfvB
Jk4An283Efy4kzBZf6yl4UtfSJKk0ZtL
=DG76
-END PGP SIGNATURE-

Re: ":source ~/.muttrc" command weirdly moves message around in

[Russell Hoover]

On Sun 06/15/08 at 02:50 PM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote:
> Think of it this way:
>  mutt reads your muttrc (sort=date)
>  mutt opens your inbox (hook triggered, sort=threads)
>  you tell mutt to re-read the muttrc (sort=date)
>  you tell mutt to re-open your inbox (hook triggered, sort=threads)


Thanks -- my problem was I'd "set sort=mailbox-order" at some point.
I restored that to "date-sent" -- that's how I'd always had it before.

Another mistake I had to see up on the list before I could really see it was:

folder-hook <|sent|cv|dm|fabio'set index_format= etc
   ^^^
 . . . duplication of sent-folder names.

-- 
 // [EMAIL PROTECTED] //


pgptIUhgLfH0Y.pgp
Description: PGP signature

Re: ":source ~/.muttrc" command weirdly moves message around in

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sunday, June 15 at 02:45 PM, quoth Russell Hoover:
>On Sun 06/15/08 at 10:39 AM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote:
>
>> Probably a folder-hook that sets your sorting order whenever you enter
>> the INBOX.
>
>Well, I have what's below, but I've these forever:

How long you've had them is beside the point. The point is that folder 
hooks are only triggered when you *ENTER* a directory. So, if you have 
the following in your muttrc:

 set sort=date
 folder-hook . 'set sort=threads'

Then when you view your inbox, it'll be sorted by threads, but if you 
source your muttrc while viewing your inbox, it'll suddenly be sorted 
by date until you re-open your inbox. That's the expected behavior.

Think of it this way:

 mutt reads your muttrc (sort=date)
 mutt opens your inbox (hook triggered, sort=threads)
 you tell mutt to re-read the muttrc (sort=date)
 you tell mutt to re-open your inbox (hook triggered, sort=threads)

~Kyle
- -- 
I have always found that mercy bears richer fruits than strict 
justice.
 -- Abraham Lincoln
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhVco0ACgkQBkIOoMqOI15Z8QCfawy6QvYqUxIid8a7VtSqskB8
xg8AmwTv562gON+a5c0Z2V78tFxVISkP
=wZqC
-END PGP SIGNATURE-

Re: ":source ~/.muttrc" command weirdly moves message around in

[Russell Hoover]

On Sun 06/15/08 at 10:39 AM -0500, Kyle Wheeler <[EMAIL PROTECTED]> wrote:

> Probably a folder-hook that sets your sorting order whenever you enter
> the INBOX.

Well, I have what's below, but I've these forever:

folder-hook   . set sort=threads
folder-hook   .'set index_format="%3C %Z %[%m/%d]   %-20.20n \
%3l   %s"'

# Now handle special mailboxes:

folder-hook  "!"   set sort=date-sent
folder-hook   >set sort=date-received
folder-hook <|sent|cv|dm|fabio'set index_format="%3C %Z %[%m/%d]
%-22.22F   %c   %s"'
folder-hook <|sent|cv|dm|fabio'set pager_format="-%S-  [%C/%m]  %n \
(%c)   %s"'

-- 
 // [EMAIL PROTECTED] //
   My mechanic told me, "I couldn't repair
  your brakes, so I made your horn louder."


pgpZh0gNmwQ6u.pgp
Description: PGP signature

Re: ":source ~/.muttrc" command weirdly moves message around in

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Sunday, June 15 at 01:04 AM, quoth Russell Hoover:
> Suddenly I've discovered that when I try to re-load my .muttrc with the 
> ":source ~/.muttrc" command, the last message in my index (number 920), is 
> re-positioned as number 576. Other messages are also moved around.

Sounds like it's changing your sorting order.

> If I change folders out of the inbox and then back into it, the 
> message-order is restored to normal.  What could be causing this?

Probably a folder-hook that sets your sorting order whenever you enter 
the INBOX.

~Kyle
- -- 
If you're flammable and have legs, you are never blocking a fire exit. 
Unless you're a table.
   -- Mitch Hedberg
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhVN6EACgkQBkIOoMqOI16wjgCfSfR4Lt6hCM/J/3TesL8fTyiO
uxIAn07s6wx9WvN8IU2OENRHBMuBbivs
=SLqN
-END PGP SIGNATURE-

":source ~/.muttrc" command weirdly moves message around in index

[Russell Hoover]

Suddenly I've discovered that when I try to re-load my .muttrc with the
":source ~/.muttrc" command, the last message in my index (number 920), is
re-positioned as number 576. Other messages are also moved around.

If I change folders out of the inbox and then back into it, the
message-order is restored to normal.  What could be causing this?

-- 
 // [EMAIL PROTECTED] //

Re: folder-hook in my .muttrc doesn't work

[Rudolf Bahr]

* Kyle Wheeler ([EMAIL PROTECTED]) [080602 22:19]:

...
> I would have done something like this:
> 
>  alias -group lisagroup lisa Lisa Lady <[EMAIL PROTECTED]>
>  set use_from=no
>  send-hook '%C lisagroup' 'my_hdr From: [EMAIL PROTECTED]'
>  fcc-save-hook '%C lisagroup' +fanciulla/lisa

Hello Kyle,

I think it is a good advice to write an own .muttrc from scratch. 
I will do that around your code suggestion above.

Thank you again!

Rudolf

Re: folder-hook in my .muttrc doesn't work

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday, June  2 at 09:39 PM, quoth Rudolf Bahr:
>> On Monday, June  2 at 12:29 PM, quoth Rudolf Bahr:
>>> folder-hook +fanciulla/lisa   'set use_from=no'
>>> folder-hook +fanciulla/lisa   'unmy_hdr *'
>>> folder-hook +fanciulla/lisa   'my_hdr From: [EMAIL PROTECTED]'
>> Those three should work fine.
> Sorry, they don't, in this case, at least. The From: address is 
> still a combination of my username and PC's hostname.

Hmmm In that case, I'm not sure. Let's try something different to 
see if this works (all one line, of course):

 send-hook '~C [EMAIL PROTECTED]' 'my_hdr From:
 [EMAIL PROTECTED]'

>>  folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'
>
>
> Ok, I removed the folder-hooks which can't be preset by me and are 
> indeed unnecessary. Instead I added as you suggested:
>
> folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'
>
> But Mutt gives me still back: '[EMAIL PROTECTED]' instead of 
> '=fanciulla/lisa'.

Very interesting. That's not a typical mutt-default Fcc, so I suspect 
you have other hooks in your configuration that are re-setting it... 
particularly fcc-hooks or fcc-save-hooks.

>> *answer* email (r), as opposed to compose new email (m)? If you're 
>> *replying* to email (r), then the recipient (To:) is set based on 
>> the message you're replying to.
>> 
>> What exactly are you trying to achieve?
>
> I'm entering the folder 'fanciulla/lisa' in order to answer a message 
> there by 'r' or ',a'.

Well, I guess my point is... I generally prefer using send-hooks (or 
reply-hooks) instead of folder-hooks for changing these sorts of 
settings, because they allow me to have the message anywhere, and get 
triggered for every message (thus, they over-rule folder-hooks). 
Often, the only reason people choose to use folder-hooks is because 
they haven't yet discovered send-hooks. On the other hand, some people 
strongly associate a given folder with a given role, and associating 
folder with sending address (for example) makes more sense in their 
head.

I would have done something like this:

 alias -group lisagroup lisa Lisa Lady <[EMAIL PROTECTED]>
 set use_from=no
 send-hook '%C lisagroup' 'my_hdr From: [EMAIL PROTECTED]'
 fcc-save-hook '%C lisagroup' +fanciulla/lisa
 # Reply-To isn't usually useful

Note that the send-hook and fcc-save-hook trigger whenever I send a 
message to lisa regardless of what folder I'm in. The $use_from 
setting stays the same always, unless I add hooks to change it (in 
which case it'll have to go into a hook as well). The use of a group 
means I can later add addresses for lisa (e.g. 'group -group lisagroup 
- -addr [EMAIL PROTECTED]') and not have to change my hooks.

Without the "group" bit, that would be rewritten as:

 alias lisa Lisa Lady <[EMAIL PROTECTED]>
 set use_from=no
 send-hook '~C [EMAIL PROTECTED]' 'my_hdr From:
 [EMAIL PROTECTED]'
 fcc-save-hook '~C [EMAIL PROTECTED]' +fanciulla/lisa
 # Reply-To isn't usually useful

>> Keep in mind, these hooks are only triggered when you enter the 
>> folder. If you have other hooks that override them (such as 
>> send-hooks or reply-hooks or message-hooks), they will not be 
>> re-triggered until you re-enter the folder.
>
> Yes, therefore I commented all other lines which have something to 
> do with 'lisa' or '=fanciulla/lisa'. It seems to help nothing.

Depending on your configuration, you may have plenty of "default" 
hooks that don't contain the text "lisa", but apply anyway. For 
example the patterns "~A" and "." in send/reply/message/display-hooks 
will match your emails... there may be lots more hooks being triggered 
than you're aware of. I'd start by following the debug steps outlined 
here: http://wiki.mutt.org/?DebugConfig

This is why I usually recommend that, once you start getting serious 
about configuring your own mutt, you start your own muttrc from 
scratch. It'll take some time to read the descriptions of all the 
relevant settings, but it's *well* worth your time.

> Kyle, many thanks for your answer with the explanations!

Happy to help!

~Kyle
- -- 
If we knew what it was we were doing, it would not be called research, 
would it?
   -- Albert Einstein, 1941
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhEU64ACgkQBkIOoMqOI172lQCcDYXz+ht0y1WnmxgK4UYQQ2zb
KJUAoPlsoVLonvGYQ0Ifi5pXd4tBZTYR
=Z/PN
-END PGP SIGNATURE-

Re: folder-hook in my .muttrc doesn't work

[Rudolf Bahr]

* Kyle Wheeler ([EMAIL PROTECTED]) [080602 16:19]:

Hello Kyle,

> On Monday, June  2 at 12:29 PM, quoth Rudolf Bahr:
> >folder-hook +fanciulla/lisa   'set use_from=no'
> >folder-hook +fanciulla/lisa   'unmy_hdr *'
> >folder-hook +fanciulla/lisa   'my_hdr From: [EMAIL PROTECTED]'
> 
> Those three should work fine.
> 

Sorry, they don't, in this case, at least. The From: address is still a 
combination 
of my username and PC's hostname. 


> >folder-hook +fanciulla/lisa   'my_hdr   To: [EMAIL PROTECTED]'
> >folder-hook +fanciulla/lisa   'my_hdr  Fcc: =fanciulla/lisa'

> Those two won't do anything (well... they will, but not what you 
> expect). First of all, every time you compose a message, mutt asks you 
> who the recipient is. Setting a To: header ahead of time doesn't 
> change that, so whatever To: header you had set before will get 
> overwritten. Secondly, the Fcc: setting isn't a *header*, it's a 
> *setting* (that mutt displays in the compose screen as if it was a 
> header). Here's how you'd do it the "right" way:
> 
>  folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'


Ok, I removed the folder-hooks which can't be preset by me and are 
indeed unnecessary. Instead I added as you suggested:

folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'

But Mutt gives me still back: '[EMAIL PROTECTED]' instead of '=fanciulla/lisa'. 
 
> 
> *answer* email (r), as opposed to compose new email (m)? If you're 
> *replying* to email (r), then the recipient (To:) is set based on the 
> message you're replying to.
> 
> What exactly are you trying to achieve?

I'm entering the folder 'fanciulla/lisa' in order to answer a message
there by 'r' or ',a'.

> 
> Keep in mind, these hooks are only triggered when you enter the 
> folder. If you have other hooks that override them (such as send-hooks 
> or reply-hooks or message-hooks), they will not be re-triggered until 
> you re-enter the folder.
> 

Yes, therefore I commented all other lines which have something to do with 
'lisa'
or '=fanciulla/lisa'. It seems to help nothing.

Any additional ideas?

Kyle, many thanks for your answer with the explanations!

Rudolf

Re: folder-hook in my .muttrc doesn't work

[Rocco Rutte]

Hi,

* Kyle Wheeler wrote:

Secondly, the Fcc: setting isn't a *header*, it's a 
*setting* (that mutt displays in the compose screen as if it was a 
header). Here's how you'd do it the "right" way:



folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'


Yes, this form is better.

But for the record, you can add the "special" Fcc: and Attach: headers 
in the editor for mutt to pick up. It'll then attach all files mentioned 
and set the fcc accordingly (if headers are given).


Users in general should be aware of this because it can be a quite 
dangerous "feature" and easily abused:


  mutt 'mailto:[EMAIL PROTECTED]/.gnupg/secring.gpg'

could send out files you really want to keep private if you don't pay 
enough attention to the compose menu.


Now that I see it, maybe mutt shouldn't allow for Fcc: and Attach: user 
defined headers at all.


Rocco

Re: folder-hook in my .muttrc doesn't work

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Monday, June  2 at 12:29 PM, quoth Rudolf Bahr:
>folder-hook +fanciulla/lisa   'set use_from=no'
>folder-hook +fanciulla/lisa   'unmy_hdr *'
>folder-hook +fanciulla/lisa   'my_hdr From: [EMAIL PROTECTED]'

Those three should work fine.

>folder-hook +fanciulla/lisa   'my_hdr   To: [EMAIL PROTECTED]'
>folder-hook +fanciulla/lisa   'my_hdr  Fcc: 
>=fanciulla/lisa'

Those two won't do anything (well... they will, but not what you 
expect). First of all, every time you compose a message, mutt asks you 
who the recipient is. Setting a To: header ahead of time doesn't 
change that, so whatever To: header you had set before will get 
overwritten. Secondly, the Fcc: setting isn't a *header*, it's a 
*setting* (that mutt displays in the compose screen as if it was a 
header). Here's how you'd do it the "right" way:

 folder-hook +fanciulla/lisa 'set record="=fanciulla/lisa"'

>folder-hook +fanciulla/lisa   'my_hdr Reply-To: 
>[EMAIL PROTECTED]'

That's another one that mutt often generates at compose-time (just 
like the "To:" header) and overwrites any previous settings. For 
example, mutt obeys the environment variable REPLYTO.

> Hopelessly, it doesn't work. if I answer to an e-mail in this 
> folder, I still allways have to correct some of the header fields. 

*answer* email (r), as opposed to compose new email (m)? If you're 
*replying* to email (r), then the recipient (To:) is set based on the 
message you're replying to.

What exactly are you trying to achieve?

Keep in mind, these hooks are only triggered when you enter the 
folder. If you have other hooks that override them (such as send-hooks 
or reply-hooks or message-hooks), they will not be re-triggered until 
you re-enter the folder.

~Kyle
- -- 
Suppose ye that I am come to give peace on earth? I tell you, Nay; but 
rather division: For henceforth there shall be five in one house 
divided, three against two, and two against three. The father shall be 
divided against the son, and the son against the father; the mother 
against the daughter, and the daughter against the mother; the mother 
in law against her daughter in law, and the daughter in law against 
her mother in law.
   -- Prince of Peace, Jesus Christ (Luke 12:51-53)
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iEYEARECAAYFAkhD/lUACgkQBkIOoMqOI15TMQCgg8KKrpfe1srdiQyPGeBMPk4V
f8QAoNG85Z3RNne7p6Mka1aKXQMVlYnj
=T3JL
-END PGP SIGNATURE-

Re: folder-hook in my .muttrc doesn't work

[Rado S]

=- Rudolf Bahr wrote on Mon  2.Jun'08 at 12:29:05 +0200 -=

> Up to now I used a .muttrc-file which I found on the internet and
> it worked rather fine.

Catchup with rtfm then. :)
Once you know what you do, you can analyze what's wrong.
For example you set fcc-hook rather than Fcc: header your way.

For general debugging advice see also the welcome message with links
to the wiki.

-- 
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.

folder-hook in my .muttrc doesn't work

[Rudolf Bahr]

Hello everybody,

it's the first time I'm posting a question here though I used to be a mutt
user for a longer time. As OS I'm using debian, 2.6.24-1-686; my Mutt works in 
mbox_type=Maildir mode and in conjunction with fetchmail, procmail and postfix.

Up to now I used a .muttrc-file which I found on the internet and it worked
rather fine. Now I'd like to intend to have some changes and try the 
configuration 
command "folder-hook" as follows:

folder-hook +fanciulla/lisa   'set use_from=no'
folder-hook +fanciulla/lisa   'unmy_hdr *'
folder-hook +fanciulla/lisa   'my_hdr From: [EMAIL PROTECTED]'
folder-hook +fanciulla/lisa   'my_hdr   To: [EMAIL PROTECTED]'
folder-hook +fanciulla/lisa   'my_hdr  Fcc: =fanciulla/lisa'
folder-hook +fanciulla/lisa   'my_hdr Reply-To: [EMAIL PROTECTED]'

Hopelessly, it doesn't work. if I answer to an e-mail in this folder, I still 
allways 
have to correct some of the header fields. Though I set and unset a lot of 
other 
parameters of which I thought they could have an impact to folder-hook, mutt 
doesn't 
honor any of the desired parameters. 

The only command with a certain influence to the folder-hook command with
respect to the from: header field I found in the manual is the "use_from" 
command:

"When set, Mutt will generate the `From:' header field when sending
messages. If unset, no `From:' header field will be generated unless the
user explicitly sets one using the ``my_hdr'' command."

Where could be my mistake? Which command prevents mutt from taking over
the desired parameters?

Rudolf

PS.: Here my Mutt's capabilities:

---
[EMAIL PROTECTED]:~$ mutt -v
Mutt 1.5.18 (2008-05-17)
Copyright (C) 1996-2008 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.24-1-686 (i686)
ncurses: ncurses 5.6.20080503 (compiled with 5.6)
libidn: 1.8 (compiled with 1.8)
hcache backend: GDBM version 1.8.3. 10/15/2002 (built Apr 24 2006 03:25:20)
Einstellungen bei der Compilierung:
-DOMAIN
+DEBUG
-HOMESPOOL  +USE_SETGID  +USE_DOTLOCK  +DL_STANDALONE
+USE_FCNTL  -USE_FLOCK
+USE_POP  +USE_IMAP  +USE_SMTP  -USE_GSS  -USE_SSL_OPENSSL  +USE_SSL_GNUTLS  
+USE_SASL  +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"
Um die Entwickler zu kontaktieren, schicken Sie bitte
eine Nachricht (in englisch) an <[EMAIL PROTECTED]>.
Um einen Bug zu melden, besuchen Sie bitte http://bugs.mutt.org/.

patch-1.5.13.cd.ifdef.2
patch-1.5.13.cd.purge_message.3.4
patch-1.5.13.nt+ab.xtitles.4
patch-1.5.4.vk.pgp_verbose_mime
patch-1.5.6.dw.maildir-mtime.1
patch-1.5.8.hr.sensible_browser_position.3
---

Re: [FEATURE REQUEST] ~/.muttrc, ~/.mutt/muttrc and other

[Rocco Rutte]

Hi,

* Rado S wrote:

=- Michelle Konzack wrote on Sun 18.May'08 at  0:06:56 +0200 -=



This would simplify things, because currently if I use



mutt -F ~/.mutt_bts/muttrc



I have to specify ALL files I source with the FULL PATH which mess
up things since some files are only copies from other configs and
I have to edit this files all the time I want to change
something...



Using symlinks and abusing "$folder" should ease things.


Plus shell commands for setup (e.g. 'ls' which can also be useful to 
generate the appropriate mailboxes command for local mailboxes) and 
custom my_ variables instead of using $folder (if mutt is recent 
enough) since that's what they're for, after all... :)


Rocco

Re: [FEATURE REQUEST] ~/.muttrc, ~/.mutt/muttrc and other

[Rado S]

=- Michelle Konzack wrote on Sun 18.May'08 at  0:06:56 +0200 -=

> This would simplify things, because currently if I use
> 
> mutt -F ~/.mutt_bts/muttrc
> 
> I have to specify ALL files I source with the FULL PATH which mess
> up things since some files are only copies from other configs and
> I have to edit this files all the time I want to change
> something...

Using symlinks and abusing "$folder" should ease things.

-- 
© Rado S. -- You must provide YOUR effort for your goal!
EVERY effort counts: at least to show your attitude.
You're responsible for ALL you do: you get what you give.

[FEATURE REQUEST] ~/.muttrc, ~/.mutt/muttrc and other directories

[Michelle Konzack]

Hello,

Since I am developer and my mailinglist/bts subscriptions explode I like
to separate the stuff.  Unfortunately I have  already  over  200  config
files in my ~/.mutt/ directory.

I know I can use

mutt -F ~/.mutt/muttrc_std
mutt -F ~/.mutt/muttrc_bts
mutt -F ~/.mutt/muttrc_ml

but this keep all the config files in the same  directory  which  is  by
default ~/.mutt/.

Now I have tried to use

mutt -F ~/.mutt_bts/

but this does not work.

So I like to see the feature, that if "mutt" is called with a DIRECTORY
as parameter for -F then the default ~/.mutt/ is not more used.

This would simplify things, because currently if I use

mutt -F ~/.mutt_bts/muttrc

I have to specify ALL files I source with the FULL PATH  which  mess  up
things since some files are only copies from other configs and I have to
edit this files all the time I want to change something...

Thanks, Greetings and nice Day
Michelle Konzack
Systemadministrator
24V Electronic Engineer
Tamay Dogan Network
Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
+49/177/935194750, rue de Soultz MSN LinuxMichi
+33/6/61925193 67100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Re: Grouping commands in muttrc?

[Dan H.]

On Fri, Jan 25, 2008 at 09:18:05AM +0100, Dan H. wrote:

> Curiously, however, the "identity switching" works but the sorting doesn't.
> I always het everything sorted by date.

Duh. That's because it's 'threads', not 'thread'.

Sorry for bandwidth waste.

--D.

Re: Grouping commands in muttrc?

[Dan H.]

On Thu, Jan 24, 2008 at 10:09:28AM -0600, Kyle Wheeler wrote:

> Yup, you can put several commands in a folder-hook; you just have to 
> separate them with semicolons and put them all in a single quote 
> block. They can even span multiple lines, like so:
> 
>  folder-hook . 'set ascii_chars=yes ; set othervariable=no ; \
> set thirdvariable=ask-yes'

I've done that and it kinda works. This is from my muttrc:

folder-hook . '\
source $HOME/.mutt/profile.normal; \
set sort=date'

folder-hook Lists '\
source $HOME/.mutt/profile.dunno; \
set sort=thread'

The idea is that I like threaded listing for mailing lists, and by-date
otherwise. Also I have two different "identities" for mailing lists and
work.

Curiously, however, the "identity switching" works but the sorting doesn't.
I always het everything sorted by date.

How's that possible?

--D.

Re: Grouping commands in muttrc?

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Thursday, January 24 at 04:29 PM, quoth Dan H.:
> please note that I'm sending this from mutt. It was an uphill battle 
> and I'm still not sure if I won, but I'm getting there.

So far so good! The message made it!

> One question: Is it possible to group commands after, for instance, 
> a folder-hook? Like when I move into a folder I want a whole bunch 
> of commands executed. Or do I have to put those into a file and 
> source that with the folder-hook?

Yup, you can put several commands in a folder-hook; you just have to 
separate them with semicolons and put them all in a single quote 
block. They can even span multiple lines, like so:

 folder-hook . 'set ascii_chars=yes ; set othervariable=no ; \
set thirdvariable=ask-yes'

~Kyle
- -- 
Do not seek to follow in the footsteps of the men of old. Seek what 
they sought.
-- Matsuo Basho
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!

iD8DBQFHmLg4BkIOoMqOI14RAl0HAJ9wEh6SRBXGnySSYxw3oGpoGSMfNQCgnnei
slLvPspxQUtn0DWAjeQ57as=
=fkw4
-END PGP SIGNATURE-

Grouping commands in muttrc?

[Dan H.]

Hello, 

please note that I'm sending this from mutt. It was an uphill battle and I'm
still not sure if I won, but I'm getting there.

One question: Is it possible to group commands after, for instance, a
folder-hook? Like when I move into a folder I want a whole bunch of commands
executed. Or do I have to put those into a file and source that with the
folder-hook?

Thanks,
--D.

Re: Setting subscribe/list within muttrc (using IMAP) [SOLVED]

[Rocco Rutte]

Hi,

* David J. Weller-Fahy wrote:

* Rocco Rutte <[EMAIL PROTECTED]> [2007-09-06 06:19 -0700]:



Just a minor note: When does this script get called? I'm asking
because if it gets called more than once per session, you'll keep
adding the same lines of folder-hook and subscribe all the time. Or do
you clear them previously?



Sorry, just noticed this email.



The script gets called every time a new mailbox is entered.  I do not
clear the values, because I assumed that identical values would be
overwritten.  That may be a bad assumption.  I'll have to contemplate my
setup and see if there's a better way to do what I want to do, again. ;]


Sorry, my fault. I looked at the code and does check for duplicates for 
folder-hook and subscribe. So as long as the input is stable (and the 
script seems to do that) it should be fine (it does check strings so 
e.g. spaces can matter).


Rocco

Re: Setting subscribe/list within muttrc (using IMAP) [SOLVED]

[David J. Weller-Fahy]

* Rocco Rutte <[EMAIL PROTECTED]> [2007-09-06 06:19 -0700]:
> Just a minor note: When does this script get called? I'm asking
> because if it gets called more than once per session, you'll keep
> adding the same lines of folder-hook and subscribe all the time. Or do
> you clear them previously?

Sorry, just noticed this email.

The script gets called every time a new mailbox is entered.  I do not
clear the values, because I assumed that identical values would be
overwritten.  That may be a bad assumption.  I'll have to contemplate my
setup and see if there's a better way to do what I want to do, again. ;]

Regards,
-- 
David J. Weller-Fahy| 'These are the questions that kept me out
largely at innocent dot com |  of the really *good* schools.'
www dot weller-fahy dot com |  - One of The Group

Re: numerical field in .muttrc for positioning menus

[Mauro Sacchetto]

Alle martedì 20 novembre 2007, Kyle Wheeler ha scritto:
> It's the same logic as in printf. To quote the applicable parts from
> the man page:
[cut]
> Does that make sense?

Yes, great answer, it' almost a treatise! :-)
Thanx a lot
M.

-- 
linux user no.: 353546
public key at http://keyserver.linux.it

Re: numerical field in .muttrc for positioning menus

[Kyle Wheeler]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Tuesday, November 20 at 12:29 AM, quoth Mauro Sacchetto:
>In my -muttrc I've , for instance:
>set index_format = "(%3C) %Z %-7.7{%b %d} %-20.20F (lin:%4l msg:%2M) %-28.28t 
>%s"
>What is the exact logic of the numerical field, as -7.7
>to obtain the right positioning of the fileds FROM, TOO etc?

It's the same logic as in printf. To quote the applicable parts from 
the man page:

 Each format specification is introduced by the percent character
 (``%''). The remainder of the format specification includes, in
 the following order:

 Zero or more of the following flags:

 -   A minus sign `-' which specifies left adjustment of the
 output in the indicated field;
 ` ' A space specifying that a blank should be left before a
 positive number for a signed format.  A `+' overrides a
 space if both are used;
 0   A zero `0' character indicating that zero-padding should
 be used rather than blank-padding.  A `-' overrides a `0'
 if both are used;

 Field Width:
 An optional digit string specifying a field width; if the
 output string has fewer characters than the field width it
 will be blank-padded on the left (or right, if the
 left-adjustment indicator has been given) to make up the field
 width (note that a leading zero is a flag, but an embedded
 zero is part of a field width);

 Precision:
 An optional period, `.', followed by an optional digit string
 giving a precision which specifies the number of digits to
 appear after the decimal point, for e and f formats, or the
 maximum number of characters to be printed from a string; if
 the digit string is missing, the precision is treated as zero;

Translating that, in the case of something like %-7.8s, we're telling 
mutt that:

 1. We want to print the subject (because it ends in s)
 2. Exactly 7 spaces are to be reserved for the subject (because of
the 7), but more may be printed if the subject is longer.
 3. The subject must be right-aligned (because of the -).
 4. Only 8 characters may be printed.

To demonstrate the difference, let's take two subjects, "foobarbaz" 
and "morky" to play with. I'll surround them with wockas (><) so that 
you can see where other text would be printed if they were part of a 
longer line. If we print both of them with >%s< we get:

 >foobarbaz<
 >morky<

If we use >%7s< we get:

 >foobarbaz<
 >  morky<

Note that in both cases, 7 spots were reserved, but the longer subject 
printed in its entirety anyway. If we negated it (>%-7s<), we'd get:

 >foobarbaz<
 >morky  <

If we just use the bit after the decimal (>%.7s<), we're limiting how 
many characters can print:

 >foobarb<
 >morky<

Note that without reserving spaces, adding a negative (>%-.7s<) does 
nothing:

 >foobarb<
 >morky<

BUT these two can be combined to simulate a tabulated list. We use the 
first number (to the left of the decimal) to reserve character spaces, 
and the second number (to the right of the decimal) to limit how many 
print. For example, if we use >%7.7s< then it looks like:

 >foobarb<
 >  morky<

Adding a negative (>%-7.7s<) aligns things to the left:

 >foobarb<
 >morky  <

To put that back in context, let's take a look at your $index_format:

set index_format = "(%3C) %Z %-7.7{%b %d} %-20.20F (lin:%4l msg:%2M) %-28.28t 
%s"

Let's pretend that you have an unread message from foo sent on 
November 20th, that's 10 lines long and 1k big, with a subject of "get 
a load of this weird stuff!". That would be displayed like this:

   1 N   Nov 20  foo  (lin:10   msg:1k) you 
get a load of this weird stuff

Let me replace the spaces that were added as padding with underscores 
so you can see them:

__1 N   Nov 20_ foo_ (lin:10__ msg:1k) 
you get a load of this weird stuff

Let's ignore everything after the msg: part, just to keep things 
simple:

__1 N   Nov 20_ foo_ (lin:10__ msg:1k)

Here's what it would look like if you used %20.20F instead of %-20.20F:

__1 N   Nov 20_ _foo (lin:10__ msg:1k)

It would look exactly the same for this mail if you used %20F instead 
of %-20.20F, but if the sender was foobarbazquxquuxgarply instead of 
foo, here's how it would compare:

__1 N   Nov 20_ foobarbazquxquuxgarp (lin:10__ msg:1k) << %-20.20F
__1 N   Nov 20_ foobarbazqux

numerical field in .muttrc for positioning menus

[Mauro Sacchetto]

In my -muttrc I've , for instance:
set index_format = "(%3C) %Z %-7.7{%b %d} %-20.20F (lin:%4l msg:%2M) %-28.28t 
%s"
What is the exact logic of the numerical field, as -7.7
to obtain the right positioning of the fileds FROM, TOO etc?
Thanx
MS

-- 
Prof. Mauro Sacchetto
Santa Croce 1332a
30155 VENEZIA
tel.: 041 5226494
cell.: 320 7414579
e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
linux user no.: 353546
public key at http://keyserver.linux.it

Re: Muttrc not source when reading from stdin

[Michelle Konzack]

Am 2007-11-12 11:41:51, schrieb Roger Cornelius:
> mutt 1.5.16, 1.5.17
> SCO OSR507 & OSR6
> 
> I have "hostname=" in the system Muttrc file.  If I invoke
> mutt interactively to send a message, e.g. "mutt someuser", the hostname
> setting is honored and the From and To headers both contain  as
> expected.  But if mutt reads it's input from stdin,
> e.g. "echo test | mutt -s test someuser", the hostname= setting is
> ignored and neither the From nor To headers reflect the hostname
> setting.  My .signature is also not appended to the message.
> 
> Is this intended behavour, or am I missing something (or a bug)?

I am using 1.5.13 and I have the same behaviour here.
I need to use

echo test | mutt -f ~/.mutt/muttrc -s test someuser

to get it working.

Thanks, Greetings and nice Day
Michelle Konzack
Tamay Dogan Network
Open Hardware Developer
Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSN LinuxMichi
0033/6/6192519367100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Muttrc not source when reading from stdin

[Roger Cornelius]

mutt 1.5.16, 1.5.17
SCO OSR507 & OSR6

I have "hostname=" in the system Muttrc file.  If I invoke
mutt interactively to send a message, e.g. "mutt someuser", the hostname
setting is honored and the From and To headers both contain  as
expected.  But if mutt reads it's input from stdin,
e.g. "echo test | mutt -s test someuser", the hostname= setting is
ignored and neither the From nor To headers reflect the hostname
setting.  My .signature is also not appended to the message.

Is this intended behavour, or am I missing something (or a bug)?
-- 
Roger Cornelius[EMAIL PROTECTED]

Re: Setting subscribe/list within muttrc (using IMAP) [SOLVED]

[Rocco Rutte]

Hi,

* David J. Weller-Fahy [07-08-30 23:28:27 +0200] wrote:

[...]

Just a minor note: When does this script get called? I'm asking because 
if it gets called more than once per session, you'll keep adding the 
same lines of folder-hook and subscribe all the time. Or do you clear 
them previously?


  bye, Rocco
--
:wq!

Re: Setting subscribe/list within muttrc (using IMAP) [SOLVED]

[David J. Weller-Fahy]

* Michelle Konzack <[EMAIL PROTECTED]> [2007-08-29 19:12 +0200]:
> Am 2007-08-24 23:49:36, schrieb David J. Weller-Fahy:
> > Perhaps I'm looking for a feature that doesn't exist, and I'm almost
> > certainly missing something simple, but here's the background:
> 
>
> It seems there is no way in mutt...

That is the way it seemed.  However, after digging into the archives a
bit deeper, and playing with a patch I found, I've come up with a
solution that works for me (it does require patching, though).  Details
follow.

Inspiration came from:
<http://marc.info/?l=mutt-users&m=99616338121641&w=2>

The patch exports the current mailbox name to an environment variable,
then I source a shell script as part of a folder hook.  The shell script
parses the mailbox name to determine whether it is a list mailbox, then,
if it is, outputs the muttrc commands I use for lists.  I've tested this
with all the lists I subscribe to, and it works with one caveat:

All my lists are stored in the format =lists.list-name, so
mutt-users is in =lists.mutt-users.  While this makes it easy for my
script to parse the name, it also means that my script/setup may not
work for you.

Hope this helps... I know it doesn't do everything, but it gets me a
little closer. ;]

> I am too using a simplified code sniplet of "uw-imap" to get all
> directories (and number of NEW/READ messages ) from an imap-server...

Would you mind sharing your sniplet?  It may be a bit better than mine.

Regards,
-- 
dave [ please don't CC me ]
# vim:ft=diff:
This is a patch to place the current mailbox path in an environment variable
whenever a folder-hook is called.  This (trivial) patch was based on a
message[1] on the mutt mailing list:

[1]: http://marc.info/?l=mutt-users&m=99616338121641&w=2

In fact, the ONLY differences are the name of the variable, and adding the
patch name to PATCHES. ;]

diff -r f467353f5657 PATCHES
--- a/PATCHES   Sat Mar 31 18:50:39 2007 -0700
+++ b/PATCHES   Wed Aug 29 22:09:38 2007 +0200
@@ -0,0 +1,1 @@
+patch-tip-20070829-env_current_mailbox
diff -r 3f8829e739e9 hook.c
--- a/hook.cTue Aug 28 11:33:52 2007 -0700
+++ b/hook.cThu Aug 30 22:08:56 2007 +0200
@@ -282,6 +282,8 @@ void mutt_folder_hook (char *path)
   BUFFER err, token;
   char buf[STRING];
 
+  setenv( "MUTT_CURRENTMAILBOX", path, 1 );
+
   current_hook_type = M_FOLDERHOOK;
   
   err.data = buf;
#!/bin/sh
# .mutt/rc.testforlist.sh

# This will only work if:
# - $MUTT_CURRENTMAILBOX contains the name of the current mailbox in mutt.
# - Your list directory structure looks like the following:
#   lists
#   lists.aklug
#   lists.mutt-users
#   lists.resnet-l
#   lists.[mailing list name]
#
# If your structure is not like the above, then tweak the code heavily.

mailbox=`echo $MUTT_CURRENTMAILBOX | sed -r -e "s/^imaps:\/\/[^\/]+\///"`
listpfx=`echo $mailbox | cut -d . -f 1`
if test "$listpfx" = "lists" ; then
test "$mailbox" != "lists" && echo "subscribe ${mailbox#lists.}"
echo "folder-hook +$mailbox set from=dave-$( echo $mailbox | tr '.' '-' 
)@weller-fahy.com"
fi

Re: Setting subscribe/list within muttrc (using IMAP)

[Michelle Konzack]

Am 2007-08-24 23:49:36, schrieb David J. Weller-Fahy:
> Perhaps I'm looking for a feature that doesn't exist, and I'm almost
> certainly missing something simple, but here's the background:


It seems there is no way in mutt...

I am too using a simplified code sniplet of "uw-imap" to get all
directories (and number of NEW/READ messages ) from an imap-server...

Greetings
Michelle Konzack
Systemadministrator
Tamay Dogan Network
Debian GNU/Linux Consultant


-- 
Linux-User #280138 with the Linux Counter, http://counter.li.org/
# Debian GNU/Linux Consultant #
Michelle Konzack   Apt. 917  ICQ #328449886
   50, rue de Soultz MSN LinuxMichi
0033/6/6192519367100 Strasbourg/France   IRC #Debian (irc.icq.com)


signature.pgp
Description: Digital signature

Setting subscribe/list within muttrc (using IMAP)

[David J. Weller-Fahy]

Perhaps I'm looking for a feature that doesn't exist, and I'm almost
certainly missing something simple, but here's the background:

I currently use a script to connect to my IMAP server, and get a list of
all mail folders.  I then parse that list to get the mailing list
folders (all named list.mailing-list-name), and use that to generate the
necessary rc commands (subscribe and from).  I would like to remove that
extra connection to the server, and just use rc commands plus a little
shell scripting to do the same thing.

I've searched TFM, and the mailing list via marc.info, but haven't been
able to find anything useful.  I believe I should be able to do what I
need to do if I can figure out how to pass the value of ^ to the shell.

So, is there a way to pass the value of ^ to the shell?  If so, would
someone mind showing me an example?

If there is something about this in the manual/man pages/wiki/mailing
list, a simple scoff and pointer will be sufficient. ;]

Oh, and if there's an easier/better way to do this, please let me know.

Regards,
-- 
dave [ please don't CC me ]

only from pager: source: errors in .mutt/muttrc

[martin f krafft]

Hi, I receive the warning

  source: errors in /home/madduck/.mutt/muttrc

whenever I resource the muttrc from the pager:

  :source /home/madduck/.mutt/muttrc

It works fine from the index and the compose menu.

I checked the keybindings but I don't have any pager-only bindings,
and I cannot fathom what other reason there might be.

How can I figure out what's responsible here? Can I get mutt to give
me a line number? Of course, I could bisect my configuration, but
there has to be a better way to do this.

Thanks,

-- 
martin;  (greetings from the heart of the sun.)
  \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED]
 
an avocado-tone refrigerator would look good on your resume.
 
spamtraps: [EMAIL PROTECTED]


digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)

Re: Module to add mailinglist-names from the header in .muttrc

[Oliver Fuchs]

On Fri, 04 Oct 2002, Sven Guckes wrote:

> * Oliver Fuchs <[EMAIL PROTECTED]> [2002-10-03 15:29]:
> > Is there something similar "no more hand work" for/in mutt?
> > Example: Extract the mailing-list address from the header, add
> > it in .muttrc to the mailbox and the list/subscribe feature?
> 
>   macro index ~~ "grep ... >> $HOME/.muttrc"
> 
> homework:  fill in the dots.
> 
> Sven

Hi,
thanx again for the advice ... I am so lazy thought that someone else
did already the homework ... but I will do it.
By the way:

Can I be punished for something I have forgotten?
No.
I have forgotten to do my homework.
But thanx a lot.

Oliver
-- 
GeRo GeRo GeRo GeRo GeRo-Pee
My heart is on Mars
My heart is on Mars
Planet Heart

Re: Module to add mailinglist-names from the header in .muttrc

[Ryan Sorensen]

> * Oliver Fuchs <[EMAIL PROTECTED]> [2002-10-03 15:29]:
> > Is there something similar "no more hand work" for/in mutt?
> > Example: Extract the mailing-list address from the header, add
> > it in .muttrc to the mailbox and the list/subscribe feature?

Didn't see the original message, I apologize for the minor thread
breaking.

It's possible to set up procmail to automatically recognize most lists,
and then siphon that into a folder based on list name. Like
mutt-users goes to a folder [EMAIL PROTECTED] You could
create a shell script, so that when procmail sees a list mail, it
siphons off into that folder, and calls this shell-script with the name
of the folder. Shell scripts checks some file to see if you've got
things defined, if not, it adds them, and source this file from muttrc.

But I'm sure I'm getting off-topic.

Re: Module to add mailinglist-names from the header in .muttrc

[Sven Guckes]

* Oliver Fuchs <[EMAIL PROTECTED]> [2002-10-03 15:29]:
> Is there something similar "no more hand work" for/in mutt?
> Example: Extract the mailing-list address from the header, add
> it in .muttrc to the mailbox and the list/subscribe feature?

  macro index ~~ "grep ... >> $HOME/.muttrc"

homework:  fill in the dots.

Sven

Module to add mailinglist-names from the header in .muttrc

[Oliver Fuchs]

Hi,

I found these days that there is a procmail-module which can do the
following:

o   *pm-jalist.rc* -- Subroutine to extract mailing list name from
message. Do you need to add new recipe to your .procmailrc
every time you subscribe to new mailing list? If you do,
take a look at this module, which examines the message and
defines variable `LIST' to hold the mailing list name. You
can use it directly to save the messages adaptively to
correct folders. No more hand work and manual storing
of mailing list messages.

Is there something similar "no more hand work" for/in mutt?

Example:
Extract the mailing-list address from the header, add it in .muttrc to
the mailbox and the list/subscribe feature?

Oliver
-- 
GeRo GeRo GeRo GeRo GeRo-Pee
My heart is on Mars
My heart is on Mars
Planet Heart

Migrating from MH to mutt (helpful muttrc)

[Adam Fields]

I've posted my .muttrc, which has a bunch of MH-like keybindings (the
ones I use most). If you're switching over from MH, you might find
that this helps ease the transition.

Enjoy!

http://www.aquick.org/adam_muttrc.txt


-- 
- Adam

-
Adam Fields, Managing Partner, [EMAIL PROTECTED]
Surgam, Inc. is a technology consulting firm with strong background in
delivering scalable and robust enterprise web and IT applications.
Ask about Vignette maximization: http://www.surgam.net/vignette.html

Re: BUG - wrapping lines in muttrc

[Bruno Postle]

On Sun 04-Aug-2002 at 01:39:21 -0400, Andy Saxena wrote:
> 
> I think I may have found a possible bug in the way .muttrc is parsed.
> I ran into this while setting up a folder-hook option.
> 
> If \ is the last character on a line that's commented out, mutt seems
> to read the line instead of ignoring it.

The \ at the end of the line continues the comment:

  # this is a comment that \
continues over multiple \
lines.

I was caught by this, vim syntax highlighting isn't 100% with such
obscure stuff.

-- 
Bruno

Re: BUG - wrapping lines in muttrc

[Andre Berger]

--gj572EiMnwbLXET9
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

* Andy Saxena <[EMAIL PROTECTED]>, 2002-08-04 13:40 -0400:
> Hi,
>=20
> I think I may have found a possible bug in the way .muttrc is parsed. I
> ran into this while setting up a folder-hook option.
>=20
> If \ is the last character on a line that's commented out, mutt seems to
> read the line instead of ignoring it.
>=20
> Here are my test cases:
> Test Case 1 -
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> #folder-hook .\
> folder-hook (mutt-users|debian-.*|vim) \
>   push ~r>6w
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Result - The folder-hook does not work.

Shouldn't it be folder-hook . \
 ^
> Test Case 2 -
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> #folder-hook .\
> folder-hook (mutt-users|debian-.*|vim) \
>   push ~r>6w
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Result - The folder-hook is enabled.
>=20
> Could somebody please reproduce this and verify that it is indeed the
> case? If it is verified I will file a bug report.

I don't see the bug :)

-Andre

--gj572EiMnwbLXET9
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9TWfZWkhBtALlJZ0RAv52AJ4l/icuyIt8YamVWWhQinHg7FSPRwCfVETH
vQUcOQoOcPCo3iFuQyHBBE4=
=Fvqs
-END PGP SIGNATURE-

--gj572EiMnwbLXET9--

BUG - wrapping lines in muttrc

[Andy Saxena]

Hi,

I think I may have found a possible bug in the way .muttrc is parsed. I
ran into this while setting up a folder-hook option.

If \ is the last character on a line that's commented out, mutt seems to
read the line instead of ignoring it.

Here are my test cases:
Test Case 1 -
=
#folder-hook .\
folder-hook (mutt-users|debian-.*|vim) \
push ~r>6w
=
Result - The folder-hook does not work.

Test Case 2 -
=
#folder-hook .\
folder-hook (mutt-users|debian-.*|vim) \
push ~r>6w
=
Result - The folder-hook is enabled.

Could somebody please reproduce this and verify that it is indeed the
case? If it is verified I will file a bug report.

Thanks,
Andy

Re: categorizing muttrc -> upload to webserver, post url

[Vincent Lefevre]

On Tue, Jul 30, 2002 at 14:40:00 +0200, Sven Guckes wrote:
> a better way is that of vim which includes the info
> that the option/variable is only available when
> some code is in binary as indicated by "+feature"
> in the outut of the ":version" command.

Yes, we should have something like that in Mutt. And when it depends
on the configuration, the default value shouldn't be given, as it may
be wrong (this would confuse the user).

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web:  - 100%
validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International
des Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Re: categorizing muttrc -> upload to webserver, post url

[Sven Guckes]

* Vincent Lefevre <[EMAIL PROTECTED]> [2002-07-30 09:29]:
> On Tue, Jul 30, 2002 at 10:22:43 +0200, Sven Guckes wrote:
> > * Russell L. Harris <[EMAIL PROTECTED]> [2002-07-30 06:22]:
> > > (variables not applicable to the particular
> > > installation may be commented out, using #)
> > 
> > you want manuals which depend on the current installation?
> > what about systems which more than one mutt binary?
> > my point:  this won't work.
> 
> I think that Mutt should be fixed concerning this point.
> For instance, on one of my accounts, the manual says:
>   6.3.36.  dotlock_program
>   Contains the path of the mutt_dotlock (8) binary to be used by mutt.
> 
> But as dotlocking is disabled, this variable doesn't exist!

bad idea.
what if the manual does not describe this variable
and the user hits on a mutt binary which includes it?

a better way is that of vim which includes the info
that the option/variable is only available when
some code is in binary as indicated by "+feature"
in the outut of the ":version" command.

something similar for mutt would be most welcome.

Sven

Re: categorizing muttrc -> upload to webserver, post url

[Vincent Lefevre]

On Tue, Jul 30, 2002 at 10:22:43 +0200, Sven Guckes wrote:
> * Russell L. Harris <[EMAIL PROTECTED]> [2002-07-30 06:22]:
> > (variables not applicable to the particular
> > installation may be commented out, using #)
> 
> you want manuals which depend on the current installation?
> what about systems which more than one mutt binary?
> my point:  this won't work.

I think that Mutt should be fixed concerning this point.
For instance, on one of my accounts, the manual says:

  6.3.36.  dotlock_program

  Type: path
  Default: "/usr/local/bin/mutt_dotlock"

  Contains the path of the mutt_dotlock (8) binary to be used by mutt.

But as dotlocking is disabled, this variable doesn't exist! And
if I choose to enable dotlocking, the default path won't be

  /usr/local/bin/mutt_dotlock

but something in my home directory (the path depends on the $bindir
variable, defined when compiling Mutt).

Look at init.h, the existence of some other variables depends
on configure settings (HAVE_PGP, HAVE_MIME, USE_IMAP, USE_SSL
and so on).

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web:  - 100%
validated (X)HTML - Acorn Risc PC, Yellow Pig 17, Championnat International
des Jeux Mathématiques et Logiques, TETRHEX, etc.
Work: CR INRIA - computer arithmetic / SPACES project at LORIA

Re: categorizing muttrc -> upload to webserver, post url

[Sven Guckes]

* Russell L. Harris <[EMAIL PROTECTED]> [2002-07-30 06:22]:
> I am a mutt newbie.  It seems to me that
> configuration of mutt would be easier if:
> * muttrc contains the entire set of mutt
> configuration variables

are you saying that there are
options missing in the manual?
if so then please send in
a bug report using "flea".

> (variables not applicable to the particular
> installation may be commented out, using #)

you want manuals which depend on the current installation?
what about systems which more than one mutt binary?
my point:  this won't work.

> * the configuration variables are grouped in categories..

Been there, done that, got the tshirt.
but that was some five years ago.

> * each variable would be accompanied by a brief
> comment regarding applicability and proper usage

examples?  well, you can fill manuals with
billions of examples - but then the real
power is with combining them with other options.
and that's where online setup files can help more.

> Are there drawbacks to such a scheme?

yes.
copy cats will simply rely on
the examples without thinking.
but we usually send these people
over to the pine folks.  hehehe

> I have begun categorizing the configuration variables.
> I solicit comments and recommendations.
> Would anyone be interested in posting a copy
> of the commented configuration file?

please don't post huse setup files onto this list, thankyou.
instead, upload it to your webserver and post the url.

Sven

-- 
Sven Guckes  http://www.math.fu-berlin.de/~guckes/mutt/setup.html
Mutt setup from scratch, Sven's sample setup; attribution, "limit", "list"
vs "subscribe", histories, mailcap, POP, hooks, use of external pagers,
troubleshooting, adding header lines, "from Mozilla to Mutt".

Re: categorizing muttrc

[Rocco Rutte]

Hi,

* Russell L. Harris [02-07-30 08:39:13 +0200] wrote:
> * muttrc contains the entire set of mutt configuration
> variables (variables not applicable to the particular
> installation may be commented out, using #)

Hmm, I don't think this is really necessary because of two
reasons. First of all, one doesn't need every variable to be
set; second, I wouldn't switch to mutt if the first thing I
saw was a file containing ~200 variables with lots of
comments. But in fact, that's what the manual is for: sorted
by category with good explanations instead of a short
comment. If you like, just take manual.txt and reorder the
variables in section 6.

[...]

> Are there drawbacks to such a scheme?  Would anyone be
> interested in posting a copy of the commented
> configuration file?  Would this project have the blessing
> of the author of mutt?

There's a muttrcbuilder on the web which does produces
muttrcs while variables are sorted by categories. Those
people will certainly be interested in what you have to
contribute.

> I have begun categorizing the configuration variables.  I
> solicit comments and recommendations.

Lots of people do it. But organizing muttrc highly depends
on personal tasts and such.

   bye, Rocco

Re: categorizing muttrc

[Rob 'Feztaa' Park]

--8P1HSweYDcXXzwPJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Alas! Russell L. Harris spake thus:
> I am a mutt newbie.  It seems to me that configuration of mutt would be=
=20
> easier if:
>=20
> * muttrc contains the entire set of mutt configuration variables (variabl=
es=20
> not applicable to the particular installation may be commented out, using=
 #)

I disagree. Mutt has manuals for a reason. Plus there are scores of
people who have their muttrc's online that you can read for examples.

> * the configuration variables are grouped in categories, such as the=20
> following (this list is incomplete):
>=20
> user interface
> message composition
> attachments
> file copy of messages
> message headers
> message display
> message transmission
> message printing
> mailboxes
> address qualification
> user personalities
> encryption & ssl
> message piping
> message scoring
> message signatures
> searching
> sorting
> MIME
> mixmaster
> POP
> IMAP
> MH
> aliases
>=20
> * each variable would be accompanied by a brief comment regarding=20
> applicability and proper usage
>=20
> Are there drawbacks to such a scheme?  Would anyone be interested in=20
> posting a copy of the commented configuration file?  Would this project=
=20
> have the blessing of the author of mutt?

Drawbacks:

 - the documentation would have to be rewritten
 - there wouldn't really be a benefit because if you're searching for
   something, you can just search for the keywords, no grouping
   necessary.
 - etc, I guess.

--=20
Rob 'Feztaa' Park
http://members.shaw.ca/feztaa/
--
Warning: Listening to WXRT on April Fools' Day is not recommended for
those who are slightly disoriented the first few hours after waking up.
-- Chicago Reader 4/22/83

--8P1HSweYDcXXzwPJ
Content-Type: application/pgp-signature
Content-Disposition: inline

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9RjW2PTh2iSBKeccRAoCyAJ0TAnhttPrrTQBmUkM2fA/K6NZvUwCggKD4
HrCryKprablJFBPCjz7l/s8=
=KaHP
-END PGP SIGNATURE-

--8P1HSweYDcXXzwPJ--

categorizing muttrc

[Russell L. Harris]

I am a mutt newbie.  It seems to me that configuration of mutt would be 
easier if:

* muttrc contains the entire set of mutt configuration variables (variables 
not applicable to the particular installation may be commented out, using #)

* the configuration variables are grouped in categories, such as the 
following (this list is incomplete):

 user interface
 message composition
 attachments
 file copy of messages
 message headers
 message display
 message transmission
 message printing
 mailboxes
 address qualification
 user personalities
 encryption & ssl
 message piping
 message scoring
 message signatures
 searching
 sorting
 MIME
 mixmaster
 POP
 IMAP
 MH
 aliases

* each variable would be accompanied by a brief comment regarding 
applicability and proper usage

Are there drawbacks to such a scheme?  Would anyone be interested in 
posting a copy of the commented configuration file?  Would this project 
have the blessing of the author of mutt?

I have begun categorizing the configuration variables.  I solicit comments 
and recommendations.

RLH

Re: generating .muttrc

[darren chamberlain]

* Martin Siegert <[EMAIL PROTECTED]> [2002-07-09 14:08]:
> Thus, the question is: has anybody expanded mutt to include something
> like an option menu that can be called from within mutt?

Several months ago, there was a thread about writing a utility to
generate a muttrc for a user.  I took a stab at it (see
<http://www.mail-archive.com/mutt-users@mutt.org/msg25193.html> for my
little perl script), and then... nothing happened.  It's a beginning,
though, and the script concentrates on things that it can get from the
environment and simple questions, and all the settings it writes are
related directly to the user: realname, email addresses (and
alternates), postponed stuff.  It's something to start from (if
not too much else) if you decide to write something to do the job.

It's a command line script, so it can be setup to run as part of an
account creation process, for example (all the schools I've been to
have a kind of self-service account creation mechanism, I'm assuming you
have something similar).

We can talk more about the script offlist if you're interested.

(darren)

-- 
Democracy is a form of government where you can say what you
think, even if you don't think.

Re: generating .muttrc

[Raoul Bönisch]

On Wed, Jul 10, 2002 at 09:52:56AM -0700, Martin Siegert wrote:
> On Wed, Jul 10, 2002 at 09:03:04AM +0200, Rocco Rutte wrote:
> > * Martin Siegert [02-07-10 08:34:56 +0200] wrote:

[...]

> > I wouldn't replace it. I would let the users choose their
> > MUA.
> 
> This is undesirable: pine is a nightmare to maintain (hard-coded paths, etc.)
> and, more importantly, a reoccuring security problem. We have to get
> rid of elm, because we want to get rid of NFS exported mail spools. 
> Thus, we want to switch to pop/imap exclusively.
> Without those reasons I wouln't even consider switching to mutt with
> all its undesirable consequences (i.e., faculty members complaining
> about not being able to use their favorite email reader).

"I can't open my favorite security flaw anymore! What happened?"

[...]

> Yes, I know. The problem starts when a user decides that (s)he does
> not like the settings I choose in Muttrc.

What's "(s)he"? Couldn't find it in my dictionary.

[...]

> Not that important. The options menu should only contain the most
> basic settings. The expert can edit ~/.muttrc.

This would especially be bloat if it was integrated within mutt. :o)

External programs should do this.

> > > Thus, the question is: has anybody expanded mutt to
> > > include something like an option menu that can be called
> > > from within mutt?
> > 
> > Not that I know.
> 
> I am right now considering using something like the muttrc builder
> (http://mutt.netliberte.org/) running under lynx. I could bind the
> whole thing to some key in mutt. I was hoping that somebody had done
> something like that already.
> (I guess this is kind of contradictory: using a web browser to configure
> a command line email reader that users use because they do not want to
> use a web browser for email).

Nevertheless that's a nice idea. But I'm afraid using configuration
files off the net without checking is a security risk. The users
and useresses should really first check the generated config file
before using it! Or you should use secure connections to trusted
institutions to generate them.

Raoul

auto-generating .muttrc

[Martin Siegert]

On Wed, Jul 10, 2002 at 09:03:04AM +0200, Rocco Rutte wrote:
> Hi,
> 
> * Martin Siegert [02-07-10 08:34:56 +0200] wrote:
> > I am planning to replace elm and pine with mutt as the
> > university wide default email reader.
> 
> Just do:
> 
>   $ rm `which elm`
>   $ ln -s `which pine` /bin/false
> 
> ;-)
> 
> I wouldn't replace it. I would let the users choose their
> MUA.

This is undesirable: pine is a nightmare to maintain (hard-coded paths, etc.)
and, more importantly, a reoccuring security problem. We have to get
rid of elm, because we want to get rid of NFS exported mail spools. 
Thus, we want to switch to pop/imap exclusively.
Without those reasons I wouln't even consider switching to mutt with
all its undesirable consequences (i.e., faculty members complaining
about not being able to use their favorite email reader).

> > This will only be possible, if it is "convenient" to
> > switch to mutt.
> 
> It is. There's a system-wide config file. Without a
> ~/.muttrc it works just fine. All settings you find usefull
> just go in there (/etc/Muttrc, or whatever, depending on the
> OS).
 
Yes, I know. The problem starts when a user decides that (s)he does
not like the settings I choose in Muttrc.

> > Thus, the biggest show-stopper I can find right now that
> > mutt does not seem to have an "option" menu that allows
> > users to modify the default settings to their liking.
> 
> The problem with an option menu is that mutt has kind of
> static and dynamic configuration. Static can be easily done
> by just presenting editing fields for variables. But what to
> do with the dynamic part (all the hooks, for example)?

Not that important. The options menu should only contain the most
basic settings. The expert can edit ~/.muttrc.

> > Thus, the question is: has anybody expanded mutt to
> > include something like an option menu that can be called
> > from within mutt?
> 
> Not that I know.

I am right now considering using something like the muttrc builder
(http://mutt.netliberte.org/) running under lynx. I could bind the
whole thing to some key in mutt. I was hoping that somebody had done
something like that already.
(I guess this is kind of contradictory: using a web browser to configure
a command line email reader that users use because they do not want to
use a web browser for email).

Thanks for the comments.

Cheers,
Martin

Re: pattern match variables in muttrc regexp

[Rocco Rutte]

Hi,

* Mark [02-07-10 20:10:11 +0200] wrote:
> I want to save a copy of each message I send saved into
> the current folder. Didn't think this would work:
> folder-hook   (.) set record=$1
> and it didn't.

What I recently picked up (didn't know it before): One may
use printf()-style sequences in fcc-hook. Example to match
your needs:

  fcc-hook . $path/sent-%B

in your ~/.muttrc. Since this is not documented (or I didn't
find it) I don't know what the letters expand to. I guess
one may use the values from $index_format.

> I'd also like a second copy saved into a 'sent-mail' folder.

That won't work easily. There's a patch (I don't know the
URL right now) so that you can use a script two save the two
messages.

   bye, Rocco

Re: generating .muttrc

[Martin Siegert]

On Wed, Jul 10, 2002 at 09:03:04AM +0200, Rocco Rutte wrote:
> Hi,
> 
> * Martin Siegert [02-07-10 08:34:56 +0200] wrote:
> > I am planning to replace elm and pine with mutt as the
> > university wide default email reader.
> 
> Just do:
> 
>   $ rm `which elm`
>   $ ln -s `which pine` /bin/false
> 
> ;-)
> 
> I wouldn't replace it. I would let the users choose their
> MUA.

This is undesirable: pine is a nightmare to maintain (hard-coded paths, etc.)
and, more importantly, a reoccuring security problem. We have to get
rid of elm, because we want to get rid of NFS exported mail spools. 
Thus, we want to switch to pop/imap exclusively.
Without those reasons I wouln't even consider switching to mutt with
all its undesirable consequences (i.e., faculty members complaining
about not being able to use their favorite email reader).

> > This will only be possible, if it is "convenient" to
> > switch to mutt.
> 
> It is. There's a system-wide config file. Without a
> ~/.muttrc it works just fine. All settings you find usefull
> just go in there (/etc/Muttrc, or whatever, depending on the
> OS).
 
Yes, I know. The problem starts when a user decides that (s)he does
not like the settings I choose in Muttrc.

> > Thus, the biggest show-stopper I can find right now that
> > mutt does not seem to have an "option" menu that allows
> > users to modify the default settings to their liking.
> 
> The problem with an option menu is that mutt has kind of
> static and dynamic configuration. Static can be easily done
> by just presenting editing fields for variables. But what to
> do with the dynamic part (all the hooks, for example)?

Not that important. The options menu should only contain the most
basic settings. The expert can edit ~/.muttrc.

> > Thus, the question is: has anybody expanded mutt to
> > include something like an option menu that can be called
> > from within mutt?
> 
> Not that I know.

I am right now considering using something like the muttrc builder
(http://mutt.netliberte.org/) running under lynx. I could bind the
whole thing to some key in mutt. I was hoping that somebody had done
something like that already.
(I guess this is kind of contradictory: using a web browser to configure
a command line email reader that users use because they do not want to
use a web browser for email).

Thanks for the comments.

Cheers,
Martin

pattern match variables in muttrc regexp

[Mark]

I want to save a copy of each message I send saved into the current 
folder. Didn't think this would work:
folder-hook (.) set record=$1
and it didn't.

I'd also like a second copy saved into a 'sent-mail' folder.

Thanks for the help!

-- 

Mark

Re: generating .muttrc

[Rocco Rutte]

Hi,

* Martin Siegert [02-07-10 08:34:56 +0200] wrote:
> I am planning to replace elm and pine with mutt as the
> university wide default email reader.

Just do:

  $ rm `which elm`
  $ ln -s `which pine` /bin/false

;-)

I wouldn't replace it. I would let the users choose their
MUA.

> This will only be possible, if it is "convenient" to
> switch to mutt.

It is. There's a system-wide config file. Without a
~/.muttrc it works just fine. All settings you find usefull
just go in there (/etc/Muttrc, or whatever, depending on the
OS).

> Thus, the biggest show-stopper I can find right now that
> mutt does not seem to have an "option" menu that allows
> users to modify the default settings to their liking.

The problem with an option menu is that mutt has kind of
static and dynamic configuration. Static can be easily done
by just presenting editing fields for variables. But what to
do with the dynamic part (all the hooks, for example)?

> Thus, the question is: has anybody expanded mutt to
> include something like an option menu that can be called
> from within mutt?

Not that I know.

   bye, Rocco

Re: generating .muttrc -> web interface

[Sven Guckes]

* Martin Siegert <[EMAIL PROTECTED]> [2002-07-09 18:09]:
> I am planning to replace elm and pine with mutt
> as the university wide default email reader.

danger will robinson!

> This will only be possible, if it is "convenient" to switch to mutt.

mutt is not convenient in that way.
mutt is too good for most people.

> Thus, the biggest show-stopper I can find right now that
> mutt does not seem to have an "option" menu that allows
> users to modify the default settings to their liking.

it keeps those away who won't RTFM.  feature!

> While copying the system wide Muttrc file to ~/.muttrc
> and editing that file is good enough for myself, this is
> not really an option for university wide deployment.

mutt is not for everybody.  just like some other great programs.

> Thus, the question is: has anybody expanded mutt to include
> something like an option menu that can be called from within mutt?

nope.  such a feature will only be bloat.

there is, however, a web based config file generator thingie.

Sven  [too lazy to look it up though]

-- 
"let them use dead trees!"

generating .muttrc

[Martin Siegert]

Hi,

I am planning to replace elm and pine with mutt as the university wide
default email reader.
This will only be possible, if it is "convenient" to switch to mutt.
Thus, the biggest show-stopper I can find right now that mutt does not
seem to have an "option" menu that allows users to modify the default
settings to their liking.
While copying the system wide Muttrc file to ~/.muttrc and editing that
file is good enough for myself, this is not really an option for
university wide deployment.

Thus, the question is: has anybody expanded mutt to include something
like an option menu that can be called from within mutt?

Thanks for your help.

Cheers,
Martin


Martin Siegert
Academic Computing Servicesphone: (604) 291-4691
Simon Fraser Universityfax:   (604) 291-4242
Burnaby, British Columbia  email: [EMAIL PROTECTED]
Canada  V5A 1S6

Re: Passing muttrc format strings to bash

[David Ellement]

On 020630, at 12:03:38, Rob 'Feztaa' Park wrote
> Alas! Lee J. Moore spake thus:
> > Is this possible or impossible?  ...
> > If, in my
> > index_format, I have this:
> > 
> > `~/bin/maildir-count ~/Maildir/%f`
> > 
> > ...it's actually, ~/Maildir/%f and *not* ~/Maildir/submaildir
> > that's being passed to the bash script.
> 
> Well, yeah. The backticks are being evaluated when mutt starts, not when
> viewing a folder. So of course, %f cannot be expanded because mutt can't
> possibly know what it is.

It is possible to delay evaluation of the backticks, using single
quotes instead of double quotes.  (I don't know, and have tried, if
this will help in this case).

-- 
David Ellement

Re: Passing muttrc format strings to bash

[Lee J. Moore]

On Mon, 01 Jul 2002, Aragon Gouveia wrote:

[..]
> There's a patch here: http://home.uchicago.edu/~dgc/mutt/

Brilliant! :-)

> It works excellently. I'm using it to get mutt to display a 'U' flag for
> my maildir folders that have unread message in them.

It took me five minutes max to patch, recompile and install the
Gentoo Mutt 1.4 ebuild and I've already got the folder_format I
was looking for.  Thanks a lot for that URL.

I think Mutt badly needs some format specifiers relevant to
maildir folders.  However useful this solution may be, having to
use it for a mere message count (in cur and new) seems a bit
much.

-- 
Lee J. Moore
[EMAIL PROTECTED]



msg29333/pgp0.pgp
Description: PGP signature

Re: Passing muttrc format strings to bash

[Aragon Gouveia]

| By Nicolas Rachinsky <[EMAIL PROTECTED]>
|  [ 2002-07-01 01:40 +0200 ]
> I have the vague feeling to remember that
> <[EMAIL PROTECTED]> was about a patch for this
> problem.

There's a patch here: http://home.uchicago.edu/~dgc/mutt/

It works excellently. I'm using it to get mutt to display a 'U' flag for
my maildir folders that have unread message in them.


Regards,
Aragon

Re: Passing muttrc format strings to bash

[Nicolas Rachinsky]

* "Lee J. Moore" <[EMAIL PROTECTED]> [2002-06-30 19:13 +0100]:
> On Sun, 30 Jun 2002, Rob 'Feztaa' Park wrote:
> 
> > Alas! Lee J. Moore spake thus:
> [..]
> > > `~/bin/maildir-count ~/Maildir/%f`
> > > 
> > > ...it's actually, ~/Maildir/%f and *not* ~/Maildir/submaildir
> > > that's being passed to the bash script.
> > 
> > Well, yeah. The backticks are being evaluated when mutt starts, not when
> > viewing a folder. So of course, %f cannot be expanded because mutt can't
> > possibly know what it is.
> 
> It's a pity that muttrc printf style format strings can't be
> expanded into bash variables - allowing the user to pass them to
> external scripts/programs.  
> 
> set $thisvariable="%f"
> set folder_format="`~/bin/myscript $thisvariable`"
> 
> I was hoping to have an incredibly descriptive folder_format
> list, but my plans have been dashed by my little oversight. ;-)

I have the vague feeling to remember that
<[EMAIL PROTECTED]> was about a patch for this
problem.

Nicolas

Re: Passing muttrc format strings to bash

[Lee J. Moore]

On Sun, 30 Jun 2002, Rob 'Feztaa' Park wrote:

> Alas! Lee J. Moore spake thus:
[..]
> > `~/bin/maildir-count ~/Maildir/%f`
> > 
> > ...it's actually, ~/Maildir/%f and *not* ~/Maildir/submaildir
> > that's being passed to the bash script.
> 
> Well, yeah. The backticks are being evaluated when mutt starts, not when
> viewing a folder. So of course, %f cannot be expanded because mutt can't
> possibly know what it is.

It's a pity that muttrc printf style format strings can't be
expanded into bash variables - allowing the user to pass them to
external scripts/programs.  

set $thisvariable="%f"
set folder_format="`~/bin/myscript $thisvariable`"

I was hoping to have an incredibly descriptive folder_format
list, but my plans have been dashed by my little oversight. ;-)

-- 
Lee J. Moore
[EMAIL PROTECTED]



msg29320/pgp0.pgp
Description: PGP signature

Re: Passing muttrc format strings to bash

[Rob 'Feztaa' Park]

Alas! Lee J. Moore spake thus:
> Is this possible or impossible?  I switched to Maildir a couple
> of months ago after years of using mbox and I finally got around
> to completely rewriting my muttrc to try to take advantage of
> Maildirs different little quirks.
> 
> In the index_format (muttrc) variable, I'd like to pass each of
> my sub-Maildir's to a bash script so that I can calculate the
> new, deleted and total number of messages - for each sub-Maildir
> - and put it in the message index.  However, when I call my bash
> script, the %f (of course) isn't being expanded.  If, in my
> index_format, I have this:
> 
> `~/bin/maildir-count ~/Maildir/%f`
> 
> ...it's actually, ~/Maildir/%f and *not* ~/Maildir/submaildir
> that's being passed to the bash script.

Well, yeah. The backticks are being evaluated when mutt starts, not when
viewing a folder. So of course, %f cannot be expanded because mutt can't
possibly know what it is.

-- 
Rob 'Feztaa' Park
http://members.shaw.ca/feztaa/
--
It's simply unbelievable how much energy and creativity people have
invested into creating contradictory, bogus and stupid licenses...
--- Sven Rudolph about licences in debian/non-free.



msg29319/pgp0.pgp
Description: PGP signature

Passing muttrc format strings to bash

[Lee J. Moore]

Is this possible or impossible?  I switched to Maildir a couple
of months ago after years of using mbox and I finally got around
to completely rewriting my muttrc to try to take advantage of
Maildirs different little quirks.

In the index_format (muttrc) variable, I'd like to pass each of
my sub-Maildir's to a bash script so that I can calculate the
new, deleted and total number of messages - for each sub-Maildir
- and put it in the message index.  However, when I call my bash
script, the %f (of course) isn't being expanded.  If, in my
index_format, I have this:

`~/bin/maildir-count ~/Maildir/%f`

...it's actually, ~/Maildir/%f and *not* ~/Maildir/submaildir
that's being passed to the bash script.
-- 
Lee J. Moore
[EMAIL PROTECTED]



msg29317/pgp0.pgp
Description: PGP signature

Re: save-hook command problems in .muttrc

[munk]

On Tue, May 14, 2002 at 11:41:28AM +0200, Martin Karlsson wrote:
> Hmm. I'm not sure it works that way. Look for something specific in
> the mail (just like when writing a procmail recipe). I have:
> 
> save-hook "~h owner-mutt-users" +s.mutt-users
> save-hook "(~f pal1|~f pal2)" +s.pal1_and_2
> 
> The ~h tells mutt to look in the headers, and the ~f matches 'from'.
> Study the manual carefully to find more ways of doing this!
Hey Martin,

Thanks a lot for the reply - as you probably see from my reply ^^ in list I just about 
got it sussed out now and it works a treat with the ~t descriptor(?), searching for 
[mM]utt - thanx anyway!

Jez
:))
-- 
http://munkboxen.mine.nu - FreeBSD network
http://www.freebsd.org

Re: save-hook command problems in .muttrc - pattern required

[Cedric Duval]

* Sven Guckes <[EMAIL PROTECTED]> [05/14/02 06:02]:
> * munk <[EMAIL PROTECTED]> [2002-05-13 23:14]:
> > I'm having trouble getting the 'save-hook' command
> > to work properly in my .muttrc file.
> > The current settings I have look as follows:
> > 
> >   save-hook mutt +mutt-users-list
> >   save-hook bugtraq +bugtraq-list
> >
> > but whenever I press 's' to save a mail that
> > includes 'mutt' or 'bugtraq' in the 'From' header
> > field, the default 'save' folder selected is never
> > 'mutt-users-list' or 'bugtraq-list' respectively.
> >
> > I can't work this out at all - does anyone
> > else use the save-hook function with joy?

> make the first parameter a pattern:

Yes. Otherwise, without explicitly specifying a pattern, it is be
expanded according to the value of $default_hook.
("~f %s !~P | (~P ~C %s)" by default).

-- 
Cedric

Re: save-hook command problems in .muttrc

[Martin Karlsson]

* munk <[EMAIL PROTECTED]> [2002-05-14 00.12 +0100]:
> Hi,
 
Hello!

> I'm having trouble getting the 'save-hook' command to work properly in my .muttrc 
>file.
> 
> The current settings I have look as follows:
> 
>   save-hook mutt +mutt-users-list
>   save-hook bugtraq +bugtraq-list

Hmm. I'm not sure it works that way. Look for something specific in
the mail (just like when writing a procmail recipe). I have:

save-hook "~h owner-mutt-users" +s.mutt-users
save-hook "(~f pal1|~f pal2)" +s.pal1_and_2

The ~h tells mutt to look in the headers, and the ~f matches 'from'.
Study the manual carefully to find more ways of doing this!

HTH
-- 
Martin Karlsson   _
GPG/PGP public key: 0x9C924660 ASCII ribbon campaign ( )
   -against HTML, vCards and  X
  -proprietary attachments in e-mail / \



msg28083/pgp0.pgp
Description: PGP signature

Re: save-hook command problems in .muttrc - pattern required

[Sven Guckes]

* munk <[EMAIL PROTECTED]> [2002-05-13 23:14]:
> I'm having trouble getting the 'save-hook' command
> to work properly in my .muttrc file.
> The current settings I have look as follows:
> 
>   save-hook mutt +mutt-users-list
>   save-hook bugtraq +bugtraq-list
>
> but whenever I press 's' to save a mail that
> includes 'mutt' or 'bugtraq' in the 'From' header
> field, the default 'save' folder selected is never
> 'mutt-users-list' or 'bugtraq-list' respectively.
>
> I can't work this out at all - does anyone
> else use the save-hook function with joy?

make the first parameter a pattern:

save-hook "~f mutt"  +mutt-users-list
save-hook "~f bugtraq"   +bugtraq-list

you might want to identify messages *to* mailing list
by their distribution address, though:

save-hook "~C address1"  +mutt-users-list
save-hook "~C address2"  +bugtraq-list

enjoy!

> Also I'm not sure of the difference
> between +file and =file - is there any???

yes - spelling.  they are synonyms.
however, "+foo" and "=foo" might
not be synonyms to your shell...

> Are = and + expanded to ~ in all cases???

no - they are expanded to $folder.

> From: munk <[EMAIL PROTECTED]>

and get a hair cut.. mink.. munk.. whatever.

Sven

save-hook command problems in .muttrc

[munk]

Hi,

I'm having trouble getting the 'save-hook' command to work properly in my .muttrc file.

The current settings I have look as follows:

save-hook mutt +mutt-users-list
save-hook bugtraq +bugtraq-list

but whenever I press 's' to save a mail that includes 'mutt' or 'bugtraq' in the 
'From' header field, the default 'save' folder selected is never 'mutt-users-list' or 
'bugtraq-list' respectively. I can't work this out at all - does anyone else use the 
save-hook function with joy?

Also I'm not sure of the difference between +file and =file - is there any??? Are = 
and + expanded to ~ in all cases???

Many thanks in advance,
Jez

-- 
http://munkboxen.mine.nu - FreeBSD network
http://www.freebsd.org

Re: .muttrc config help.

[David T-G]

Matt --

...and then DARCY,MATTHEW (Non-HP-UnitedKingdom,ex2) said...
% 
% Dave, 

Um, "David", if you please :-)  If you've found "Dave" anywhere on my
site or in my email to mislead you, please let me know I've been hacked.


% 
% thanks for taking the time to reply to me on this matter.

Sure thing!


% 
% My backups are much better, the machine I was using mutt on was a
% development box, so I was just playing with it and wasn't really bothered

Heh.  They all start that way :-)


% about backups until I went to far...and destoryed it. The same backup
% system as on my production machines is now in place. 

*grin*


% 
% You suggestions to the muttrc file are excellent and just what I was looking
% for. I'll implement them ASAP. 

Happy to help!


% 
% Yes I am using out look at 1 of the offices I work in, but then again it is
% the clients choice what mail client I use when on site. 

Haven't you gotten mutt set up to talk IMAP to your exchange server so
that you can use Real Mail when you want to? :-)


% 
% I am a firm user off mutt at home and in my parent companys office hence why
% I would like to get it right.

Makes sense.


% 
% 
% Believe me, I searched the web for a muttrc file that had all of the
% functions in I needed, and I manged to get some of the variables, I even
% used the muttrc generator script on the web (didn't like that at all)
% and could not find a couple of missing parameters.

Take time, grasshopper.  RTFM.


% 
% so once again thanks for the help.

Sure thing!


% 
% Matt.


:-D
-- 
David T-G  * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!




msg28037/pgp0.pgp
Description: PGP signature

RE: .muttrc config help.

[DARCY,MATTHEW \(Non-HP-UnitedKingdom,ex2\)]

Dave, 

thanks for taking the time to reply to me on this matter.

My backups are much better, the machine I was using mutt on was a
development box, so I was just playing with it and wasn't really bothered
about backups until I went to far...and destoryed it. The same backup
system as on my production machines is now in place. 

You suggestions to the muttrc file are excellent and just what I was looking
for. I'll implement them ASAP. 

Yes I am using out look at 1 of the offices I work in, but then again it is
the clients choice what mail client I use when on site. 

I am a firm user off mutt at home and in my parent companys office hence why
I would like to get it right.


Believe me, I searched the web for a muttrc file that had all of the
functions in I needed, and I manged to get some of the variables, I even
used the muttrc generator script on the web (didn't like that at all)
and could not find a couple of missing parameters.

so once again thanks for the help.

Matt.


-Original Message-
From: David T-G [mailto:[EMAIL PROTECTED]]
Sent: Monday, May 13, 2002 2:29 PM
To: Mutt Users' List
Cc: DARCY,MATTHEW (Non-HP-UnitedKingdom,ex2)
Subject: Re: .muttrc config help.


Matt --

...and then DARCY,MATTHEW (Non-HP-UnitedKingdom,ex2) said...
% 
% hi,

Hello!


% 
% I have lost my .muttrc config file.

Ouch.  Better backups next time!


% 
% there is a couple of variables which I am having trouble resetting in my
new
% file.
% 
% 
% to view my mail box I have to type "mutt -f ~/Maildir" 
% 
% what variables do I have to set to make this happen in my .muttrc file ??

I presume you probably want

  set folder=$HOME/Mail
  set spoolfile=$HOME/Maildir

so that you need only type "mutt" to start reading your maildir and so
that the '=' shortcut will point to your Mail dir.


% 
% also my mail server is,  "mail.mydomain.co.uk" so mail I send comes from
% [EMAIL PROTECTED] how do I set it to come from [EMAIL PROTECTED]

You probably want either

  set from="[EMAIL PROTECTED]"

or

  my_hdr From: "Me <[EMAIL PROTECTED]"

or possibly

  set hostname=mydomain.co.uk

but only you can decide.


% 
% 
% Pretty simple I know but I have not got a reference point.

Well, you have, actually...  There's the well-commented system Muttrc
file, the manual, and the web site, not to mention countless example
muttrc files out there.  Of course, you're using LookOut! (well, a
variant) to send this, so you actually deserve *no* mercy ;-)


% 
% Thanks, 
% 
% Matt.


HTH & HAND

:-D
-- 
David T-G  * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!

Re: .muttrc config help.

[David T-G]

Matt --

...and then DARCY,MATTHEW (Non-HP-UnitedKingdom,ex2) said...
% 
% hi,

Hello!


% 
% I have lost my .muttrc config file.

Ouch.  Better backups next time!


% 
% there is a couple of variables which I am having trouble resetting in my new
% file.
% 
% 
% to view my mail box I have to type "mutt -f ~/Maildir" 
% 
% what variables do I have to set to make this happen in my .muttrc file ??

I presume you probably want

  set folder=$HOME/Mail
  set spoolfile=$HOME/Maildir

so that you need only type "mutt" to start reading your maildir and so
that the '=' shortcut will point to your Mail dir.


% 
% also my mail server is,  "mail.mydomain.co.uk" so mail I send comes from
% [EMAIL PROTECTED] how do I set it to come from [EMAIL PROTECTED]

You probably want either

  set from="[EMAIL PROTECTED]"

or

  my_hdr From: "Me <[EMAIL PROTECTED]"

or possibly

  set hostname=mydomain.co.uk

but only you can decide.


% 
% 
% Pretty simple I know but I have not got a reference point.

Well, you have, actually...  There's the well-commented system Muttrc
file, the manual, and the web site, not to mention countless example
muttrc files out there.  Of course, you're using LookOut! (well, a
variant) to send this, so you actually deserve *no* mercy ;-)


% 
% Thanks, 
% 
% Matt.


HTH & HAND

:-D
-- 
David T-G  * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!




msg28035/pgp0.pgp
Description: PGP signature