[EMAIL PROTECTED] muttered:
> It's quite a large amount of matter to go through. When I look at
> section 6.3, which has 209 config options by itself... It is easy to
> get lost in there.
True, but that's what makes mutt such a flexible MTA. Just go through the
variables section and see whether y
It was Oct 7, 2000, 12:34, when Jamie Novak keyboarded:
>On 10/07, [EMAIL PROTECTED] rearranged the electrons to read:
>
>> I already did, and I found this fcc-hook there. It's quite a large amount of
>> matter to go through. When I look at section 6.3, which has 209 config options
>> by itself..
On 10/07, [EMAIL PROTECTED] rearranged the electrons to read:
> I already did, and I found this fcc-hook there. It's quite a large amount of
> matter to go through. When I look at section 6.3, which has 209 config options
> by itself... It is easy to get lost in there.
Have you considered using
On Sat, Oct 07, 2000 at 05:54:31PM +0200, Michael Tatge keyboarded:
>Will you ever start reading the manual?
I already did, and I found this fcc-hook there. It's quite a large amount of
matter to go through. When I look at section 6.3, which has 209 config options
by itself... It is easy to get l
Will you ever start reading the manual?
[EMAIL PROTECTED] muttered:
> fcc-hook . +sent-mail
I'd rather use $record.
> A funny thing though: the sent-mail mailbox is created in ~/Mail.
> In .muttrc I set mbox=~/mail # without capital m.
First of all this is a mailfolder in mbox format - a file
Hello all,
I am still venturing into the world of Mutt.
There is a little thing I don't get my fingers on. I have put a command in
.muttrc like this:
fcc-hook . +sent-mail
Mutt does not complain about this, which is good. A funny thing though: the
sent-mail mailbox is created in ~/Mail. In .mut
