> 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? Why does it generate a mail loop in my local postfix? Could it have anything to do with the always_bcc setting? $ postconf always_bcc always_bcc = backups@*otherlocaldomain*.com Would some other MTA deliver the message anyway, or this simply a spam harvesting tactic? The messages don’t seem to generate a valid bounce to a valid address… -- S is for SUSAN who perished of fits T is for TITUS who flew into bits
