All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Paul Janzen <pcj@xenomai.sez.to>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Xenomai 3.0-rc3 Interruption on Arietta G25 (AT91SAM9G25 chip)
Date: Thu, 26 Mar 2015 19:58:07 +0100	[thread overview]
Message-ID: <20150326185807.GA15125@hermes.click-hack.org> (raw)
In-Reply-To: <oqk2y3zj6n.fsf@merlin.sez.to>

On Thu, Mar 26, 2015 at 11:51:12AM -0700, Paul Janzen wrote:
> Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org> writes:
> > On Thu, Mar 26, 2015 at 10:08:30AM -0700, Paul Janzen wrote:
> >> Neither your MUA nor the mailing list software insert a
> >> 
> >> Reply-To: xenomai@xenomai.org
> >
> > You should get a resent-to.
> 
> I see Resent-To: in only 0.3% of my xenomai messages.  I assume those
> are the ones that people first replied to the original sender, then
> later on noticed and forwarded again to the mailing list.
> 
> > A proper MUA should display the resent-to header indicating that the
> > mail was bounced. Unfortunately, it seems few people use proper MUAs
> > these days.
> 
> Proper MUA's do not create a "Reply" type message with a To: field
> initialized to the value of Resent-To:.

Of course.

> 
> Proper MUA's create a "Reply" message with a To: field initalized with
> the value of Reply-To:.

The message I was replying to was not a message sent on the xenomai
mailing list. It was a private message. So, the To: field was set to
the sender only. I did not notice, sent the mail. Then did not see
the mail coming to the list, looked at the mail, so it had not been
sent to the list, so bounced the message, again, because it is
easy and has the advantage that the new mail has the same id than
the first mail, so allows eliminating the duplicate.

> 
> I'm simply suggesting that xenomai mailman be configured to include
> this header. Then people would have to consciously edit header fields
> to send to your private account only.

No, the mailman documentation recommends against that, it is a
recipe for sending private mails to the list unintentionally, which
is way worse than the opposite.

-- 
					    Gilles.


  reply	other threads:[~2015-03-26 18:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-23 11:07 [Xenomai] Xenomai 3.0-rc3 Interruption on Arietta G25 (AT91SAM9G25 chip) Tianchi Huang
2015-03-23 22:09 ` Gilles Chanteperdrix
2015-03-24 15:55   ` Tianchi Huang
2015-03-24 16:01     ` Gilles Chanteperdrix
2015-03-24 16:13       ` Gilles Chanteperdrix
2015-03-25  8:58         ` Tianchi Huang
     [not found]           ` <CAJT0owE7vtJDWM289=4cNR_LuUqPWAO60nvg9D0NiTQWeN9Xbg@mail.gmail.com>
2015-03-26 14:31             ` Gilles Chanteperdrix
2015-03-26 14:52               ` Tianchi Huang
2015-03-26 14:54                 ` Gilles Chanteperdrix
2015-03-26 15:19                   ` Tianchi Huang
2015-03-26 15:40                   ` Tianchi Huang
2015-03-26 15:44                     ` Gilles Chanteperdrix
2015-03-26 15:58                       ` Tianchi Huang
2015-03-26 16:00                         ` Gilles Chanteperdrix
2015-03-26 16:26                           ` Tianchi Huang
2015-03-26 16:35                             ` Gilles Chanteperdrix
2015-03-26 16:40                               ` Gilles Chanteperdrix
2015-03-26 16:56                               ` Tianchi Huang
2015-03-26 16:57                                 ` Gilles Chanteperdrix
2015-03-26 17:25                                   ` Tianchi Huang
2015-03-26 14:32             ` Gilles Chanteperdrix
2015-03-26 17:08               ` Paul Janzen
2015-03-26 18:30                 ` Gilles Chanteperdrix
2015-03-26 18:51                   ` Paul Janzen
2015-03-26 18:58                     ` Gilles Chanteperdrix [this message]
2015-03-26 19:32                       ` Paul Janzen
2015-03-26 19:52                         ` Gilles Chanteperdrix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150326185807.GA15125@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=pcj@xenomai.sez.to \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.