Re: Has the handling of my_hdr and send_hook changed between 1.10.x and 2.1.4?

On Mon, Apr 10, 2023 at 07:06:14PM +0100, Chris Green wrote: On Mon, Apr 10, 2023 at 06:45:04PM +0100, Chris Green wrote: I'll try to narrow this down further by trying a very short list of mailing list names. After a bit of chopping and changing the list of addresses in 'lists' I finally spo

Re: Has the handling of my_hdr and send_hook changed between 1.10.x and 2.1.4?

On Mon, Apr 10, 2023 at 06:45:04PM +0100, Chris Green wrote: > > I'll try to narrow this down further by trying a very short list of > mailing list names. > After a bit of chopping and changing the list of addresses in 'lists' I finally spotted my problem. Totally my fault, my program that gener

Re: Has the handling of my_hdr and send_hook changed between 1.10.x and 2.1.4?

OK, I now know what was working (in 1.10.1) and now isn't working the way it did. If I put the following in my muttrc:- lists mutt-users@mutt.org subscribe mutt-users@mutt.org Then my send-hooks setting a different From: for mutt-users@mutt.org work as expected in both 1.10.1 and 2.1.4.

Re: Has the handling of my_hdr and send_hook changed between 1.10.x and 2.1.4?

s I don't have access to. Please, when I say minimal, I mean > *minimal*. > > I have tested against latest git with this muttrc: > > lists mutt-users@mutt.org > subscribe mutt-users@mutt.org > set my_addr = 'ch...@isbd.co.uk' > send-hook . 'my_hd

Re: Has the handling of my_hdr and send_hook changed between 1.10.x and 2.1.4?

sbd.co.uk' send-hook . 'my_hdr From: Chris Green <$my_addr>' send-hook ~l 'my_hdr From: Chris Green ' I invoke mutt with 'mutt -F cgreen.muttrc', type 'm', enter mutt-users@mutt.org at the To prompt. After the subject prompt and editor complete,

Re: Has the handling of my_hdr and send_hook changed between 1.10.x and 2.1.4?

>still runs mutt 1.10.4 and there my send-hook/my_hdr configuration > >works. It doesn't work on my current mutt 2.1.4. > > Not knowingly, but a lot of the sending code has been modified in that > period of time. > > >I see the documentation now says "Also not

Re: Has the handling of my_hdr and send_hook changed between 1.10.x and 2.1.4?

On Sun, Apr 09, 2023 at 08:23:55PM +0100, c...@isbd.net wrote: I'm trying to sort out why something that used to work for me no longer works. I just went and tried out an older installation that still runs mutt 1.10.4 and there my send-hook/my_hdr configuration works. It doesn't

Has the handling of my_hdr and send_hook changed between 1.10.x and 2.1.4?

I'm trying to sort out why something that used to work for me no longer works. I just went and tried out an older installation that still runs mutt 1.10.4 and there my send-hook/my_hdr configuration works. It doesn't work on my current mutt 2.1.4. I see the documentation now says "

Re: trouble with my_hdr and $format_flowed [SOLVED]

On 02Sep2022 15:27, Cameron Simpson wrote: On 01Sep2022 20:18, Kevin J. McCarthy wrote: I'm not sure if it helps at this point, but I can report that I've taken your template above and passed it to 'mutt -H' and the resulting sent file has format=flowed in its content-type header. :-/ Can yo

Re: trouble with my_hdr and $format_flowed

On 01Sep2022 20:18, Kevin J. McCarthy wrote: >On Fri, Sep 02, 2022 at 08:28:01AM +1000, Cameron Simpson wrote: >>and the file ~/var/mutt/mutt-fleet2-501-83365-16591433053586932493 >>passwd to "mutt -H" is already gone. Does mutt remove it? >> >>Ah, mutt might have move it to ~/var/mutt/compose/mut

Re: trouble with my_hdr and $format_flowed

On Fri, Sep 02, 2022 at 08:28:01AM +1000, Cameron Simpson wrote: and the file ~/var/mutt/mutt-fleet2-501-83365-16591433053586932493 passwd to "mutt -H" is already gone. Does mutt remove it? Ah, mutt might have move it to ~/var/mutt/compose/muttedit.94328, which exists with the header above. Let

Re: trouble with my_hdr and $format_flowed

rset=utf-8; format=flowed From: Cameron Simpson To: mutt-users@mutt.org Cc: Bcc: c...@cskk.id.au Subject: Re: trouble with my_hdr and $format_flowed Reply-To: In-Reply-To: and the Content-Type is not presented in this current editor. Interestingly, the process tree lo

Re: trouble with my_hdr and $format_flowed

On 01Sep2022 09:09, Kevin J. McCarthy wrote: >On Wed, Aug 31, 2022 at 06:45:08PM -0700, Kevin J. McCarthy wrote: >>In my testing, a header 'Content-Type: text/plain; format=flowed' in >>the draft file does result in the sent email being format=flowed. > >My example wasn't great: you *should* add

Re: trouble with my_hdr and $format_flowed

On Wed, Aug 31, 2022 at 06:45:08PM -0700, Kevin J. McCarthy wrote: In my testing, a header 'Content-Type: text/plain; format=flowed' in the draft file does result in the sent email being format=flowed. My example wasn't great: you *should* add a charset parameter set to your system charset (I'

Re: trouble with my_hdr and $format_flowed

On Thu, Sep 01, 2022 at 08:50:33AM +1000, Cameron Simpson wrote: On 31Aug2022 15:37, Kevin J. McCarthy wrote: I think this may work best for you, if the my_hdr approach doesn't work. It seems to have no effect; the Content-Type eg from my reply just now to you is still not format=flow

Re: trouble with my_hdr and $format_flowed

On 01Sep2022 08:50, Cameron Simpson wrote: >>If you haven't played with it before, you might also look into >>background editing and the contrib/bgedit-screen-tmux.sh script. See >>. > >I will; the background editing feature postdated my tmux games. I don'

Re: trouble with my_hdr and $format_flowed

has no effect then, but I seem to have no other way to >>apply the needed header - adding it by hand during composition is >>ineffective. >> >>I _might_ do better adding it to the copy before starting the separate >>mutt; I'll see if that works. > >I think th

Re: trouble with my_hdr and $format_flowed

On 31Aug2022 15:28, Kevin J. McCarthy wrote: >The parser for my_hdr is a bit different - it allows quote characters >in the header, so it doesn't treat them specially like elsewhere. >However, semicolons are still parsed normally. Ah, right. >I think this was a mistak

Re: trouble with my_hdr and $format_flowed

ded header - adding it by hand during composition is ineffective. I _might_ do better adding it to the copy before starting the separate mutt; I'll see if that works. I think this may work best for you, if the my_hdr approach doesn't work. Content-Type and other MIME headers aren

Re: trouble with my_hdr and $format_flowed

On Thu, Sep 01, 2022 at 08:08:21AM +1000, Cameron Simpson wrote: I forgot the my_hdr issue. This line: my_hdr "Content-Type: teAxt/plain; charset=usascii; format-flowed" results in this from from mutt at startup: Error in /Users/cameron/rc/mutt/settings, line 129: chars

Re: trouble with my_hdr and $format_flowed

On 31Aug2022 18:06, David Lowry-Duda wrote: >>I have a pretty weird way of composing replies and new messages: I like >>to be able to detach from the new message window. So I compose in a >>separate tmux session. > >If you compose directly in mutt+vim without composing in a separate >tmux window,

Re: trouble with my_hdr and $format_flowed

I forgot the my_hdr issue. This line: my_hdr "Content-Type: text/plain; charset=usascii; format-flowed" results in this from from mutt at startup: Error in /Users/cameron/rc/mutt/settings, line 129: charset=usascii: unknown command So it appears that I can't use a semi

Re: trouble with my_hdr and $format_flowed

I have a pretty weird way of composing replies and new messages: I like to be able to detach from the new message window. So I compose in a separate tmux session. If you compose directly in mutt+vim without composing in a separate tmux window, does it work? (I would assume so, as I use mutt+vim

Re: trouble with my_hdr and $format_flowed

On 01Sep2022 07:58, Cameron Simpson wrote: >I've put a format=flowed into this message by hand, and I'll see if it >survives. It did not. The message sent by mutt discarded my Content-Type header and used: Content-Type: text/plain; charset=us-ascii So I've actually got a significant proble

trouble with my_hdr and $format_flowed

I've long had my mutt+vim setup to compose format=flowed email. There's just one problem: it wasn't working. So I'm digging into why. I've got: set text_flowed=yes in my setup. And if I pare down enough mutt settings, my reply goes out with this header: Content-Type: text/plain; chars

Re: Always CC specific messages to some people (send-hook and my_hdr)

ot; basis. So I could use it to put my coworkers in an alias, but they would be in the "To:" field, not "CC". I wanted to use a send-hook and the my_hdr variable, but it works for other fields (such as adding a "Organization: A Really Big Company, Anytown, USA", fr

Re: Always CC specific messages to some people (send-hook and my_hdr)

dent, and I would like my exchanges with the student > to be sent to others. > > Mutt aliases seems to be on a "per field" basis. So I could use it to > put my coworkers in an alias, but they would be in the "To:" field, > not "CC". > > I wanted

Re: Always CC specific messages to some people (send-hook and my_hdr)

t;to be sent to others. > >Mutt aliases seems to be on a "per field" basis. So I could use it to put my >coworkers in an alias, but they would be in the "To:" field, not "CC". > >I wanted to use a send-hook and the my_hdr variable, but it works for other >

Always CC specific messages to some people (send-hook and my_hdr)

"per field" basis. So I could use it to put my coworkers in an alias, but they would be in the "To:" field, not "CC". I wanted to use a send-hook and the my_hdr variable, but it works for other fields (such as adding a "Organization: A Really Big Company, Anyto

Suppress my_hdr in compose window

Hello list, is there a way to define which headers show up in the compose window if edit_headers is set? For example I want to see the normal From, To and Subject headers. But not the extra headers defined with my_hdr X-URL or X-PGP-Key. Nevertheless these extra headers should be send. Is this

Can I use my_hdr from a macro?

I want to create a macro in 'compose' which does something like the following:- Set From: to something special Send the message Set From: back to the default I can't quite see how to do this, how can one use my_hdr from a macro? my_hdr isn't a function is it? .

Re: my_hdr text (between parens) not used

hostname=example.net; \ my_hdr From: Flavius (Example Support) " If I remove the parens then "Example Support" appears in the header. What is going on here? I think this is mutt's overly strict (pedantic?) interpretation of RFC 2822 (or whatever is the current version), se

Re: my_hdr text (between parens) not used

On 06Sep2015 07:40, Cameron Simpson wrote: Actually, on reading section 4 from RFC 2822 "Obsolete Grammar", mutt should parse your From: line but _not_ emit it unchanged. Obsolete grammar is meant to be accepted and understood but not generated. And just to witter on, section 4 says in part:

Re: my_hdr text (between parens) not used

On 06Sep2015 07:35, Cameron Simpson wrote: On 05Sep2015 09:19, Ian Zimmerman wrote: I think this is mutt's overly strict (pedantic?) interpretation of RFC 2822 (or whatever is the current version), section 3.4 (Address Specification). That section says that an address is in one _and only one_

Re: my_hdr text (between parens) not used

On 2015-09-05 09:19 -0700, Ian Zimmerman wrote: > > my_hdr From: Flavius (Example Support) " > I think this is mutt's overly strict (pedantic?) interpretation of RFC > 2822 (or whatever is the current version), section 3.4 (Address > Specification). That section s

Re: my_hdr text (between parens) not used

On 2015-09-05 16:25 +0200, Louis-David Mitterrand wrote: > Hi, > > When this reply-hook is applied the text between parens doesn't appear > in replies: > > reply-hook '~h((X-Original-)?To\|From):.+(contact\|info)@example.net' \ > "set hostname=ex

my_hdr text (between parens) not used

Hi, When this reply-hook is applied the text between parens doesn't appear in replies: reply-hook '~h((X-Original-)?To\|From):.+(contact\|info)@example.net' \ "set hostname=example.net; \ my_hdr From: Flavius (Example Support) " If I remove the par

Re: Send-hook "set my_hdr" Not Working as Expected

On Thu, May 10, 2012 at 09:28:03PM +0100, Koralatov wrote: On Thu, May 10, 2012 at 19:09, Ed Blackman wrote: I use this pattern: send-hook . my_hdr "From: " send-hook "~t @mutt.org" my_hdr "From: " send-hook "~t @ex

Re: Send-hook "set my_hdr" Not Working as Expected

On Wed, May 09, 2012 at 10:47:58PM +0100, Koralatov wrote: send-hook * "unmy_hdr From:" send-hook * "my_hdr From: Michael Graham " send-hook @mutt.org "unmy_hdr From:" send-hook @mutt.org "my_hdr From: Koralatov

Re: Send-hook "set my_hdr" Not Working as Expected

Koralatov wrote, on Wed, May 09, 2012 at 10:49:18PM +0100: > [snip] > >I thought I'd fixed it by using the following: > > send-hook * "unmy_hdr From:" > send-hook * "my_hdr From: Michael Graham " > send-

Can't seem to set/change To: header with my_hdr

I am trying to change the To: address of some messages with a send-hook and failing completely. I already have a pair of send-hook commands that work for all lists:- send-hook . 'my_hdr From: Chris Green ' send-hook ~l 'my_hdr From: Chris Green ' This sets the Fro

Re: Ignoring my_hdr

On Sun, May 29, 2011 at 04:51:01PM +0100, David Woodfall wrote: On (13:42 29/05/11), Jamie Paul Griffin put forth the proposition: IIUC, you're talking about when you are composing in the editor, not mutt, which would explain why. I guess this means you have $edit_headers set in $your muttrc

Re: Ignoring my_hdr

tice that I have a custom header set by: > >> > >> my_hdr X-PGP-Key: http://www.dawoodfall.net/dawoodfall.asc > >> > >> Now this is fine but is there a way to ignore it when composing mail? > >> I don't really need to see it. My ignore/unignore lines are

Re: Ignoring my_hdr

On (13:42 29/05/11), Jamie Paul Griffin put forth the proposition: On Sun, May 29, 2011 at 01:15:38PM +0100, David Woodfall wrote: Hi, The observant will notice that I have a custom header set by: my_hdr X-PGP-Key: http://www.dawoodfall.net/dawoodfall.asc Now this is fine but is there a

Re: Ignoring my_hdr

On Sun, May 29, 2011 at 01:15:38PM +0100, David Woodfall wrote: > Hi, > > The observant will notice that I have a custom header set by: > > my_hdr X-PGP-Key: http://www.dawoodfall.net/dawoodfall.asc > > Now this is fine but is there a way to ignore it when composing mail?

Ignoring my_hdr

Hi, The observant will notice that I have a custom header set by: my_hdr X-PGP-Key: http://www.dawoodfall.net/dawoodfall.asc Now this is fine but is there a way to ignore it when composing mail? I don't really need to see it. My ignore/unignore lines are: ignore * unignore date from:

Re: send-hook my_hdr unknown variable

:' > > send-hook '~t [EMAIL PROTECTED]' 'set signature=~/.mutt/signature-personal' > > 'my_hdr From: Joseph <[EMAIL PROTECTED]> > > > > The signature part is working but my_hdr gives me "unknown variable" > > when I try t

Re: send-hook my_hdr unknown variable

Hello,Joseph <[EMAIL PROTECTED]>! * You wrote on Sun, Oct 07, 2007 at 11:15:29PM -0600: > Is there a limit how many variable I can assign to a hook? > I have below: > > send-hook . 'unmy_hdr From:' > send-hook '~t [EMAIL PROTECTED]' 'set signatu

Re: send-hook my_hdr unknown variable

AIL PROTECTED]' 'set signature=~/.mutt/signature-personal' > > 'my_hdr From: Joseph <[EMAIL PROTECTED]> > > Instead of trying to get everything together in one line, you could include a > file with the settings you want. > > For an example, you could chec

Re: send-hook my_hdr unknown variable

On Sun, Oct 07, 2007 at 11:15:29PM -0600, Joseph wrote: > Is there a limit how many variable I can assign to a hook? > I have below: > > send-hook . 'unmy_hdr From:' > send-hook '~t [EMAIL PROTECTED]' 'set signature=~/.mutt/signature-personal' > &

Re: send-hook my_hdr unknown variable

On Sun, Oct 07, 2007 at 11:48:47PM -0600, Joseph wrote: > send-hook '~t [EMAIL PROTECTED]' 'set signature=~/.mutt/signature-personal > my_hdr From: Joseph <[EMAIL PROTECTED]> set record=~/.maildir/friends' > > Is there something to joint the patterns? ma

Re: send-hook my_hdr unknown variable

On 10/08/07 00:20, Javier Rojas wrote: > > send-hook . 'unmy_hdr From:' > > send-hook '~t [EMAIL PROTECTED]' 'set signature=~/.mutt/signature-personal' > > 'my_hdr From: Joseph <[EMAIL PROTECTED]> > > > > The signature pa

Re: send-hook my_hdr unknown variable

On Sun, Oct 07, 2007 at 11:15:29PM -0600, Joseph wrote: > Is there a limit how many variable I can assign to a hook? > I have below: > > send-hook . 'unmy_hdr From:' > send-hook '~t [EMAIL PROTECTED]' 'set signature=~/.mutt/signature-personal' > &

send-hook my_hdr unknown variable

Is there a limit how many variable I can assign to a hook? I have below: send-hook . 'unmy_hdr From:' send-hook '~t [EMAIL PROTECTED]' 'set signature=~/.mutt/signature-personal' 'my_hdr From: Joseph <[EMAIL PROTECTED]> The signature part is working but m

Re: my_hdr From

sending messages. If unset, no From:' header field will be generated unless the user explicitly sets one using the “my_hdr” command. > > 3. make sure $envelope_from resp. use_envelope_from is set > > Again what this one do? ... again, 'man

Re: my_hdr From

correctly explained. > > > > and I was under impression that: > > "my_hdr From:" is the same as "set from=" > > but apparently not. > > With: > > my_hdr From: Joseph <[EMAIL PROTECTED]> > > > > My email was sent but I

Re: my_hdr From

* On Thu, Sep 27, 2007 Joseph ([EMAIL PROTECTED]) muttered: > I'm following this guide in setting up profiles: > http://www.acoustics.hut.fi/~mara/mutt/profiles.html > > and I was under impression that: > "my_hdr From:" is the same as "set from=" > b

my_hdr From

I'm following this guide in setting up profiles: http://www.acoustics.hut.fi/~mara/mutt/profiles.html and I was under impression that: "my_hdr From:" is the same as "set from=" but apparently not. With: my_hdr From: Joseph <[EMAIL PROTECTED]> My email was sent

Re: my_hdr not working with multiple IMAP accounts

.muttrc: > >#set some default locations >set spoolfile=imap:[EMAIL PROTECTED]/INBOX >set folder=imap:[EMAIL PROTECTED]/ >set record=imap:[EMAIL PROTECTED]/INBOX.Sent >set postponed=imap:[EMAIL PROTECTED]/INBOX.Drafts >my_hdr From: Kurt Lieber <[EMAIL PROTECTED]> > Try &#

Re: my_hdr not working with multiple IMAP accounts

$from. Based on a suggestion from someone else, I switched to using $my_hdr instead, and I still ran into problems. If you have already replied to comp.mail.mutt, my news server hasn't received the post yet. As for the issue at hand, I've found a work-around by placing each account person

Re: my_hdr not working with multiple IMAP accounts

* Kurt Lieber <[EMAIL PROTECTED]> [2002-09-29 17:48]: > I'm setting up mutt for the first time.[..] > Any help is appreciated. since you have also posted this to comp.mail.mutt i suggest that you look for answer on that medium. Sven

my_hdr not working with multiple IMAP accounts

map:[EMAIL PROTECTED]/INBOX.Drafts my_hdr From: Kurt Lieber <[EMAIL PROTECTED]> account-hook . 'unset spoolfile folder record postponed hostname pgp_autosign; unmy_hdr From:' account-hook imap:[EMAIL PROTECTED]/ \ 'set spoolfile=imap:[EMAIL PROTECTED]/INBOX; \ set folder=ima

Re: from, realname, my_hdr "From:"

On Mon, Jul 15, 2002 at 09:54:14AM -0500, Derrick 'dman' Hudson wrote: > On Mon, Jul 15, 2002 at 08:21:27AM -0400, Daniel J Peng wrote: > | On Sun, Jul 14, 2002 at 10:08:47PM -0500, Derrick 'dman' Hudson wrote: > | > On Sun, Jul 14, 2002 at 09:37:03PM -0400, Daniel J Peng wrote: > | > | I just ins

Re: from, realname, my_hdr "From:"

On Mon, Jul 15, 2002 at 08:21:27AM -0400, Daniel J Peng wrote: | On Sun, Jul 14, 2002 at 10:08:47PM -0500, Derrick 'dman' Hudson wrote: | > On Sun, Jul 14, 2002 at 09:37:03PM -0400, Daniel J Peng wrote: | > | I just installed Debian woody with Mutt 1.3.28i, and I've discovered a | > | puzzling beh

Re: from, realname, my_hdr "From:"

On Sun, Jul 14, 2002 at 10:08:47PM -0500, Derrick 'dman' Hudson wrote: > On Sun, Jul 14, 2002 at 09:37:03PM -0400, Daniel J Peng wrote: > | I just installed Debian woody with Mutt 1.3.28i, and I've discovered a > | puzzling behavior that wasn't in the Mutt that came with Mandrake 8.0 > | nor any o

Re: from, realname, my_hdr "From:"

On Sun, Jul 14, 2002 at 09:37:03PM -0400, Daniel J Peng wrote: | I just installed Debian woody with Mutt 1.3.28i, and I've discovered a | puzzling behavior that wasn't in the Mutt that came with Mandrake 8.0 | nor any other Mutt I've ever used. I made a simple muttrc with just | | > set from="[E

from, realname, my_hdr "From:"

I just installed Debian woody with Mutt 1.3.28i, and I've discovered a puzzling behavior that wasn't in the Mutt that came with Mandrake 8.0 nor any other Mutt I've ever used. I made a simple muttrc with just > set from="[EMAIL PROTECTED]" > set realname="Daniel J. Peng" Now I expected that whe

Re: reverse_name question - my_hdr overrides

; My understanding was that "reverse_name" could > override the setting of "from", but that > "my_hdr From" would override "reverse_name". correct. a FROM header set with my_hdr will simply be "added" and thus will override a FROM header generat

Re: Command parsing within my_hdr

Michael Elkins <[EMAIL PROTECTED]>: > > Use single quotes instead. That will defer the execution until when > the hook is activated instead of when the muttrc is parsed. Indeed it does. I usually do that, but didn't know why. I had changed it when trying to determine the problem. Thanks. --

Re: Command parsing within my_hdr

Drew Raines wrote: > I have another question, though. Shouldn't send-hook run the command > every time I start to send a message that matches it? It seems to only > run it when I source .muttrc. Use single quotes instead. That will defer the execution until when the hook is activated instead o

Re: Command parsing within my_hdr

Mike Schiraldi <[EMAIL PROTECTED]>: > > > send-hook . "my_hdr Reply-To: '`/path/to/some-command`'" I think it was a problem with my regex I was using for the send-hook. All the combinations of output redirections started working. > Yeah, that should wor

Re: Command parsing within my_hdr

Mike Schiraldi <[EMAIL PROTECTED]>: > > > send-hook . "my_hdr Reply-To: '`/path/to/some-command`'" I think it was a problem with my regex I was using for the send-hook. All the combinations of output redirections started working. > Yeah, that should wor

Re: Command parsing within my_hdr

Knute <[EMAIL PROTECTED]>: > > > my_hdr Reply-To: `/path/to/some-command-output` > > It wasn't designed to execute commands, though it could trigger a > command to be done, depending on that header. Depends on how it is set > up. Actually, the above does wo

Re: Command parsing within my_hdr

> Try wrapping it in another layer of quotes, like > > send-hook . "my_hdr Reply-To: '`/path/to/some-command`'" Yeah, that should work. I've been doing that for months and haven't had a problem: send-hook . 'my_hdr X-Last-Reboot: `uptime.pl`

Re: Command parsing within my_hdr

On Thu, 17 Jan 2002, Drew Raines wrote: >Knute <[EMAIL PROTECTED]>: >> >> > my_hdr Reply-To: `/path/to/some-command-output` >> >> It wasn't designed to execute commands, though it could trigger a >> command to be done, depending on that heade

Re: Command parsing within my_hdr

Drew -- ...and then Drew Raines said... % % Knute <[EMAIL PROTECTED]>: % > % > > my_hdr Reply-To: `/path/to/some-command-output` % > % > It wasn't designed to execute commands, though it could trigger a % > command to be done, depending on that header. De

Re: Command parsing within my_hdr

Knute <[EMAIL PROTECTED]>: > > > my_hdr Reply-To: `/path/to/some-command-output` > > It wasn't designed to execute commands, though it could trigger a > command to be done, depending on that header. Depends on how it is > set up. Actually, the above does wo

Re: Command parsing within my_hdr

On Thu, 17 Jan 2002, Drew Raines wrote: > >Inserting a command within a my_hdr doesn't seem to work; should it? > > my_hdr Reply-To: `/path/to/some-command-output` > >mutt complains with ``/path/to/some-command-output: unknown command.'' My understanding o

Command parsing within my_hdr

Inserting a command within a my_hdr doesn't seem to work; should it? my_hdr Reply-To: `/path/to/some-command-output` mutt complains with ``/path/to/some-command-output: unknown command.'' -- Drew

Re: problems with non a-z chars and my_hdr (1.3.24i)

On Wed, Dec 19, 2001 at 03:44:27PM +0100, Vincent Lefevre wrote: > > So, perhaps you should quote the name: > > my_hdr From: "Christian Kjønsvik" <[EMAIL PROTECTED]> > > (I haven't tried and don't know if this works.) It doesn't, same

Re: problems with non a-z chars and my_hdr (1.3.24i)

sers > > > started complaining that his From field was all messed up. At first I > > > suspected he'd made a mess of his .muttrc, but after taking time to > > > investigate today it seems that his .muttrc is correct. > > > > > > my_hdr Christian Kjønsvi

Re: problems with non a-z chars and my_hdr (1.3.24i)

I > > suspected he'd made a mess of his .muttrc, but after taking time to > > investigate today it seems that his .muttrc is correct. > > > > my_hdr Christian Kjønsvik <[EMAIL PROTECTED]> > > is the line in question, when changed to > > my_hdr Ch

Re: problems with non a-z chars and my_hdr (1.3.24i)

> investigate today it seems that his .muttrc is correct. > > my_hdr Christian Kjønsvik <[EMAIL PROTECTED]> > is the line in question, when changed to > my_hdr Christian Kjnsvik <[EMAIL PROTECTED]> > it worked as specified. This is strange as it isn't a valid my

problems with non a-z chars and my_hdr (1.3.24i)

After I upgraded from 1.3.23 to 1.3.24 a few days ago, one of my users started complaining that his From field was all messed up. At first I suspected he'd made a mess of his .muttrc, but after taking time to investigate today it seems that his .muttrc is correct. my_hdr Christian Kjø

Re: send-hook and my_hdr

On Thu, Oct 25, 2001 at 11:44:12PM -0700, Gary Johnson wrote: > folder-hook . unhook send-hook > folder-hook . 'unmy_hdr From:' > folder-hook folder1 send-hook . 'my_hdr From: default_for_folder1' > folder-hook folder2 send-hook . 'my_hdr

Re: send-hook and my_hdr

from variable from folder-hooks and use my_hdr from > send-hooks to override it from case to case. Thanks Thomas. This works great! Greetings - Lars.

Re: send-hook and my_hdr

ooks together >to modify the From-headers in a way that i want? I'd set the $from variable from folder-hooks and use my_hdr from send-hooks to override it from case to case. -- Thomas Roesslerhttp://log.does-not-exist.org/

Re: send-hook and my_hdr

at should give you the general idea. (This particular example is untested, but I have verified that similar examples do work.) folder-hook . unhook send-hook folder-hook . 'unmy_hdr From:' folder-hook folder1 send-hook . 'my_hdr From: default_for_folder1' fold

Re: send-hook and my_hdr

On Fri, Oct 26, 2001 at 01:52:16AM +0200, Lars Becker (dis)graced my inbox with: > On Thu, Oct 11, 2001 at 02:53:29PM +0200, Thomas Roessler wrote: > > >>See that header in this mail. That is from a send-hook. Problem > >>is that once that hook is activated, the header ends up in all > >>ma

Re: send-hook and my_hdr

On Thu, Oct 11, 2001 at 02:53:29PM +0200, Thomas Roessler wrote: >>See that header in this mail. That is from a send-hook. Problem >>is that once that hook is activated, the header ends up in all >>mails (like this one). >>How to fix? > Add a hook matching all messages which unmy_hdrs the

Re: my_hdr vs. $from

On 2001-10-23 13:36:59 +0200, Volker Moell wrote: >Where's my error? Is this a bug or a feature? It's intended to work that way. $from sets the default from address, which can be overridden by setting the $reverse_name variable. It's evaluated before any hooks are

my_hdr vs. $from

get this value instead of "moell". But in no case I get the value from my default send-hook. When setting "my_hdr" instead of $from works: set realname="Volker Moell" set from="[EMAIL PROTECTED]" set use_from=yes send-hook . 'unmy_hdr From:

Re: my_hdr From: problems

On Oct/18/2001, Drew Raines wrote: > I can't get my_hdr From: to display anything other than >Drew Raines <[EMAIL PROTECTED]> I always do a "unmy_hdr From:" before using "my_hdr". Like this: send-hook . 'unmy_hdr From:; \

Re: my_hdr From: problems

On Oct/18/2001, Drew Raines wrote: > I can't get my_hdr From: to display anything other than >Drew Raines <[EMAIL PROTECTED]> I always do a "unmy_hdr From:" before using "my_hdr". Like this: send-hook . 'unmy_hdr From:; \

Re: my_hdr From: problems

On Thu, Oct 18, 2001 at 12:47:20PM -0500, Drew Raines (dis)graced my inbox with: > * Not Even My Name <[EMAIL PROTECTED]>: > > > > my_hdr From: Not Even My Name <[EMAIL PROTECTED]> > > But why can't I use the other style? Elkins uses it in the 1.2.5 >

Re: my_hdr From: problems

* Not Even My Name <[EMAIL PROTECTED]>: > > my_hdr From: Not Even My Name <[EMAIL PROTECTED]> But why can't I use the other style? Elkins uses it in the 1.2.5 documentation every time he mentions an alias or my_hdr. Technically I should be able to put whatever I want,

Re: my_hdr From: problems

* darren chamberlain <[EMAIL PROTECTED]>: > > I think you have to do: > > my_hdr From [EMAIL PROTECTED] (Not Even My Name) > > not From:. Tells me it's an invalid header field if I do that. -- Drew

Re: my_hdr From: problems

On Thu, Oct 18, 2001 at 11:32:53AM -0500, Drew Raines wrote: > > I can't get my_hdr From: to display anything other than > >Drew Raines <[EMAIL PROTECTED]> > >my_hdr From: [EMAIL PROTECTED] (Not Even My Name) > my_hdr From: Not Even My Name <[

Re: my_hdr From: problems

Drew Raines <[EMAIL PROTECTED]> said something to this effect on 10/18/2001: > I fear this is something obvious, but I've tried everything I can think > of in both 1.2.5 and 1.3.22.1. > > I can't get my_hdr From: to display anything other than > >

my_hdr From: problems

I fear this is something obvious, but I've tried everything I can think of in both 1.2.5 and 1.3.22.1. I can't get my_hdr From: to display anything other than Drew Raines <[EMAIL PROTECTED]> Everything else works: my_hdr Organization: my_hdr X-Some-Other-Header: ..j

  1   2   >