qmail and From:

2000-01-29 Thread Patrick Walsh
As far as I can tell setting the From: when using qmail with mutt requires that the environment variables MAILUSER, MAILHOST, MAILNAME be set before starting mutt, along with QMAILINJECT=f. Is there a way to set the From: within a mutt session when using qmail as the MTA? -- Patrick Walsh

Re: qmail and From:

2000-01-29 Thread Mikko Hänninen
Patrick Walsh [EMAIL PROTECTED] wrote on Fri, 28 Jan 2000: As far as I can tell setting the From: when using qmail with mutt requires that the environment variables MAILUSER, MAILHOST, MAILNAME be set before starting mutt, along with QMAILINJECT=f. It doesn't require them, though can specify

Procmail Bug and PGP/GPG

2000-01-29 Thread Christopher Uy
Hello, I've been using mutt for sometime now, but just signed up for this list today, so I apologize if this has already been discussed. :-) There is a bug in the current version of procmail (3.14 - not sure if it goes back further than that) that does not allow the procmail recipe supplied in

Re: qmail and From:

2000-01-29 Thread Jim Breton
I've been doing this on my qmail system; however, qmail still puts a "Return-Path" header on the message which indicates the local username who called "sendmail." I haven't found any way around this yet. You can set the $QMAILUSER and $QMAILHOST env vars to specify what you want in the

folder-hook not executed with mutt -f cmdline

2000-01-29 Thread Jim Breton
Hi, it seems that my folder hooks are not run when I load a specific folder from the command line. For instance, I have a folder hook that looks like this: folder-hook =mutt "my_hdr From: Jim Breton [EMAIL PROTECTED]" But if I load mutt like this: mutt -f ~/mail/mutt It does not set

Re: qmail and From:

2000-01-29 Thread Mikko Hänninen
Jim Breton [EMAIL PROTECTED] wrote on Sat, 29 Jan 2000: I've been doing this on my qmail system; however, qmail still puts a "Return-Path" header on the message which indicates the local username who called "sendmail." I haven't found any way around this yet. Ahh. That's the envelope

Re: qmail and From:

2000-01-29 Thread Jim Breton
Haha -- guess what. :) Just on a whim I tried setting the Return-Path with a "my_hdr" command and qmail did honor it! Perfect! I was all excited about it, but you beat me to the punch. :) Thanks! On Sat, Jan 29, 2000 at 08:42:58PM +0200, Mikko Hänninen wrote: Jim Breton [EMAIL

Re: folder-hook not executed with mutt -f cmdline

2000-01-29 Thread Jon Miner
* Jim Breton ([EMAIL PROTECTED]) [000129 12:40]: folder-hook =mutt "my_hdr From: Jim Breton [EMAIL PROTECTED]" But if I load mutt like this: mutt -f ~/mail/mutt A guess (untested because I don't have time right now to test it) is that it's noticing that "~/mail/mutt" != "=mutt",

line wrap

2000-01-29 Thread Jim Breton
Quick question. Do people generally find it annoying if I don't use line wrap in my editor (vim)? I see that most other people on this list appear to be using line wrap in their editors, I always left mine disabled figuring the client's reader/pager would handle the wrapping. Is this a bad

Re: qmail and From:

2000-01-29 Thread Patrick Walsh
* Jim Breton [EMAIL PROTECTED] Sat Jan 29 13:18 -0500: I've been doing this on my qmail system; however, qmail still puts a "Return-Path" header on the message which indicates the local username who called "sendmail." I haven't found any way around this yet. You can set the $QMAILUSER and

(forw) fcc's to sent

2000-01-29 Thread Jason Helfman
I am not sure why this is happening, but I would like all mail I send to only go to "sent" folder inside of my Mailbox (~/Msgs). ~/Mail is symlinked to ~/Msgs for Procmail. I have a referrece of "set record = +sent" However mail likes to go to "clug", for a mailing list, and to "Sent". I

Re: folder-hook not executed with mutt -f cmdline

2000-01-29 Thread Jim Breton
Yep you were right. Thanks. :) Btw, this leads me to another question. Suppose I have two folders, one called "mutt" and the other one is "mutt-sent" If I want to trigger a command in the "mutt" folder but not in "mutt-sent" how can I do this? The hook seems to make a match on either one.

Re: line wrap

2000-01-29 Thread David T-G
Jim -- ...and then Jim Breton said... % Do people generally find it annoying if I don't use line wrap in my editor Actually, yes. It's only because everyone here is so polite that you haven't been flamed for it already, but it's a pretty big peeve. Oh, wait; this is the mutt-users list. I

[jamesb-mutt@alongtheway.com: look Ma, no Pine]

2000-01-29 Thread Jim Breton
Sorry if anyone gets this twice. I sent it yesterday but for some reason it didn't show up on the list, and a couple msgs I wrote just a few mins ago have already shown up so I figure it's pretty safe to say this msg got lost somehow. I'm also taking this opportunity to add another question.

Re: folder-hook not executed with mutt -f cmdline

2000-01-29 Thread Mikko Hänninen
Jim Breton [EMAIL PROTECTED] wrote on Sat, 29 Jan 2000: If I want to trigger a command in the "mutt" folder but not in "mutt-sent" how can I do this? The hook seems to make a match on either one. I've tried "mutt" and "=mutt" for the hook. There must be some regexp pattern that would get

Re: Procmail Bug and PGP/GPG

2000-01-29 Thread Terje Elde
* Christopher Uy ([EMAIL PROTECTED]) [000129 20:17]: Will lose a whitespace before the colon. I was pulling my hair out for a while trying to find out why some of my signed messages were coming back with bad signature errors. I have no problems with the mentioned procmail version under

Re: (forw) fcc's to sent

2000-01-29 Thread Mikko Hänninen
Jason Helfman [EMAIL PROTECTED] wrote on Sat, 29 Jan 2000: Date: Sat, 29 Jan 2000 12:30:04 -0600 From: Jason Helfman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: fcc's to sent Hmmm, as a tip, if you want a remail a message originally sent to a different address, you can b(ounce) it, no

Re: [jamesb-mutt@alongtheway.com: look Ma, no Pine]

2000-01-29 Thread Mikko Hänninen
Jim Breton [EMAIL PROTECTED] wrote on Sat, 29 Jan 2000: As some of you may remember I just "discovered" Mutt only a few days ago. Well, those few days have been awesome, Mutt is unbelievable! I'm glad you think so. And I wholeheartedly agree! :-) I do have a few questions though. :)

Re: line wrap

2000-01-29 Thread Marius Gedminas
On Sat, Jan 29, 2000 at 02:31:20PM -0500, David T-G wrote: ...and then Jim Breton said... % Do people generally find it annoying if I don't use line wrap in my editor Actually, yes. It's only because everyone here is so polite that you haven't been flamed for it already, but it's a pretty

Re: Procmail Bug and PGP/GPG

2000-01-29 Thread Christopher Uy
On Sat, Jan 29, 2000 at 09:08:57PM +0100, Terje Elde wrote: I have no problems with the mentioned procmail version under FreeBSD. I'm able to handle both encrypted and signed messages. The only patch applied by the FreeBSD port system to the source code itself is in recommend.c, thus it

Re: Procmail Bug and PGP/GPG

2000-01-29 Thread Terje Elde
* Christopher Uy ([EMAIL PROTECTED]) [000129 23:06]: Try signing the following in-line - without using mutt's built in PGP handling. E-Mail : [EMAIL PROTECTED] When it's signed in-line and flows through procmail, the body get rewritten to: E-Mail: [EMAIL PROTECTED]

Re: Procmail Bug and PGP/GPG

2000-01-29 Thread Christopher Uy
On Sat, Jan 29, 2000 at 11:19:48PM +0100, Terje Elde wrote: I'm really tired, but unless I've misunderstood something, you wanted: I was too literal with my writing. :-) I indented the example out of habit. :-) Do what you did, but put it at the beginning of the line with no indentation:

Re: Procmail Bug and PGP/GPG

2000-01-29 Thread Terje Elde
* Christopher Uy ([EMAIL PROTECTED]) [000130 01:25]: On Sat, Jan 29, 2000 at 11:19:48PM +0100, Terje Elde wrote: I'm really tired, but unless I've misunderstood something, you wanted: I was too literal with my writing. :-) I indented the example out of habit. :-) Do what you did,

Re: Procmail Bug and PGP/GPG

2000-01-29 Thread Christopher Uy
PGP message

Using procmail to help mutt read old-style PGP (was Re: Procmail Bug and PGP/GPG)

2000-01-29 Thread Bennett Todd
2000-01-29-19:41:36 Christopher Uy: In the mean while, adding that 'h' flag to your rule should get you by until then. Since the "h" makes it more efficient, it seems like a good idea to include anyway. Here's what I'm using these days, purely swiped from the PGP-Notes.txt that comes with

Pine Role type features

2000-01-29 Thread Jander Sunstar
Does anyone know if there is a hack/patch for mutt to enable the Role selection as in Pine ? I have a need to answer email based on the sender and respond as various addreses andneed to do so quickly. Any Ideas? Jander Sunstar [EMAIL PROTECTED] - "Watch the Watchers"

Re: line wrap

2000-01-29 Thread -kevin-
My two cents on formatting... On 00-01-29 23:31, Marius Gedminas wrote: There's one more reason: mutt and vim (and I think this is the most Formatting made easy with vim... Try this: set editor=vim_for_mutt Script vim_for_mutt: #!/usr/local/bin/bash if [ $# -ne 1 ] then echo "Usage: $0

Printing...?

2000-01-29 Thread Jason Helfman
Got this error, when trying to print sh: mp: command not found lpr: stdin: empty input file Press any key to continue... when it exited to the shell, came back, doesn't look like anything went to spool

Re: (forw) fcc's to sent

2000-01-29 Thread Jason Helfman
$record certainly is the default fcc location specification. The other two variables that might affect things are $save_name and $force_name. Do you have them set, perhaps? (Check with ":set ?save_name") They both are unset by default. I tried an fcc-hook to rememdy the problem, in my