Re: fcc and reply as in pine

2002-08-29 Thread Richard P. Groenewegen
On Thu, Aug 29, 2002 at 09:22:25AM -0400, darren chamberlain wrote: > Ouch, that's a lot of work. I think this will do it: > > fcc-save-hook . +%O > > The . applies the hook to all messages, and the %O turns into the > before-the-@ part of the recipient address. Cool! I didn't known this (w

fcc and reply as in pine

2002-08-29 Thread Richard P. Groenewegen
Hi, I have just converted a friend from using pine to mutt. But there is still one features he misses and I would feel stupid saying: `well, this is nog the way we do things in mutt.' When he replies to someguy@somewhere he wants the outgoing email to be saved in =someguy. I thought abou

just another send-hook question

1999-11-11 Thread Richard P. Groenewegen
Hi, Here's something that's either trivial or impossible. I want something like send-hook '~t [EMAIL PROTECTED]' '' but I'll only want this send-hook to work if [EMAIL PROTECTED] is the only recipient. On a related note: how do I limit to all messages send to [EMAIL PROTECTED] but

editing entire header?

1999-10-04 Thread Richard P. Groenewegen
Hi, When I press e to edit a message it also allows me to edit some of the headers. But some, notably the "References" header line, is left out. What is the reasoning for not allowing me to edit the References and are there other headers that don't show up when I edit a message? Richard -- Sol

And then suddenly it does not work anymore

1999-09-25 Thread Richard P. Groenewegen
On Sun, Sep 26, 1999 at 03:16:29AM +0200, Richard P. Groenewegen wrote: > The following solution is kind of a hack, but you might like it. If > have tested the code a little, but be careful with it. It is probably > not that robust yet. And it sure wasn't. When I tested it I

Re: email threading

1999-09-25 Thread Richard P. Groenewegen
On Sun, Sep 26, 1999 at 01:04:12AM +0200, Stasinos Konstantopoulos wrote: > I do have strict_threads set, and I think it's a good thing to have it > so, but I would also like to be able to manually, explicitly add the > odd message to a thread if I need to. The following solution is kind of a hac

Re: Fcc question

1999-09-24 Thread Richard P. Groenewegen
> > I think he wants to save a FCC into *both* mailboxes for every message. > > And no, I don't know how to do that. :-( > The solution I would use would be to do something like the following: > > my_hdr X-OutboundMultiStore: mailbox_target_name > # or some other unique header > > And then just

Fcc question

1999-09-24 Thread Richard P. Groenewegen
Hi, I've asked this question before, but I didn't get any answers (no hard feelings). I still don't know how to do it. I want to save some of my outgoing message in two different mailboxes, so I want to say something like Fcc: =outbox, =some_other_box Of course, this doesn't work (at least

saving mail in two places

1999-08-04 Thread Richard P. Groenewegen
Hi, I'm using mutt for some time now and I'm used to saving all my outgoing mail (set copy=yesset record=+outbox). But now I want to save all messages going to foo@bar in the mailbox +foo also. So, I want to save these message in two mailboxes, but mutt does not seem to allow this. The

Re: limit question

1999-04-19 Thread Richard P. Groenewegen
On Sat, Apr 17, 1999 at 11:36:27AM +0200, Michael Thies wrote: > Bevan Broun hat ueber "Re: limit question" geschrieben: > > > Odd. I always just "l all". > > > > "l *" is shorter. > > But it shows me, that all messages are limited. And when using "l all" > I get the normal state back, i.e. un