On 26/03/15 13:47, Reindl Harald wrote:
that below was *one* message with two different recipients
X-Spam-Status: No, score=-10.1, tag-level=5.5, block-level=8.0
X-Spam-Status: No, score=-8.1, tag-level=5.5, block-level=8.0
I hate to piss on your parade, but your example here is totally flawed;
this mail from from Gmail right?
X-Local-Envelope-From: <reindl.har...@gmail.com>
X-Local-Envelope-To: <h.rei...@thelounge.net>
Received: from mail-ig0-f171.google.com
Message-ID:
<caacbkvp4dpczlhodtuvugcfq9pat10yozsaum_7k9ositbo...@mail.gmail.com>
X-Local-Envelope-From: <reindl.har...@gmail.com>
X-Local-Envelope-To: <ha...@rhsoft.net>
Received: from mail-ie0-f177.google.com
Message-ID:
<caacbkvp4dpczlhodtuvugcfq9pat10yozsaum_7k9ositbo...@mail.gmail.com>
Gmail splits multi-recipient mail into separate deliveries, so whilst
you sent a single message to multiple recipients at your domain from
Gmail, what the big Goog does is turn that into two separate messages
that are delivered separately.
Whilst the messages have identical Message-ID headers - you missed this bit:
> Received: from mail-ig0-f171.google.com
> Received: from mail-ie0-f177.google.com
Your single message was delivered by two different hosts, with a single
recipient in each.
If you actually got a real message to multiple recipients in one SMTP
transaction, you can't accept one and reject the other once you've
entered the DATA phase because your decision becomes binary at that
point: either accept, defer or reject the message for *all* recipients
as David points out.
Regards,
Steve.
