On 4 Mar 2015, at 12:24, Viktor Dukhovni wrote:
On Wed, Mar 04, 2015 at 11:57:52PM +1100, James Brown wrote:
Just had one today. It was originally sent on 26 Feb, the wrong user
just had it delivered today.
Are you sure it is the same message?
The transactions showed the same message-id and the delivered headers
that he quoted had Received headers for transactions on both days:
On 4 Mar 2015, at 7:57, James Brown wrote:
> Header info on message that was delivered to adam:
>
> Return-Path: <scan...@bordo.com.au>
> Delivered-To: a...@bordo.com.au
> Received: from mail.bordo.com.au (localhost [127.0.0.1])
> by mail.bordo.com.au (Postfix) with ESMTP id 279374563492
> for <a...@bordo.com.au>; Wed, 4 Mar 2015 22:15:15 +1100 (EST)
> X-Assp-Resend-Blocked: mail.bordo.com.au
> Received: from [192.168.1.78] ([192.168.1.78] helo=[192.168.1.78])
> bymail.bordo.com.au with SMTPA (2.4.4); 26 Feb 2015 09:40:46
+1100.
It looks like ASSP (full name: "Anti-Spam SMTP Proxy" and it is *sorta*
that...) regurgitated an old message that it had already transferred a
week earlier but sent it to the address in the From header instead of
the SMTP envelope. Why? I have no idea specifically but I do have some
experience with ASSP being generally shoddy and it's a fair bet that
this case falls into that category.
IOW: This is like a question involving Mailscanner or Cisco firewalls:
not worth subtle analysis because a nuanced fix just enables a shoddy
tool to remain.
