On 12 Feb 2015, at 08:25 , Noel Jones <njo...@megan.vbhcs.org> wrote:
> On 2/12/2015 12:43 AM, LuKreme wrote:
>> 
>>> On Feb 11, 2015, at 6:20 PM, Wietse Venema <wie...@porcupine.org> wrote:
>>> 
>>> LuKreme:
>>>> Received: from thenewestsecret.net (unknown [170.130.246.215])
>>>>       by mail.covisp.net (Postfix) with ESMTP id 00E42212DC0
>>>>       for <*bob*@covisp.net>; Tue, 10 Feb 2015 08:53:22 -0700 (MST)
>>>> Delivered-To: *bob*@covisp.net
>>>> Received: by 170.130.246.215 with SMTP id 
>>>> 998S7h4.33K03w6s2R18O2.22351x4s23d1n26;
>>>>       Tue, 10 Feb 2015 08:51:05 -0700 (PST)
>>>> X-Received: by 170.130.246.215 with SMTP id 134G6f10K6Z34b712c43li;
>>>>       Tue, 10 Feb 2015 08:51:05 -0700 (PST)
>>>> Received: from thenewestsecret.net (thenewestsecret.net. )
>>>>       by mx.google.com with ESMTP id 
>>>> 59333u4l19.1C4P11z.147.0.5.1.2.5.5.5.1.0.7.0.4
>>>>       for <*bob*@covisp.net>;
>>>>       Tue, 10 Feb 2015 08:51:05 -0700 (PST)
>>>> Mime-Version: 1.0
>>>> Date: 
>>>> Message-Id: <235.946____781y2r0b6qn6-c...@thenewestsecret.net>
>>>> To: *bob*@covisp.net
>>> 
>>> This message contains a Delivered-To: *bob*@covisp.net header.
>>> Apparently, the sender added this to trigger a delivery error.
>>> Apparently, the sender, c...@thenewestsecret.net, wants to receive
>>> a bounce message. That message would confirm that *bob*@covisp.net
>>> is a valid email address.
>> 
>> Does it make sense to reject messages with a Delivered-To: header?
> 
> Yes.  Incoming mail with that header cannot be delivered by postfix,
> regardless whether it's really looping or not.
> 
> Although in this particular case it might be better to reject the
> spammy-looking client.

Yes, but my postscreen is already aggressive enough that I had to tone it down 
a tad to let some legitimate mail (well, mail I wanted) in.

>> Why does it generate a mail loop in my local postfix?
> 
> The presence of that header triggers the loop detection in postfix.
> The sender is adding that header either in a misguided attempt to
> improve delivery, or to intentionally cause a bounce to verify the
> address.

What is interesting is that I see these *only* for one specific user, which is 
what made me think it was something on my end.

> We don't know the motive of the sender. We do know this isn't really
> a loop and it looks like spam to me.

Oh, they are all spam so far.

Thanks.

-- 
'Luck is my middle name,' said Rincewind, indistinctly. 'Mind you, my
first name is Bad.' --Interesting Times

Reply via email to