Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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 > > > $ > > > > > > as I said, I

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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 set, > Mutt will

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

On 27.04.18 08:57, 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 configuration. > > However, if there

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

* 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. > >

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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 > > > away from

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

* Kevin J. McCarthy [04-27-18 11:47]: > 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

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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 would be

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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-To: > > and From: is quite

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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 proper address

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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 adopted by

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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 know of any others,

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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/ 

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

* 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 > >

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

Matthias Apitz wrote: > El día miércoles, abril 25, 2018 a las 08:56:26p. m. +0200, Matthias Apitz > escribió: > >> 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

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

* Matthias Apitz [04-25-18 15:08]: > El día miércoles, abril 25, 2018 a las 08:56:26p. m. +0200, Matthias Apitz > escribió: > > > 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

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

On Wed, Apr 25, 2018 at 07:31:20PM +0200, Matthias Apitz wrote: > El día Wednesday, April 25, 2018 a las 10:24:45AM -0700, Will Yardley > escribió: > > > 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: > > >

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

El día miércoles, abril 25, 2018 a las 08:56:26p. m. +0200, Matthias Apitz escribió: > 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

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

bq.com > chromium-os-disc...@chromium.org x...@freebsd.org gnupg-us...@gnupg.org > > $ 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; then you have someone in your system makeing

Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

El día Wednesday, April 25, 2018 a las 10:24:45AM -0700, Will Yardley escribió: > 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

Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)

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: Matthias Apitz ,

Re: breaking long header lines into 2 (or more) lines

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: Matthias Apitz , > > mutt-users@mutt.org" > > I do not set this in my mutt. Try adding

Re: breaking long header lines into 2 (or more) lines

On Wednesday, 25 April 2018 17:17:54 CEST, Patrick Shanahan wrote: * Ian Zimmerman [04-25-18 10:42]: On 2018-04-25 08:10, Matthias Apitz wrote: > > Please don't Cc: me privately on mailing lists and Usenet, if you > > also post the followup to the

Re: breaking long header lines into 2 (or more) lines

* Ian Zimmerman [04-25-18 10:42]: > On 2018-04-25 08:10, Matthias Apitz wrote: > > > > Please don't Cc: me privately on mailing lists and Usenet, if you > > > also post the followup to the list or newsgroup. To reply privately > > > _only_ on Usenet and on broken lists

Re: breaking long header lines into 2 (or more) lines

On 2018-04-25 08:10, Matthias Apitz wrote: > > Please don't Cc: me privately on mailing lists and Usenet, if you > > also post the followup to the list or newsgroup. To reply privately > > _only_ on Usenet and on broken lists which rewrite From, fetch the > > TXT record for no-use.mooo.com. > >

Re: breaking long header lines into 2 (or more) lines

El día martes, abril 24, 2018 a las 10:45:11p. m. -0700, Ian Zimmerman escribió: > That is odd, it shouldn't work. According to the RFC cited elsewhere in > thread. > > -- > Please don't Cc: me privately on mailing lists and Usenet, > if you also post the followup to the list or newsgroup. >

Re: breaking long header lines into 2 (or more) lines

On 2018-04-24 10:06, Matthias Apitz wrote: > Long header lines can be split into 2 or more lines and the 2nd line > must start with a blank (is TAB allowed too). Is there any rule (RFC) > at which char the split is allowed or not allowed? For example, can > mail addr lines be broken at any point

Re: breaking long header lines into 2 (or more) lines

On Tue, Apr 24, 2018 at 10:06:49AM +0200, Matthias Apitz wrote: Hello, Long header lines can be split into 2 or more lines and the 2nd line must start with a blank (is TAB allowed too). Is there any rule (RFC) at which char the split is allowed or not allowed? For example, can mail addr lines

breaking long header lines into 2 (or more) lines

Hello, Long header lines can be split into 2 or more lines and the 2nd line must start with a blank (is TAB allowed too). Is there any rule (RFC) at which char the split is allowed or not allowed? For example, can mail addr lines be broken at any point like this one: To: mutt-users@mut t.org