ich
> are super widely used / mainstream).
https://datatracker.ietf.org/doc/draft-ietf-drums-mail-followup-to/
https://people.dsv.su.se/~jpalme/ietf/draft-drums-mfwupto-01.txt
--
Michael Kjörling
🔗 https://michael.kjorling.se
On Sun, Aug 20, 2023 at 06:25:57PM +0800, "Kevin J. McCarthy"
wrote:
> On Sun, Aug 20, 2023 at 03:53:09PM +1000, raf via Mutt-users wrote:
> > I don't have any "lists" commands. I do have a "subscribe" command
> > which refers to mailing lists by their aliases. One of the aliases
> > is "debian"
On Sun, Aug 20, 2023 at 03:53:09PM +1000, raf via Mutt-users wrote:
I don't have any "lists" commands. I do have a "subscribe" command
which refers to mailing lists by their aliases. One of the aliases
is "debian" and the email address in question does contain "+debian"
but that shouldn't matter.
Hi,
Someone recently emailed me. Technically it was a reply to an
old email of mine. Since then, a few emails have gone back and
forth between us. All of my outgoing mails to this one address
have had a Mail-Followup-To header added. I have no idea why.
The address isn't mentioned i
On Fri, Apr 27, 2018 at 10:50:47AM -0700, Will Yardley wrote:
> On Fri, Apr 27, 2018 at 08:57:50AM -0700, Kevin J. McCarthy wrote:
> >
> > I always thought $followup_to was a pretty nice feature. While I
> > sympathize with Matthias, the mischief was the result of
> > misconfiguration, and Mutt r
On Fri, Apr 27, 2018 at 06:33:52AM +0200, Matthias Apitz wrote:
> El día jueves, abril 26, 2018 a las 05:28:55p. m. -0500, Derek Martin
> escribió:
>
> > On Wed, Apr 25, 2018 at 07:31:20PM +0200, Matthias Apitz wrote:
> > > $ grep -i Mail-Followup-To ~/.muttrc
> >
On Mon, Apr 30, 2018 at 05:27:26PM +1000, Erik Christiansen wrote:
> Here, declares: "Mutt also supports the Mail-Followup-To header.
> When you send a message to a list of recipients which includes one or
> several subscribed mailing lists, and if the $followup_to option is se
However, if there is a strong majority of mutt-users subscribers that
> agree with $followup_to defaulting to 'no', I'll make the change.
Here, declares: "Mutt also supports the Mail-Followup-To header.
When you send a message to a list of recipients which includes one or
On Fri, Apr 27, 2018 at 08:57:50AM -0700, Kevin J. McCarthy wrote:
>
> I always thought $followup_to was a pretty nice feature. While I
> sympathize with Matthias, the mischief was the result of
> misconfiguration, and Mutt requires nothing if not attention to the
> documentation and configuratio
* Kevin J. McCarthy [04-27-18 11:58]:
[...]
> I always thought $followup_to was a pretty nice feature. While I
> sympathize with Matthias, the mischief was the result of
> misconfiguration, and Mutt requires nothing if not attention to the
> documentation and configuration.
>
> However, if ther
On Thu, Apr 26, 2018 at 08:50:35PM +, Mihai Lazarescu wrote:
>
>
> On April 26, 2018 8:24:16 PM UTC, Ian Zimmerman wrote:
> > On 2018-04-25 10:24, Will Yardley wrote:
> >
> > > Kind of thread drift, but I actually wonder if Mutt shouldn't move
> >
d that's what I call munging.
>
> I don't believe so. I have reply_goes_to_list set to 'Poster', which is
> not supposed to add (or remove) any such header.
yes, Mail-Followup-To, is set to list addr and Reply-To is empty.
--
(paka)Patrick Shanahan Pla
On Fri, Apr 27, 2018 at 07:48:40AM -0700, Ian Zimmerman wrote:
> On 2018-04-27 06:33, Matthias Apitz wrote:
>
> > Hmm, someone set Reply-To in the headers of your mail too.
>
> That was the list manager, and that's what I call munging.
I don't believe so. I have reply_goes_to_list set to 'Poste
On 2018-04-27 06:33, Matthias Apitz wrote:
> Hmm, someone set Reply-To in the headers of your mail too.
That was the list manager, and that's what I call munging. AIUI it was
one of the reasons why Mail-Followup-To was invented, because Reply-To
could not be trusted anymore. I feel it
El día jueves, abril 26, 2018 a las 05:28:55p. m. -0500, Derek Martin escribió:
> On Wed, Apr 25, 2018 at 07:31:20PM +0200, Matthias Apitz wrote:
> > $ grep -i Mail-Followup-To ~/.muttrc
> > $
> >
> > as I said, I do not set any Mail-Followup-To; and I think Reply-
On Wed, Apr 25, 2018 at 07:31:20PM +0200, Matthias Apitz wrote:
> $ grep -i Mail-Followup-To ~/.muttrc
> $
>
> as I said, I do not set any Mail-Followup-To; and I think Reply-To:
> and From: is quite normal;
Reply-To should normally not be set; its purpose is to route mail to
the
On April 26, 2018 8:24:16 PM UTC, Ian Zimmerman wrote:
> On 2018-04-25 10:24, Will Yardley wrote:
>
> > Kind of thread drift, but I actually wonder if Mutt shouldn't move
> > away from Mail-Followup-To, as it never became a standard, and is
> not
> > really
On 2018-04-25 10:24, Will Yardley wrote:
> Kind of thread drift, but I actually wonder if Mutt shouldn't move
> away from Mail-Followup-To, as it never became a standard, and is not
> really adopted by (m)any other commonly used mail clients.
It is supported by Gnus. I don't
On Thu, Apr 26, 2018 at 06:38:54AM +0200, Matthias Apitz wrote:
> El día Wednesday, April 25, 2018 a las 08:23:37PM -0400, Patrick Shanahan
> escribió:
>
> > you might want to reconsider. you said *you* didn't make the setting,
> > that "mutt" was to blame. there really is no "blame". one must
El día Wednesday, April 25, 2018 a las 08:23:37PM -0400, Patrick Shanahan
escribió:
> you might want to reconsider. you said *you* didn't make the setting,
> that "mutt" was to blame. there really is no "blame". one must make the
> settings to do what they wish and you didn't bother and now tr
I'm tired of such blames. I'm using mutt for more then 15
years, IIRC. And of course every day you learn something new or
something I did wrong. But what you send is not help, but just
blames.
Thanks
matthias
--
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱
+49-1
* Matthias Apitz [04-25-18 17:20]:
> El día miércoles, abril 25, 2018 a las 04:14:52p. m. -0400, Patrick Shanahan
> escribió:
>
> > > Who adds this? mutt by its own? If so, based on what?
> >
> >
> > you do, don't you have man pages for mutt and muttrc? mutt doesn't do
> > anything except wha
El día miércoles, abril 25, 2018 a las 04:14:52p. m. -0400, Patrick Shanahan
escribió:
> > Who adds this? mutt by its own? If so, based on what?
>
>
> you do, don't you have man pages for mutt and muttrc? mutt doesn't do
> anything except what *you* tell it to.
no, mutt does it by its own bec
ng changes to your posts,
>>
>> the 'system' is a FreeBSD netbook using mutt+sendmail;
>>
>> I will Cc me on this mail to see its sent headers;
>
> The outgoing mails contains a header line:
>
> Mail-Followup-To: Matthias Apitz , mutt-users
your system makeing changes to your posts,
> >
> > the 'system' is a FreeBSD netbook using mutt+sendmail;
> >
> > I will Cc me on this mail to see its sent headers;
>
> The outgoing mails contains a header line:
>
> Mail-Followup-To: Matthia
00, Matthias Apitz wrote:
> > > > On Wednesday, 25 April 2018 17:17:54 CEST, Patrick Shanahan
> > > > > which he did and does regularily:
> > > > > "Mail-Followup-To: Matthias Apitz ,
> > > > > mutt-users@mutt.org"
> > > &
x27; is a FreeBSD netbook using mutt+sendmail;
>
> I will Cc me on this mail to see its sent headers;
The outgoing mails contains a header line:
Mail-Followup-To: Matthias Apitz , mutt-users@mutt.org
Who adds this? mutt by its own? If so, based on what?
matthias
--
Mat
El día miércoles, abril 25, 2018 a las 02:46:06p. m. -0400, Patrick Shanahan
escribió:
> then you have someone in your system makeing changes to your posts,
the 'system' is a FreeBSD netbook using mutt+sendmail;
I will Cc me on this mail to see its sent headers;
matthias
--
Matthias
gt; > > On Wednesday, 25 April 2018 17:17:54 CEST, Patrick Shanahan
> > > > > which he did and does regularily:
> > > > > "Mail-Followup-To: Matthias Apitz ,
> > > > > mutt-users@mutt.org"
> > > >
> > > > I do not s
ahan
> > > > which he did and does regularily:
> > > > "Mail-Followup-To: Matthias Apitz ,
> > > > mutt-users@mutt.org"
> > >
> > > I do not set this in my mutt.
> >
> > Try adding mutt-users to your 'subscribe'
On Wed, Apr 25, 2018 at 09:28:02AM -0700, Kevin J. McCarthy wrote:
> On Wed, Apr 25, 2018 at 05:56:43PM +0200, Matthias Apitz wrote:
> > On Wednesday, 25 April 2018 17:17:54 CEST, Patrick Shanahan
> > > which he did and does regularily:
> > > "Mail-Followup-To: Ma
On Mon, Oct 25, 2010 at 01:25:53PM -0500, Kyle Wheeler wrote:
> On Saturday, October 23 at 05:45 PM, quoth Mike Hollis:
> > The only problem with this config is I have to use List-Reply for
> > some mail and not for others.
>
> I had this problem (or something similar), and I used hooks to "fix"
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Saturday, October 23 at 05:45 PM, quoth Mike Hollis:
> The only problem with this config is I have to use List-Reply for
> some mail and not for others.
I had this problem (or something similar), and I used hooks to "fix"
it for all intents and
On Sun, Oct 24, 2010 at 02:14:30PM +1100, Cameron Simpson wrote:
> On 23Oct2010 17:45, Mike Hollis wrote:
> | The only problem with this config is I have to use List-Reply for some
> | mail and not for others.
>
> they're usually what I intend and easy to change if not.
>
> I can only suggest s
understand correctly I wiil have Mail-Followup-to header set to the
| mailing list I am responding and responces go to the list rather than to
| me , which is what I want.
|
| The only problem with this config is I have to use List-Reply for some
| mail and not for others.
I confess I always use (&#
On Sat, Oct 23, 2010 at 07:30:22PM -0300, Monte Stevens wrote:
> On Sat, Oct 23, 2010 at 05:45:51PM -0400, Mike Hollis wrote:
> > **suscribe caused only mutt-users@ to be shown in the index
> > ** I wanted to see the posters names
>
> What is your index_format?
> If you are using the default, chan
On Sat, Oct 23, 2010 at 05:45:51PM -0400, Mike Hollis wrote:
> **suscribe caused only mutt-users@ to be shown in the index
> ** I wanted to see the posters names
What is your index_format?
If you are using the default, change the 'L' to 'n'.
(Sorry for excessive trimming, I only wanted to tackle
After reading the docs I have :
set followup_to=yes
set honor_followup_to=yes
lists mutt-users@ some-others@
**suscribe caused only mutt-users@ to be shown in the index
** I wanted to see the posters names
various save-hooks
If I understand correctly I wiil have Mail-Followup-to header set to th
onfig there (should it be "@gary..."?),
>>that mutt knows the mailing list is on my domain and therefore decides
>>not to generate a header (i.e. my test case is wrong) or if it is a bug.
>
> The problem is your alternates setting states that any address at your
>
des
not to generate a header (i.e. my test case is wrong) or if it is a bug.
The problem is your alternates setting states that any address at your domain
is an alias for your personal address. This is probably interferring with the
list detection code. When generating the Mail-Followup-To hea
Christian Ebert writes:
> * Gary on Sunday, May 02, 2010 at 16:28:59 +0200
>> On Tue, Apr 20, 2010 at 11:07:13AM -0700, Michael Elkins wrote:
>>> The idea is to create a rc file and set of actions that demonstrate the
>>> problem. It could be just a bogus mailing list address if you prefer.
>>
>>
* Gary on Sunday, May 02, 2010 at 16:28:59 +0200
> On Tue, Apr 20, 2010 at 11:07:13AM -0700, Michael Elkins wrote:
>> The idea is to create a rc file and set of actions that demonstrate the
>> problem. It could be just a bogus mailing list address if you prefer.
>
> Okay. I have cut it down as mu
On Tue, Apr 20, 2010 at 11:07:13AM -0700, Michael Elkins wrote:
> On Tue, Apr 20, 2010 at 07:46:23PM +0200, Gary wrote:
> >>If you can produce a test muttrc and a test email message that exhibit the
> >>problem
> >
> >Well, it applies to outgoing email, so the latter doesn't really apply,
> >but I
On Tue, Apr 20, 2010 at 07:46:23PM +0200, Gary wrote:
If you can produce a test muttrc and a test email message that exhibit the
problem
Well, it applies to outgoing email, so the latter doesn't really apply,
but I can send my muttrc stripped of comments privately, or somewhat
more stripped to
On Mon, Apr 19, 2010 at 11:14:35PM +0200, Gary wrote:
Please let me know what you want and I will try to.
If you can produce a test muttrc and a test email message that exhibit the
problem, that would be helping for debugging. Typically you want something
standalone, so you will invoke it th
On Mon, Apr 19, 2010 at 08:42:58PM +0200, Gary wrote:
I may be wrong, but despite "set followup_to=yes" in my config file, and
lists + subscribe entries, mutt doesn't seem to be generating this
header correctly. I've got some extra ones being created by my_hdr, but
I don't think that could be int
Hanspeter Roth wrote:
>
> Are there headers used by other MUAs that have similar function like
> Mail-Followup-To and Reply-To?
Well Reply-To: is an internet standard, and is followed by most mailers.
Mail-Followup-To: was an internet draft that never got adopted as a
standard; mutt
Hello,
Are there headers used by other MUAs that have similar function like
Mail-Followup-To and Reply-To?
(Probably some users configure their mailers to ignore such
headers.)
-Hanspeter
* Eduardo Gargiulo <[EMAIL PROTECTED]> [2002-04-17 14:06]:
> I use diferent email addresses to subscribe to diferent lists,
> ejg-mutt for mutt-users and ejg-qmail for qmail lists. I use ejg too.
> Is the following alternetes set appropriately for my scenario?
>
> set alternates="^ejg.*(-mutt|-qm
Eduardo Gargiulo wrote:
>
> I'm running mutt 1.3.28 and i have set followup_to honor_followup_to.
> I want to configure mutt to set mail-followup-to header just only with the
> address of the mailing list i'm posting to, and not with my address.
> Is there any way to do
Michael Tatge <[EMAIL PROTECTED]> wrote:
>
> set alternates appropriately and configure the lists you are subscribed to
> with the subscribe command. If you list-reply to a mailinglist mail
> which has a mft header mutt will only reply to the adresses in the mft
> header.
>
> HTH,
thanks, it wo
Eduardo Gargiulo ([EMAIL PROTECTED]) muttered:
> I'm running mutt 1.3.28 and i have set followup_to honor_followup_to.
Good. :)
> I want to configure mutt to set mail-followup-to header just only with the
> address of the mailing list i'm posting to, and not with my address.
* On 2002.03.15, in <[EMAIL PROTECTED]>,
* "Shawn McMahon" <[EMAIL PROTECTED]> wrote:
> This one time, at band camp, David Champion wrote:
> >
> > Personally, I don't like the idea of hard-coding mutt to recognize
> > mailing lists according to commonly-observed trends that aren't
> > speci
This one time, at band camp, David Champion wrote:
>
> Personally, I don't like the idea of hard-coding mutt to recognize
> mailing lists according to commonly-observed trends that aren't
> specified by a reasonably standard standard. There are many ways
> to identify a mailing list. Mutt shouldn
This one time, at band camp, David T-G wrote:
>
> BTW, subscribe is a superset of lists; you'll only need one for lists on
> which you are and then one for lists on which you aren't.
Yeah, figured that one out after I posted. :-)
> Great. Start coding. Post the result. TIA & HAND
Trust me,
* Shawn McMahon <[EMAIL PROTECTED]> [2002-03-15 10:17:37 -0500]:
> This one time, at band camp, Dave Pearson wrote:
>
> > Perhaps I'm missing something here but I don't use to tell
> > mutt that an email is from a mailing list, I use to tell
> > mutt that I want to respond to the list it was fr
On Mar 15, Shawn McMahon [[EMAIL PROTECTED]] wrote:
> This one time, at band camp, Dave Pearson wrote:
> >
> > Perhaps I'm missing something here but I don't use to tell mutt
> > that an email is from a mailing list, I use to tell mutt that I
> > want to respond to the list it was from (instead
Shawn --
...and then Shawn McMahon said...
%
% This one time, at band camp, Dave Pearson wrote:
% >
% > Perhaps I'm missing something here but I don't use to tell mutt
% > that an email is from a mailing list, I use to tell mutt that I
% > want to respond to the list it was from (instead of t
This one time, at band camp, Dave Pearson wrote:
>
> Perhaps I'm missing something here but I don't use to tell mutt
> that an email is from a mailing list, I use to tell mutt that I
> want to respond to the list it was from (instead of to the author of the
> email, or whatever).
Uh huh. And
On Fri, Mar 15, 2002 at 02:57:36PM +, Dave Pearson wrote:
> * Shawn McMahon <[EMAIL PROTECTED]> [2002-03-15 09:41:11 -0500]:
>
> > Mailing lists aren't easy to recognize, at least when they don't put in a
> > header, but you're forgetting that this will only come up if the user hits
> > the l
* Shawn McMahon <[EMAIL PROTECTED]> [2002-03-15 09:41:11 -0500]:
> Mailing lists aren't easy to recognize, at least when they don't put in a
> header, but you're forgetting that this will only come up if the user hits
> the list-reply key, thereby TELLING mutt that the email was from a list.
Per
On Mar 15, Shawn McMahon [[EMAIL PROTECTED]] wrote:
> This one time, at band camp, Jeremy Blosser wrote:
> >
> > Not for list-reply. The important thing to make this command work is
> > letting mutt know which mails are from lists, using the 'subscribe' and
> > 'lists' commands.
>
> Bleargh. W
This one time, at band camp, David T-G wrote:
>
> So, since lists are so easy to recognize, have a script that generates
> mailing list names from your directories and put something like
Mailing lists aren't easy to recognize, at least when they don't
put in a header, but you're forgetting that
Shawn --
...and then Shawn McMahon said...
%
% This one time, at band camp, Jeremy Blosser wrote:
% >
% > Not for list-reply. The important thing to make this command work is
% > letting mutt know which mails are from lists, using the 'subscribe' and
% > 'lists' commands.
%
% Bleargh. What a
This one time, at band camp, Jeremy Blosser wrote:
>
> Not for list-reply. The important thing to make this command work is
> letting mutt know which mails are from lists, using the 'subscribe' and
> 'lists' commands.
Bleargh. What a pain in the ass. Most of my mailing lists identify
themselv
On Mar 14, Simon White [[EMAIL PROTECTED]] wrote:
> 14-Mar-02 at 12:20, Shawn McMahon ([EMAIL PROTECTED]) wrote :
> > This one time, at band camp, Simon White wrote:
> > >
> > > Ahh yes there is. L (list-reply). Or whatever you map it to in your muttrcs.
> > > Cool.
> >
> > Except it doesn't wor
14-Mar-02 at 12:20, Shawn McMahon ([EMAIL PROTECTED]) wrote :
> This one time, at band camp, Simon White wrote:
> >
> > Ahh yes there is. L (list-reply). Or whatever you map it to in your muttrcs.
> > Cool.
>
> Except it doesn't work with any mailing list I've tried.
I just hit SHIFT-L and this
On Thu, Mar 14, 2002 at 12:20:06PM -0500, Shawn McMahon wrote:
> This one time, at band camp, Simon White wrote:
> >
> > Ahh yes there is. L (list-reply). Or whatever you map it to in your muttrcs.
> > Cool.
>
> Except it doesn't work with any mailing list I've tried.
>
> Including, for example
This one time, at band camp, Simon White wrote:
>
> Ahh yes there is. L (list-reply). Or whatever you map it to in your muttrcs.
> Cool.
Except it doesn't work with any mailing list I've tried.
Including, for example, this one...
msg25508/pgp0.pgp
Description: PGP signature
* Sven Guckes <[EMAIL PROTECTED]> [2002-03-14 15:26:01 +0100]:
> oh - you mean, this Mail-Followup-To is for "extra notification"?
Please actually read what I write. I mean it could be one use for someone.
You asked a question, I provided one possible answer. Once again i
* Dave Pearson <[EMAIL PROTECTED]> [2002-03-14 14:14]:
> > So this Mail-Followup-To seems redundant [on a closed list]
> Could it not be the case that the personal entry in
> Mail-Followup-To might be pointing to an address with which
> the author isn't subscribed to
when I reply to the list you'll get a copy. So this
> Mail-Followup-To seems redundant.
Could it not be the case that the personal entry in Mail-Followup-To might
be pointing to an address with which the author isn't subscribed to the
list? This might be an address they monitor all day
er you map it to
> in your muttrcs. Cool.
exactly. no mailer is complete without such a command.
get the word out to those mail suckers, fellow dog owners!
btw, you can "unset followup_up" to not
generate the Mail-Followup-To line.
Sven
14-Mar-02 at 13:55, Sven Guckes ([EMAIL PROTECTED]) wrote :
> > > > Mail-Followup-To: Simon White <[EMAIL PROTECTED]>,
> > > > Mutt User List <[EMAIL PROTECTED]>
> > > this is a closed list, isn't it?
> > Don't follow... what
r English notes Sven)
*grin*
> > > Mail-Followup-To: Simon White <[EMAIL PROTECTED]>,
> > > Mutt User List <[EMAIL PROTECTED]>
> > this is a closed list, isn't it?
> Don't follow... what am I doing wrong?
well, you have to be subscribed to the l
Michael, et al --
...and then Michael Tatge said...
% David T-G muttered:
% >
% > :set ?charset
% > charset="iso-8859-1"
% >
% > so I should think that it would be fine. Does anyone have any idea what
% > might be up?
%
% What are your LC settings?
%
% Mine are:
% LANG=en_US
% LANGUAGE=e
David T-G muttered:
> % | % René Clerc - ([EMAIL PROTECTED])
>
> Interesting... Your accented e showed up as backslash-three-five-one
> in the pager
> My charset value is
>
> :set ?charset
> charset="iso-8859-1"
>
> so I should think that it would be fine. Does anyon
Rene --
...and then Ren? Clerc said...
% * David T-G <[EMAIL PROTECTED]> [05-12-2001 03:18]:
%
% | :set ?charset
% | charset="iso-8859-1"
%
% So is mine.
Hokay; that makes sense.
%
% | so I should think that it would be fine. Does anyone have any idea what
% | might be up?
%
% Except
* David T-G <[EMAIL PROTECTED]> [05-12-2001 03:18]:
| My charset value is
|
| :set ?charset
| charset="iso-8859-1"
So is mine.
| so I should think that it would be fine. Does anyone have any idea what
| might be up?
Except for this incredibly long list of patches, most values are the
sam
Rene, et al --
...and then Ren? Clerc said...
% * David T-G <[EMAIL PROTECTED]> [04-12-2001 23:41]:
%
% | Rene --
% |
% | ...and then Ren? Clerc said...
...
% | % --
% | % René Clerc - ([EMAIL PROTECTED])
%
% Hmm... you still seem to find three ways to spell my name ;)
I
* David T-G <[EMAIL PROTECTED]> [04-12-2001 23:41]:
| Rene --
|
| ...and then Ren? Clerc said...
(see below)
| Did you postpone in the middle of that message? If you postpone, you
| must be in the same mailbox when you recall and complete in order for the
| flag to be properly updated.
That
Rene --
...and then Ren? Clerc said...
% Something else that strikes me:
Whack!
%
%
%
...
% 593 rs Dec 04 Mark Sheppard( 41) tq>
% 594 S> Dec 04 To Mutt Users( 50) x mq>
% 595 S Dec 04 Will Yardley ( 42) mq
Something else that strikes me:
591 r Dec 04 Will Yardley ( 38) mq>
592 s> Dec 04 To Mutt Users( 74) mq>
593 rs Dec 04 Mark Sheppard( 41) tq>
594 S> Dec 04 To Mutt Users( 50) x mq>
595
* Samuel Padgett <[EMAIL PROTECTED]> [04-12-2001 22:43]:
| Mutt should generate the MFT header based on the people you've
| included in the To: and Cc: headers. If you remove the improperly
| Cc-ed individual from the Cc: header, Mutt should not put that
| person in the MFT header.
I completely
* Mark Sheppard <[EMAIL PROTECTED]> [04-12-2001 22:11]:
| > | true, however if your admin were to add this list to the server (say for
| > | internal lists, or common lists) then you would have no way to change
| > | this (assuming you do not have root access on the machine). if it's
| > | your
* Will Yardley <[EMAIL PROTECTED]> [04-12-2001 22:41]:
[...]
| besides, i don't think you had reply-to set on your message anyway...
| hitting group-reply still honors MFT i'm pretty sure.
You don't have to have a Reply-To header in order for group-reply to
work, do you?
--
René Clerc
Will Yardley <[EMAIL PROTECTED]> writes:
> Ren? Clerc wrote:
>
>> Then you probably have set ignore_list_reply_to=yes (where no = default)
>
> i don't.
>
> zugzug [~]% grep -ri ignore_list_reply .mutt*
> zugzug [~]%
A better test might be
:set ?ignore_list_reply_to
inside of Mutt.
> yes i
Ren? Clerc wrote:
> * Will Yardley <[EMAIL PROTECTED]> [04-12-2001 21:52]:
> | Ren? Clerc wrote:
> | yeah you're correct about 'reply' - my bad. however group-reply i'm
> | pretty sure honors MFT... if i select group-reply, in response to your
> | mail, it is just addressed to the mutt list.
>
On 2001-12-04 (Tuesday) at 21:40:40 +0100, René Clerc wrote:
> * Will Yardley <[EMAIL PROTECTED]> [04-12-2001 21:22]:
> | Josh Huber wrote:
> | >
> | > 1) to have qmail generate the Mail-Followup-To header automatically,
> | >you must have a list of mailing list
* Will Yardley <[EMAIL PROTECTED]> [04-12-2001 21:52]:
| Ren? Clerc wrote:
| >
| > I didn't check for group reply, but when I reply to your mail, it will
| > be sent to you directly, and when I 'L'ist reply, as I'm doing now, it
| > is sent to the list. Strange, I can't think of any directive th
Ren? Clerc wrote:
>
> I didn't check for group reply, but when I reply to your mail, it will
> be sent to you directly, and when I 'L'ist reply, as I'm doing now, it
> is sent to the list. Strange, I can't think of any directive that
> would cause this behaviour...
yeah you're correct about 're
* Will Yardley <[EMAIL PROTECTED]> [04-12-2001 21:22]:
| Josh Huber wrote:
| > Will Yardley writes:
| >
| > Er, a few points:
| >
| > 1) to have qmail generate the Mail-Followup-To header automatically,
| >you must have a list of mailing lists for it to use,
Josh Huber wrote:
> Will Yardley writes:
>
> Er, a few points:
>
> 1) to have qmail generate the Mail-Followup-To header automatically,
>you must have a list of mailing lists for it to use, so unless you
>add addresses to this list, the header won't get generat
o' header to my address, but my mail server,
> running qmail (mine doesn't really) adds a 'Mail-Followup-To' header
> with the list address. Of course i don't use mutt (actually i do,
> but just suppose) so i have no easy way of overriding this header.
>
> now
I have set followup_to in my .muttrc, I have subscribe set (although
only with the first part of the list name, i.e. cvs-all not
[EMAIL PROTECTED] list-reply works fine, but for some reason mutt .24
isn't setting Mail-Followup-To.
Is it only set in original mails, not replies?
Hm, it is
left
to MUAs - even if they are slow to adopt this, it seems as if enforcing
this in an MTA might cause some problems. for instance if i set the
'Reply-To' header to my address, but my mail server, running qmail (mine
doesn't really) adds a 'Mail-Followup-To' header with the list
> > >
>http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-followup-to-00.txt
> > There are many RFC's in use as "standards" that never got beyond being
> > draft standards "officially" I believe.
> well their point seems to
Cliff Sarginson wrote:
> On Mon, Dec 03, 2001 at 10:21:38PM -0800, Will Yardley wrote:
> > the only quasi-official reference i've been able to find on the
> > Mail-Followup-To header is:
> >
> > http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-
On Mon, Dec 03, 2001 at 10:21:38PM -0800, Will Yardley wrote:
> the only quasi-official reference i've been able to find on the
> Mail-Followup-To header is:
>
> http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-followup-to-00.txt
>
> while i think that
the only quasi-official reference i've been able to find on the
Mail-Followup-To header is:
http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-followup-to-00.txt
while i think that this becoming standard would be a Good Thing, since
the draft is from 1997, it would seem unl
1 - 100 of 161 matches
Mail list logo
