qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Eric Blake <eblake@redhat.com>,
	Marcel Apfelbaum <marcel@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Laszlo Ersek <lersek@redhat.com>,
	peter.maydell@linaro.org, Stefan Hajnoczi <stefanha@redhat.com>
Cc: drjones@redhat.com, mst@redhat.com, qemu-devel@nongnu.org,
	abologna@redhat.com, kraxel@redhat.com, laine@redhat.com
Subject: Re: [Qemu-devel] [PATCH V2] docs: add PCIe devices placement guidelines
Date: Thu, 13 Oct 2016 17:04:00 +0300	[thread overview]
Message-ID: <7877fd3e-ac12-9df9-8639-8d772f49d177@gmail.com> (raw)
In-Reply-To: <da242ad3-9126-4108-e79a-5f53b2485c97@redhat.com>

On 10/13/2016 04:12 PM, Eric Blake wrote:
> On 10/13/2016 05:53 AM, Marcel Apfelbaum wrote:
>> On 10/13/2016 12:38 PM, Paolo Bonzini wrote:
>>>
>>>
>>> On 13/10/2016 11:11, Marcel Apfelbaum wrote:
>>>> Agreed, I sent the patch with both Red Hat and Google SMTP and each time
>>>> was rejected by the server for the recipient domain nongnu.org by
>>>> eggs.gnu.org. [2001:4830:134:3::10].
>>>>
>>>> The error that the other server returned was: 550 Invalid address in
>>>> message header
>>>
>>> You have an "alex.williamson@redhat.comberrange"@redhat.com address that
>>> looks seriously invalid. :)
>>>
>>
>> Yes, I saw that - we have 2 lucky people not spammed (yet),
>> but sadly is uncorrelated with the issue in hand.
>
> How so? It could very well be that the list engine is refusing to
> deliver the mail because the mail has an invalid To: header (you left
> out a comma, creating a single invalid address instead of two desired
> addresses).  Your outgoing SMTP is delivering to as many valid addresses
> as possible, but the list engine is unable to rewrite the message for
> distribution to the list as soon as it encounters something invalid.
>

Hi Eric,

Indeed, I sent the patch again, this time to QEMU list only and it was sent OK.

I didn't think this was the problem because:
   (a) some addresses did receive the message
   (b) I thought I didn't mess up the mails on my first mail, but I was wrong.

Anyway, thank you for the explanation, you and Paolo are right.
Marcel

      reply	other threads:[~2016-10-13 14:04 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1476193521-29034-1-git-send-email-marcel@redhat.com>
2016-10-12 15:28 ` [Qemu-devel] [PATCH V2] docs: add PCIe devices placement guidelines Laszlo Ersek
2016-10-13  7:25   ` Marcel Apfelbaum
2016-10-13  8:53     ` Laszlo Ersek
2016-10-13  9:11       ` Marcel Apfelbaum
2016-10-13  9:38         ` Paolo Bonzini
2016-10-13 10:53           ` Marcel Apfelbaum
2016-10-13 13:12             ` Eric Blake
2016-10-13 14:04               ` Marcel Apfelbaum [this message]

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=7877fd3e-ac12-9df9-8639-8d772f49d177@gmail.com \
    --to=marcel.apfelbaum@gmail.com \
    --cc=abologna@redhat.com \
    --cc=drjones@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=laine@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).