Re: Setting X-Priority/Priority/Important headers more easiliy?

Hi Tim, Tim Chase schrieb am 27.09.2023 21:36:57: > Does anyone have any suggestions/mappings that might make it easier > to add/manage add/manage these headers rather than hand-entering > them with {edit-headers} in the message-compose menu? If you use vim you could use imap in ~/.vim

Re: Setting X-Priority/Priority/Important headers more easiliy?

On Wed, Sep 27, 2023 at 02:36:57PM -0500, Tim Chase wrote: > Howdy, > > RFC-2156[1] specifies ways to use the headers > > Importance: {low, normal, high} > Priority: {normal, non-urgent, urgent} > Sensitivity: {Personal, Private, Company-Confidential} > >

Setting X-Priority/Priority/Important headers more easiliy?

Howdy, RFC-2156[1] specifies ways to use the headers Importance: {low, normal, high} Priority: {normal, non-urgent, urgent} Sensitivity: {Personal, Private, Company-Confidential} and I've also seen the non-standard X-Priority: 1 (Highest) X-MSMail-Priority: High (with X-Priority ranging

Re: Identifying messages with no To: or CC: headers?

On Fri, Sep 02, 2022 at 04:03:22PM -0400, John Hawkinson wrote: >> Could you not prepend your EXPR with something like this? >> >> `^(Delivered|Envelope)-To:\ ` > > I belive that you want this to be all-lowercase, because those headers > can be any case

Re: Identifying messages with no To: or CC: headers?

On 2022-09-02 17:42, Todd Zullinger wrote: > Tim Chase wrote: >> color index reverse brightblack black "~h ^(delivered|envelope)-to:\ >> +[0-9a-f]{5,}[.][0-9a-f]{5,}@mydomain.com)$" >> >> Mutt complains >> >> Error in [my muttrc]: '^(delivered': parentheses not balanced >> >> which looks

Re: Identifying messages with no To: or CC: headers?

Tim Chase wrote: > On 2022-09-02 19:45, Sam Kuper wrote: >> Could you not prepend your EXPR with something like this? >> >> `^(Delivered|Envelope)-To:\ ` > > Ah, so the pattern for matching ~h includes the header-name then > and the regex can match against that? That should work. > >

Re: Identifying messages with no To: or CC: headers?

r CC: header, so I > >>> can't identify them with a ~C and I don't see an option for > >>> identifying messages by the Delivered-To or Envelope-To headers. > >>> > >>> Is there a good way to identify these messages? > >> > >> Che

Re: Identifying messages with no To: or CC: headers?

> Could you not prepend your EXPR with something like this? > > `^(Delivered|Envelope)-To:\ ` I belive that you want this to be all-lowercase, because those headers can be any case, and mutt will search case-insensitively per sec. 8.3 of the manual: > As for regular expressi

Re: Identifying messages with no To: or CC: headers?

C and I don't see an option for >>> identifying messages by the Delivered-To or Envelope-To headers. >>> >>> Is there a good way to identify these messages? >> >> Check ~h and =h, it those don???t do, consider filtering with your >> mail retriever (e

Re: Identifying messages with no To: or CC: headers?

ivered-To or Envelope-To headers. > > > > Is there a good way to identify these messages? > > Check ~h and =h, it those don???t do, consider filtering with your > mail retriever (e.g getmail, that is what I use). Hmm, that looks like it might work. Is there further documentation

Re: Identifying messages with no To: or CC: headers?

Hello Tim, Il 02 settembre 2022 alle 18:01 Tim Chase ha scritto: > However, often these messages don't have a To: or CC: header, so I > can't identify them with a ~C and I don't see an option for identifying > messages by the Delivered-To or Envelope-To headers. > > Is t

Identifying messages with no To: or CC: headers?

I have a catch-all mailbox and would like to set up a filter/coloring for spam messages coming to me of the form [[:xdigit:]]{5,}[.][[:xdigit:]]{5,}@me.mydomain.com according to the Delivered-To: or Envelope-To: headers. I suspect they're comming from scraped message-IDs from messages I've

Setting Importance:, Priority:, X-Priority: headers

According to RFC-2076[1], I should be able to include headers such as Importance: {high,normal,low} Priority: {normal,urgent,non-urgent} X-Priority: [1-5] (where X-Priority's 1=highest, 5=lowest) to inform others' MUAs of the intended importance/priority. Currently I'm manually setting

Take over existing attachments as "Attach: " pseudo-headers

Hi all, Using long time $edit_headers option, just discovered lovely "Attach: " pseudo header, which makes it easy to specify new attachments during message body edit. However it works just one-way - once editor is finished, those pseudo-headers are processed somehow and added to

Re: Headers in Editor

On Sun, Aug 29, 2021 at 06:02:43PM +0200, Rene Kita wrote: The idea behind this is, that can you view/edit the headers while replying. That's why the headers are cleared if you delete these lines. They want end up in the body of that mail. As already that said in another reply, 'set

Re: Headers in Editor

s of the editor! > > If I write over them, or delete them, I have no addresses when sending > the message. > > How do I fix this? The idea behind this is, that can you view/edit the headers while replying. That's why the headers are cleared if you delete these lines. They want e

Re: Headers in Editor

How could I have missed that! Thank you - I have NO idea why it's working on one computer but not this one. But now thank to your help it's working fine. Thank you! David On 08/29/ , ಚಿರಾಗ್ ನಟರಾಜ್ wrote: > 12021/06/00 03:92.08 ನಲ್ಲಿ, "David J. Ring, Jr." ಬರೆದರು: > > I have the strangest

Re: Headers in Editor

12021/06/00 03:92.08 ನಲ್ಲಿ, "David J. Ring, Jr." ಬರೆದರು: > I have the strangest problem. > > When I reply to a message in a new installation of mutt, what will > eventually become the addresses, and subject, and In-Reply-To threading > informaton becomes the top lines of the editor! > > If I

Headers in Editor

I have the strangest problem. When I reply to a message in a new installation of mutt, what will eventually become the addresses, and subject, and In-Reply-To threading informaton becomes the top lines of the editor! If I write over them, or delete them, I have no addresses when sending the

Re: Is it possible to change/add headers to incoming mail?

On 2020-12-09 05:11, Sam Kuper wrote: procmail is not a good option anymore, and has not been for a while now: https://marc.info/?l=openbsd-ports=141634350915839 ... Maildrop is a popular alternative. Some more delivery agents are listed in the Wikipedia article below. They may not all

Re: Is it possible to change/add headers to incoming mail?

On Wed, Dec 09, 2020 at 03:23:20AM -0500, Philippe Meunier wrote: > raf wrote: >> for mail delivered locally, procmail could do it. > > procmail is not a good option anymore, and has not been for a while > now: > https://marc.info/?l=openbsd-ports=141634350915839 Debian continues to make

Re: Is it possible to change/add headers to incoming mail?

raf wrote: >for mail delivered locally, procmail could do it. procmail is not a good option anymore, and has not been for a while now: https://marc.info/?l=openbsd-ports=141634350915839 Philippe

Re: Is it possible to change/add headers to incoming mail?

On Tue, Dec 08, 2020 at 09:34:48PM +, Chris Green wrote: > Are there any mutt hooks which act on incoming mail? > > So I could (for example) add a header to incoming mail which matches > certain criteria. > > -- > Chris Green for mail on an imap server, imapfilter could do it. you'd need

Re: Is it possible to change/add headers to incoming mail?

like getmail to your stack? Works flawlessly here and you can do nifty things with headers like spam-marking with bmf and I believe what you are asking too without much fuss.

Is it possible to change/add headers to incoming mail?

Are there any mutt hooks which act on incoming mail? So I could (for example) add a header to incoming mail which matches certain criteria. -- Chris Green

Re: Can one 'unignore' headers from a specific host

On Tue, Dec 08, 2020 at 08:46:14PM +, Chris Green wrote: I want to unignore headers from a few specific hosts, i.e. I want to do something like:- unignore Received: from dns.zbmc.eu Is this possible in any way? Mutt performs a string comparison of the unignore value against

Can one 'unignore' headers from a specific host

I want to unignore headers from a few specific hosts, i.e. I want to do something like:- unignore Received: from dns.zbmc.eu Is this possible in any way? Alternatively is there any way to flag messages which have "Received: from dns.zbmc.eu" in the headers and add a custom head

Overwrite draft headers?

Hi, Is it possible to tell mutt to automatically overwrite headers (content-type, etc) from a draft that is being edited? My question comes after the other day I started a draft using Fastmail's webmail app, then finished it using mutt and sent it. Later, I saw that the f=f settings were

Re: Using UTC as time zone in outgoing email headers

On 2019-07-24, at 12:31:23, Derek Martin wrote: > > On Wed, Jul 24, 2019 at 07:06:52AM +, Ryan Smith wrote: >> By default, mutt uses local or computer time zone in outgoing email full >> header, Date section. >> >> How to force mutt to use UTC as time zone

Re: Using UTC as time zone in outgoing email headers

On Wed, Jul 24, 2019 at 07:06:52AM +, Ryan Smith wrote: > By default, mutt uses local or computer time zone in outgoing email full > header, Date section. > > How to force mutt to use UTC as time zone in all outgoing email headers? For what it's worth, this is probably most

Re: Using UTC as time zone in outgoing email headers

: > By default, mutt uses local or computer time zone in outgoing email > full header, Date section. > > How to force mutt to use UTC as time zone in all outgoing email > headers? > > set_hdr Date=? > > K9 Mail in Android has such option in privacy settings Hide Timezone, > use

Using UTC as time zone in outgoing email headers

By default, mutt uses local or computer time zone in outgoing email full header, Date section. How to force mutt to use UTC as time zone in all outgoing email headers? set_hdr Date=? K9 Mail in Android has such option in privacy settings Hide Timezone, use UTC instead of local time zone. Ryan

Re: Limit number of fetched message headers WITHOUT using header cache/body cache?

On Mon, Mar 11, 2019 at 03:11:57PM +, Jaime T wrote: Is there a way to limit how many message headers mutt fetches? Not within Mutt, but Gmail has a "Folder size limits" setting to do so. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684

Limit number of fetched message headers WITHOUT using header cache/body cache?

After installing and setting up mutt to connect to my gmail account via imap, mutt downloads all message headers, thus: Fetching message headers... 41821/78259 (53%) I already know that the "standard" way of *not* repeatedly downloading all these message headers is to cache them on

Re: Color headers in pager based on message patterns

On 07Feb2018 20:35, Scott Kostyshak wrote: Example (untested): message-hook . 'set my_hdr_colour=green' message-hook ~p!~l 'set my_hdr_colour=yellow' message-hook . 'color header $my_hdr_colour default' so that a colour is chosen per message, then applied to your

Re: Color headers in pager based on message patterns

the following to color the index if a message > > was sent to me and not sent to a list: > > > > color index yellow black ~p!~l > > > > But I cannot do the following: > > > > color header yellow black ~p!~l > > > > to color all headers in t

Re: Color headers in pager based on message patterns

But I cannot do the following: color header yellow black ~p!~l to color all headers in the pager if a message was sent to me and not sent to a list. This is understandable, as the pattern is matched against each header. As for why I would like to do this, I rarely look at the index. I configur

Color headers in pager based on message patterns

to color all headers in the pager if a message was sent to me and not sent to a list. This is understandable, as the pattern is matched against each header. As for why I would like to do this, I rarely look at the index. I configure mutt to go directly to the pager, so that I focus on one email

Re: view complete message (including headers)

Using mutt's help screen (?), always a good place to start, in index view: hdisplay-toggle-weeddisplay message and toggle header weeding On Mon, Feb 05, 2018 at 09:29:14PM +0800, Yubin Ruan wrote: > Hi, > > In Mutt, how can I view the complete email (including all headers

Re: view complete message (including headers)

El día Monday, February 05, 2018 a las 09:29:14PM +0800, Yubin Ruan escribió: > Hi, > > In Mutt, how can I view the complete email (including all headers) without > using 'e' to (potentially) modify that email (which cause it to be deleted?) h -- Matthias Apitz, ✉ g...

view complete message (including headers)

Hi, In Mutt, how can I view the complete email (including all headers) without using 'e' to (potentially) modify that email (which cause it to be deleted?) -- Yubin

Re: Attachment saving and piping: what of the headers?

On 2017-07-11 13:05, Erik Christiansen wrote: > Curious. Here, a "| cat > /tmp/fred" produced a copy of your post, > complete with 80 lines of headers. That's with pipe_decode unset, and > Mutt 1.8.0 (2017-02-23). But that is not what I'm writing about. I'm just t

Re: Attachment saving and piping: what of the headers?

On 10.07.17 14:29, Ian Zimmerman wrote: > I tried both a straight save, and a pipe to a cat command. In either > case, no headers are present, and neither is the separator line; the > file just contains the body and that's that. Curious. Here, a "| cat > /tmp/fred" produc

Attachment saving and piping: what of the headers?

Well, just when I thought I'd never need to ask a question here again :-) I started writing a script which will run as a sink of from the attachment view. I spent some minutes to make the script correctly (I thought) skip over the MIME headers, and only start the real processing after the empty

pipe_decode: only do one of {weed headers, decode the message} ?

Hello, It seems the pipe_decode setting does two things: weed of header and decode message. How to proceed if I would like one but not the other? For example I would like to decode but not to weed the headers? Kind regards, Xu

Re: Restricting headers when forwarding messages

> Please, how I could edit inline a forwarding message? When I forwarding > a message, that's body isn't showed for editing. Perhaps you have set mime_forward? From the manual: When set, the message you are forwarding will be attached as a separate MIME part instead of included in the

Re: Restricting headers when forwarding messages

> Not sure but you might try unsetting "forward_quote" in your ~/.muttrc or > from mutt's commandline: > :unset forward_quote Unfortunately that doesn't make a difference. Matthias

Re: Restricting headers when forwarding messages

On 13/01/16 at 07:54am, Matthias Vallentin wrote: > You can always edit the msg before forwarding and easily if inline. Please, how I could edit inline a forwarding message? When I forwarding a message, that's body isn't showed for editing. -- Marcelo

Re: Restricting headers when forwarding messages

> You can always edit the msg before forwarding and easily if inline. Yeah, that's what I'm doing at the moment. However, a realized that I forgot manually weeding out unwanted headers a few times and therefore seek automation for this task. Matthias

Re: Restricting headers when forwarding messages

* Matthias Vallentin <vallen...@icir.org> [01-13-16 11:04]: > > You can always edit the msg before forwarding and easily if inline. > > Yeah, that's what I'm doing at the moment. However, a realized that I > forgot manually weeding out unwanted headers a few times and theref

Restricting headers when forwarding messages

I would like to restrict the set of headers when I forward messages, such as preventing X-Label to be included. My configuration contains currently: ignore * unignore From: Sender: Reply-To: unignore To: Cc: Bcc: unignore Subject: unignore Date: unignore User-Agent: X

Re: Restricting headers when forwarding messages

* Matthias Vallentin <vallen...@icir.org> [01-12-16 18:07]: > I would like to restrict the set of headers when I forward messages, > such as preventing X-Label to be included. My configuration contains > currently: > > ignore * > unignore From: Sender: Reply-T

Re: List headers and List Reply [Was: Sent attached doc from Libreoffice]

On Thu, May 28, 2015 at 02:28:29PM -0700, Ian Zimmerman wrote: On 2015-05-28 14:38 -0500, Derek Martin wrote: Derek Come on Patrick, you are not new here... You know full well that Derek most mailer software does not have any list-reply function; mutt Derek is a rare exception, and despite

Re: List headers and List Reply [Was: Sent attached doc from Libreoffice]

El domingo, 31 de mayo de 2015 13:40:06 (CEST), Chris Bannister escribió: ... Alas, it seems that if you append 'Sent from my iPhone' then you are excused. :( I do have sent any mail from an iPhone. matthias -- Sent from my Ubuntu phone http://www.unixarea.de/

Re: List headers and List Reply [Was: Sent attached doc from Libreoffice]

El domingo, 31 de mayo de 2015 14:45:36 (CEST), Matthias Apitz escribió: I do have sent any mail from an iPhone. I dont have sent, was what I wanted write :-) -- Sent from my Ubuntu phone http://www.unixarea.de/

Re: List headers and List Reply [Was: Sent attached doc from Libreoffice]

in a bad mood EVERY day. Actually, most lists I'm subscribed to state in the mailing list policy that personal copies are only acceptable if the OP *asks* to be CC'd. If there is no list reply function then it is up to the poster to edit the headers to conform to policy. Alas, it seems that if you

Re: List headers and List Reply [Was: Sent attached doc from Libreoffice]

On Sun, May 31, 2015 at 03:15:57PM +0200, Matthias Apitz wrote: El domingo, 31 de mayo de 2015 14:45:36 (CEST), Matthias Apitz escribió: I do have sent any mail from an iPhone. I dont have sent, was what I wanted write :-) -- Sent from my Ubuntu phone http://www.unixarea.de/ :-D

mutt hangs after fetching mail headers via IMAP

-To: Matthias Apitz user@domain' at the end it hangs with the message line: Fetching message headers... 4520/4540 (99%) Note: It says 4520 of 4540, while in the debug log it says that it has fetched all: $ tail -20 .muttdebug0 [2015-05-30 16:41:24] imap_read_literal: reading 749 bytes [2015-05-30 16:41

Re: List headers and List Reply [Was: Sent attached doc from Libreoffice]

On 2015-05-28 17:46 -0400, Patrick Shanahan wrote: Ian Note also that this list is slightly substandard in that there is Ian no List-ID header. There may be software out there that uses that Ian header to determine if a message is a list message in the first Ian place. Patrick List-Post:

Re: List headers and List Reply [Was: Sent attached doc from Libreoffice]

* Ian Zimmerman i...@buug.org [05-28-15 17:30]: [...] Note also that this list is slightly substandard in that there is no List-ID header. There may be software out there that uses that header to determine if a message is a list message in the first place. List-Post:

List headers and List Reply [Was: Sent attached doc from Libreoffice]

On 2015-05-28 14:38 -0500, Derek Martin wrote: Derek Come on Patrick, you are not new here... You know full well that Derek most mailer software does not have any list-reply function; mutt Derek is a rare exception, and despite this being a mutt-related list, Derek not the only mailer people use

Fetching message headers

in it. During this time, mutt displays Fetching message headers ... Is there any way to speed this up? I thought the header caching would eliminate most of this download time. Thank you. -pd -- Peter Davis The Tech Curmudgeon www.techcurmudgeon.com

Re: Searching To:-Headers in Sent Mail

. | | To do that, I just use: | | / ~h some_recipient_name | | OK, that looks in all the headers, but you probably want to check Cc: as | well, anyway? (And [s]he's not likely to crop up in many other headers, | so mucking with a tight regex doesn't seem warranted.) | | / ~C

Searching To:-Headers in Sent Mail

I'd like to search messages by recipient in my Sent-Folder, but at least my mutt install won't do it out of the box. Is the scope mutt searches for limited by context (e.g. Sent-Folder) or do I have to use a special search keyword? THX p@rick -- Patrick Ben Koetter p...@state-of-mind.de

Re: Searching To:-Headers in Sent Mail

On 03.06.13 14:30, Patrick Ben Koetter wrote: I'd like to search messages by recipient in my Sent-Folder, but at least my mutt install won't do it out of the box. To do that, I just use: / ~h some_recipient_name OK, that looks in all the headers, but you probably want to check Cc: as well

Re: Searching To:-Headers in Sent Mail

, that looks in all the headers, but you probably want to check Cc: as well, anyway? (And [s]he's not likely to crop up in many other headers, so mucking with a tight regex doesn't seem warranted.) / ~C some_recipient_name looks in to: and cc: -- theatre - books - texts - movies Black Trash Productions

Re: Customise headers shown in editor

On 2013–05–21 David Woodfall wrote: On (08/02/13 17:19), Marco net...@lavabit.com put forth the proposition: On 2013–02–08 Suvayu Ali wrote: I use a combination of ignore and unignore to choose which headers I see Ignore and unignore control the headers displayed in the pager

Re: Customise headers shown in editor

On (08/02/13 17:19), Marco net...@lavabit.com put forth the proposition: On 2013–02–08 Suvayu Ali wrote: I use a combination of ignore and unignore to choose which headers I see Ignore and unignore control the headers displayed in the pager and not the ones shown in the editor, if I'm

Re: Customise headers shown in editor

On (21/05/13 01:23), Dave Woodfall d...@dawoodfall.net put forth the proposition: On (08/02/13 17:19), Marco net...@lavabit.com put forth the proposition: On 2013–02–08 Suvayu Ali wrote: I use a combination of ignore and unignore to choose which headers I see Ignore and unignore control

Re: Customise headers shown in editor

of ignore and unignore to choose which headers I see Ignore and unignore control the headers displayed in the pager and not the ones shown in the editor, if I'm not mistaken. Does this work for you? Marco Hi, did you ever find a way to do this? I would also like to get rid Well, after some

Re: Mutt secretly adds Content-Length headers?

you are talking PGP and SMIME. Both secure a specific part of the message: the content in form of the body and it's attachments. So if you hash a whole message file on the sender side and do this again on the receiver's side you will end up with guaranteed always false results. There are headers

Re: Mutt secretly adds Content-Length headers?

mutt didn't need that header to operate well in the original folder. In general, can't think of any reason to modify any Maildir message on disk and view this as tainting the msgs with unecessary and un-asked-for mods. well, they don't really hurt, but may even help mutt and other tools.

Re: Mutt secretly adds Content-Length headers?

On Wed, Apr 17, 2013 at 01:39:43PM -0400, grarpamp wrote: mutt didn't need that header to operate well in the original folder. In general, can't think of any reason to modify any Maildir message on disk and view this as tainting the msgs with unecessary and un-asked-for mods. well,

Re: Mutt secretly adds Content-Length headers?

: mboxo, mboxrd, mboxcl, mboxcl2. As does mutt's mbox(5). However, that's regarding 'mbox' formats... not 'Maildir', which is strictly one message per file, where such headers like 'content-length' and 'lines' have no reason to apply that I know of from searching so far. I think we're looking

Mutt secretly adds Content-Length headers?

I'm using Maildir. mutt -R against folder A makes no mods as expected. mutt -f against folder A moves new msgs to cur with no mods as expected. But mutt -f against A, operation of tagging messages and 'C'opying them to some other folder B causes Content-Length headers to be added to each message

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

On Fri, Mar 08, 2013 at 03:47:14PM -0500, Patrick Shanahan wrote: If your user interface offers you reply and reply-to-all/reply-to-list (good ones attach the *right* thing of the latter to the button if there's one) I know not about button[s] as I work with text from the keyboard.

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

* Derek Martin inva...@pizzashack.org [03-11-13 15:09]: On Fri, Mar 08, 2013 at 03:47:14PM -0500, Patrick Shanahan wrote: If your user interface offers you reply and reply-to-all/reply-to-list (good ones attach the *right* thing of the latter to the button if there's one) I know not

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

* Alexander Dahl p...@lespocky.de [03-10-13 04:44]: On Sat, Mar 09, 2013 at 10:33:03AM -0700, s. keeling wrote: P.S.: and I have to get my mutt macros fixed, some hook changed my from address here after I replied on another mailing list … m( *lol* FWIW: send-hook . set

setting from address on mailing lists (Was: Why does some list software not honor the headers?)

Hei hei, On Sun, Mar 10, 2013 at 07:59:01AM -0400, Patrick Shanahan wrote: send-hook . set from=your@emailaddy I have this line in my send hooks: send-hook ~C ^netz39.*@lists\\.netz39\\.de$ my_hdr From: Alexander Dahl a...@netz39.de Where do I put the one above, before or

Re: setting from address on mailing lists (Was: Why does some list software not honor the headers?)

* Alexander Dahl p...@lespocky.de [03-10-13 13:08]: Hei hei, On Sun, Mar 10, 2013 at 07:59:01AM -0400, Patrick Shanahan wrote: send-hook . set from=your@emailaddy I have this line in my send hooks: send-hook ~C ^netz39.*@lists\\.netz39\\.de$ my_hdr From: Alexander

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

are on the mutt mailing list here. ;-) But we were talking about other mailing lists used by other users with other MUAs. I heard some of them use buttons and those are exposed to the user while mail headers are usually not. Some more preaching to the choir. Alex P.S.: and I have to get my mutt macros

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

Incoming from Alexander Dahl: But we were talking about other mailing lists used by other users with other MUAs. I heard some of them use buttons and those are exposed to the user while mail headers are usually not. Blasphemy! :-| P.S.: and I have to get my mutt macros fixed, some hook

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

Hei hei, On Sat, Mar 09, 2013 at 10:33:03AM -0700, s. keeling wrote: P.S.: and I have to get my mutt macros fixed, some hook changed my from address here after I replied on another mailing list … m( *lol* FWIW: send-hook . set from=your@emailaddy I have this line in my send hooks:

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

the *right* thing of the latter to the button if there's one) then you do not need to know about what happens in the background or what e-mail headers are, you just hit reply if you want to reply in private and the other button if you want to reply to all aka the list. This is simple and intuitive user

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

reply and reply-to-all/reply-to-list (good ones attach the *right* thing of the latter to the button if there's one) then you do not need to know about what happens in the background or what e-mail headers are, you just hit reply if you want to reply in private and the other button if you want

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

* Erik Christiansen dva...@internode.on.net [02-28-13 02:44]: On 27.02.13 15:59, Patrick Shanahan wrote: I am *against* Reply-To: mudging by list software and believe it should *only* be employed by a poster wishing replies to his posts to be rec'd by a different account such as posting

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

Incoming from Erik Christiansen: On 27.02.13 15:59, Patrick Shanahan wrote: I am *against* Reply-To: mudging by list software and believe it should *only* be employed by a poster wishing replies to his posts to be rec'd by a different account such as posting from work and wanting receipt

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

On Thu, Feb 28, 2013 at 06:41:55PM +1100, Erik Christiansen wrote: On 27.02.13 15:59, Patrick Shanahan wrote: I am *against* Reply-To: mudging by list software and believe it should *only* be employed by a poster wishing replies to his posts to be rec'd by a different account such as

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

On Sat, Feb 23, 2013 at 08:00:24AM -0500, Patrick Shanahan wrote: The **ONLY** way to not get an extra copy is **NOT** to get CC'd in the first place (and vice versa; i.e you in To and list in CC). It is disgusting that the list software decides whether to honor the headers

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

On Wed, Feb 27, 2013 at 12:55:15PM -0600, Derek Martin wrote: Responding to list mail *should* be to the list unless op has *specifically* requested direct mail. All other action is illogical and inefficient. Here's where I disagree. There have been many, many times when I wanted to

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

* Derek Martin inva...@pizzashack.org [02-27-13 13:56]: On Sat, Feb 23, 2013 at 08:00:24AM -0500, Patrick Shanahan wrote: [...] Responding to list mail *should* be to the list unless op has *specifically* requested direct mail. All other action is illogical and inefficient. Here's

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

On Wed, Feb 27, 2013 at 03:13:43PM -0500, Patrick Shanahan wrote: * Derek Martin inva...@pizzashack.org [02-27-13 13:56]: On Sat, Feb 23, 2013 at 08:00:24AM -0500, Patrick Shanahan wrote: [...] Responding to list mail *should* be to the list unless op has *specifically* requested direct

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

Incoming from Derek Martin: On Sat, Feb 23, 2013 at 08:00:24AM -0500, Patrick Shanahan wrote: The **ONLY** way to not get an extra copy is **NOT** to get CC'd in the I've just got to say, as much as I think this's interesting, this's not mutt related. mutt already does this stuff correctly

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

* Derek Martin inva...@pizzashack.org [02-27-13 15:45]: On Wed, Feb 27, 2013 at 03:13:43PM -0500, Patrick Shanahan wrote: [...] While you disagree with my general and incomplete statement, I do agree with you that there are times when a private reply is prudent Fair enough, but I'll just

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

Incoming from Jeremy Kitchen: On Wed, Feb 27, 2013 at 12:55:15PM -0600, Derek Martin wrote: Responding to list mail *should* be to the list unless op has *specifically* requested direct mail. All other action is illogical and inefficient. Here's where I disagree. There have been

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

On Wed, Feb 27, 2013 at 01:52:25PM -0700, s. keeling wrote: Incoming from Derek Martin: On Sat, Feb 23, 2013 at 08:00:24AM -0500, Patrick Shanahan wrote: The **ONLY** way to not get an extra copy is **NOT** to get CC'd in the I've just got to say, as much as I think this's interesting,

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

On Sat, Feb 23, 2013 at 08:00:24AM -0500, Patrick Shanahan wrote: To my understanding, list software does not decide, except concerning MFT. *The* problem is users not responding to list, L, but rather to all, g. For the record, I'll also note that I rarely actually do this, even though I

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

* Derek Martin inva...@pizzashack.org [02-27-13 17:29]: On Sat, Feb 23, 2013 at 08:00:24AM -0500, Patrick Shanahan wrote: To my understanding, list software does not decide, except concerning MFT. *The* problem is users not responding to list, L, but rather to all, g. For the record,

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

* Derek Martin inva...@pizzashack.org [02-27-13 13:56]: On Sat, Feb 23, 2013 at 08:00:24AM -0500, Patrick Shanahan wrote: [...] Responding to list mail *should* be to the list unless op has *specifically* requested direct mail. All other action is illogical and inefficient. Here's

Re: Why does some list software not honor the headers? (was ... Re: People want ...)

. The *correct* manner is L, list-reply, but pre-supposes you correctly maintain your ~/.muttrc and/or the list software provides the correct headers And all list-software does not *insert* MFT headers, and the MFT header is not necessary for proper list responses. Remember that it is *you* posting

  1   2   3   4   5   6   7   >