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. > > Hmmm? You Cc'ed me :-) Sorry about that, but it is because the list is of the munging variety (namely, it adds a Reply-To header). I refuse to spend energy compensating for that borkage. Unless you did that yourself, of course - but I'm giving you the benefit of the doubt ;-) -- 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
* 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 which rewrite From, fetch the > > > TXT record for no-use.mooo.com. > > > > Hmmm? You Cc'ed me :-) > > Sorry about that, but it is because the list is of the munging variety > (namely, it adds a Reply-To header). I refuse to spend energy > compensating for that borkage. > > Unless you did that yourself, of course - but I'm giving you the benefit > of the doubt ;-) which he did and does regularily: "Mail-Followup-To: Matthias Apitz , mutt-users@mutt.org" -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
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 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. > > Hmmm? You Cc'ed me :-) Sorry about that, but it is because the list is of the munging variety (namely, it adds a Reply-To header). I refuse to spend energy compensating for that borkage. Unless you did that yourself, of course - but I'm giving you the benefit of the doubt ;-) which he did and does regularily: "Mail-Followup-To: Matthias Apitz , mutt-users@mutt.org" I do not set this in my mutt. mstthias -- Sent from my Ubuntu phone http://www.unixarea.de/
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 mutt-users to your 'subscribe' lists, instead of 'lists'. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
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 , > > > mutt-users@mutt.org" > > > > I do not set this in my mutt. > > Try adding mutt-users to your 'subscribe' lists, instead of 'lists'. 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. w
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 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' lists, instead of 'lists'. > > 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. > > w > $ grep mutt-users ~/.muttrc send-hook mutt-users@mutt.org 'my_hdr From: Matthias Apitz ' send-hook mutt-users@mutt.org 'my_hdr Reply-To: Matthias Apitz ' lists asterisk-us...@lists.digium.com biblio-progresis...@yahoogrupos.com.mx b...@berklix.org commun...@lists.openmoko.org digikam-us...@kde.org ekiga-devel-l...@gnome.org ekiga-l...@gnome.org enlightenment-us...@lists.sourceforge.net fgcuba-muc-inter...@listen.einewelthaus.de freebsd-...@freebsd.org freebsd-curr...@freebsd.org freebsd-hack...@freebsd.org freebsd-i...@freebsd.org freebsd-j...@freebsd.org freebsd-mob...@freebsd.org freebsd-multime...@freebsd.org freebsd-...@freebsd.org freebsd-po...@freebsd.org freebsd-questi...@freebsd.org freebsd-...@freebsd.org free...@es.freebsd.org gnomemeeting-l...@gnome.org gphoto-u...@lists.sourceforge.net gpsd-us...@lists.berlios.de kde-free...@freebsd.kde.org kde-free...@kde.org l-chix...@glove.org.ve linu...@listas.softwarelibre.cu evolution-l...@gnome.org local-openmoko-sp...@projects.openmoko.org mplayer-us...@mplayerhq.hu mutt-users@mutt.org openmoko-ker...@lists.openmoko.org ubuntu-ph...@lists.launchpad.net betatesters-m10_ubu...@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; matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines)
* Matthias Apitz [04-25-18 14:07]: > 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 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' lists, instead of 'lists'. > > > > 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. > > > > w > > > > > $ grep mutt-users ~/.muttrc > send-hook mutt-users@mutt.org 'my_hdr From: Matthias Apitz > ' > send-hook mutt-users@mutt.org 'my_hdr Reply-To: Matthias > Apitz ' > lists asterisk-us...@lists.digium.com biblio-progresis...@yahoogrupos.com.mx > b...@berklix.org commun...@lists.openmoko.org digikam-us...@kde.org > ekiga-devel-l...@gnome.org ekiga-l...@gnome.org > enlightenment-us...@lists.sourceforge.net > fgcuba-muc-inter...@listen.einewelthaus.de freebsd-...@freebsd.org > freebsd-curr...@freebsd.org freebsd-hack...@freebsd.org > freebsd-i...@freebsd.org freebsd-j...@freebsd.org freebsd-mob...@freebsd.org > freebsd-multime...@freebsd.org freebsd-...@freebsd.org > freebsd-po...@freebsd.org freebsd-questi...@freebsd.org > freebsd-...@freebsd.org free...@es.freebsd.org gnomemeeting-l...@gnome.org > gphoto-u...@lists.sourceforge.net gpsd-us...@lists.berlios.de > kde-free...@freebsd.kde.org kde-free...@kde.org l-chix...@glove.org.ve > linu...@listas.softwarelibre.cu evolution-l...@gnome.org > local-openmoko-sp...@projects.openmoko.org mplayer-us...@mplayerhq.hu > mutt-users@mutt.org openmoko-ker...@lists.openmoko.org > ubuntu-ph...@lists.launchpad.net betatesters-m10_ubu...@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 changes to your posts, Date: Wed, 25 Apr 2018 19:31:20 +0200 From: Matthias Apitz To: mutt-users@mutt.org Subject: Re: Mail-Followup-To (was Re: breaking long header lines into 2 (or more) lines) X-Spam-Level: X-Spam-Status: No X-Original-To: paka X-Original-To: mutt-users@mutt.org Mail-Followup-To: Matthias Apitz , mutt-users@mutt.org User-Agent: Mutt/1.5.24 (2015-08-30) Reply-To: Matthias Apitz X-Envelope-From: mutt-users-boun...@mutt.org Lines: 57 -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
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 Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
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 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 -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
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: > > > > 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 mutt-users to your 'subscribe' lists, instead of 'lists'. ^ ^ ^ For mailing lists that you are subscribed to, you should use the 'subscribe' command, not the 'lists' command. > $ grep mutt-users ~/.muttrc > send-hook mutt-users@mutt.org 'my_hdr From: Matthias Apitz > ' > send-hook mutt-users@mutt.org 'my_hdr Reply-To: Matthias > Apitz ' > lists asterisk-us...@lists.digium.com biblio-progresis...@yahoogrupos.com.mx > b...@berklix.org commun...@lists.openmoko.org digikam-us...@kde.org > ekiga-devel-l...@gnome.org ekiga-l...@gnome.org > enlightenment-us...@lists.sourceforge.net > fgcuba-muc-inter...@listen.einewelthaus.de freebsd-...@freebsd.org > freebsd-curr...@freebsd.org freebsd-hack...@freebsd.org > freebsd-i...@freebsd.org freebsd-j...@freebsd.org freebsd-mob...@freebsd.org > freebsd-multime...@freebsd.org freebsd-...@freebsd.org > freebsd-po...@freebsd.org freebsd-questi...@freebsd.org > freebsd-...@freebsd.org free...@es.freebsd.org gnomemeeting-l...@gnome.org > gphoto-u...@lists.sourceforge.net gpsd-us...@lists.berlios.de > kde-free...@freebsd.kde.org kde-free...@kde.org l-chix...@glove.org.ve > linu...@listas.softwarelibre.cu evolution-l...@gnome.org > local-openmoko-sp...@projects.openmoko.org mplayer-us...@mplayerhq.hu > mutt-users@mutt.org openmoko-ker...@lists.openmoko.org > ubuntu-ph...@lists.launchpad.net betatesters-m10_ubu...@bq.com > chromium-os-disc...@chromium.org x...@freebsd.org gnupg-us...@gnupg.org Try changing the above line to use the 'subscribe' command (or at least move mutt-users@mutt.org to a separate 'subscribe' command if you aren't subscribed to all of those). Otherwise Mutt is interpreting it as a mailing list, but not one that you are subscribed too, and is adding your address in the Mail-Followup-To header. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA signature.asc Description: PGP signature
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 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@mutt.org > > 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. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
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 '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@mutt.org > > Who adds this? mutt by its own? If so, based on what? Quoting http://mutt.org/doc/manual/#followup-to 3.72. followup_to Type: boolean Default: yes Controls whether or not the “Mail-Followup-To:” header field is generated when sending mail. When set, Mutt will generate this field when you are replying to a known mailing list, specified with the “subscribe” or “lists” commands. This field has two purposes. First, preventing you from receiving duplicate copies of replies to messages which you send to mailing lists, and second, ensuring that you do get a reply separately for any messages sent to known lists to which you are not subscribed. The header will contain only the list's address for subscribed lists, and both the list address and your own email address for unsubscribed lists. Without this header, a group reply to your message sent to a subscribed list will be sent to both the list and your address, resulting in two copies of the same email for you. That's why Kevin suggested setting 'subscribe' for the mutt list in your config. The 'honor_followup_to' variable is related, relevant for mutt users replying to messages with a 'Mail-Follup-To:' header. -- Todd ~~ The state is the great fictitious entity by which everyone seeks to live at the expense of everyone else. -- Fredric Bastiat signature.asc Description: PGP signature
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 because the default of 'followup_to' is yes; IMHO it should be changed to 'no'. matthias -- Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
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 > > anything except what *you* tell it to. > > no, mutt does it by its own because the default of 'followup_to' is yes; IMHO > it > should be changed to 'no'. you are but one person and mutt has been around > 20 years and defaults modified to fit a majority. perhaps you can make a compelling case to change the default. but if *you* want it different, you will have to campaign for the change. usually when one begins to use an application, they make an effort to set the parameters to fit their style. you apparently have not felt the necessity to do so, past claiming the application was doing something you did not set it to. which you have found was incorrect. did you look at the defaults before using mutt? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri Registered Linux User #207535@ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
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/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
Question about saving sent mail to current mailbox
I've been dealing with an error whenever mutt starts for a few years now, and finally decided to ask how others have fixed the issue. I have all my sent email saved in the current mailbox. I do this using the following setting in my muttrc (per https://gitlab.com/muttmua/mutt/wikis/MuttFaq/Folder). #v+ folder-hook . "set record=^" #v- As a result, every time I start mutt I get the following errors. #v+ Error in /home/dave/.mutt/general.muttrc, line 25: current mailbox shortcut '^' is unset Error in /home/dave/.mutt/muttrc, line 3: source: errors in /home/dave/.mutt/general.muttrc source: errors in /home/dave/.mutt/muttrc #v- I would like to be able to have the same behavior (record gets set to the current mailbox in every mailbox I visit), but without the error or enumerating all mailboxes in folder-hooks. What are you (the wider mutt community) doing about those errors? If you're not seeing the errors, then what am I doing wrong? Regards, -- dave [ please don't CC me ] signature.asc Description: PGP signature
Re: Question about saving sent mail to current mailbox
* David J. Weller-Fahy [2018-04-25 21:38 -0400]: I've been dealing with an error whenever mutt starts for a few years now, and finally decided to ask how others have fixed the issue. #v+ folder-hook . "set record=^" #v- Sigh... apparently inspiration required that I send an email to a mailing list before figuring this out. The error was NOT the line quoted above, but the folder-hook two lines below it that did not escape the ^. One should look at the ones place in the line number, not just the tens place, when verifying that the line one thinks is causing the error is indeed the line causing the error. Apologies for the noise. -dave -- dave [ please don't CC me ] signature.asc Description: PGP signature
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 try to divert > the responsibility. Wrong. There a good and bad defaults. And the default for follow_up policy is just bad because it does, as you see in my case, things that the user newer wanted and not even was aware of. > make the correct settings and you will get what you wish. > > btw, it is not corrected yet. I know. But I have not had time to think what exactly I will change. matthias -- Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/ 📱 +49-176-38902045 Public GnuPG key: http://www.unixarea.de/key.pub
