Aliases Am I doing it wrong

Help with Setup/Upgrade
1

I create a new aliase and forward it to an external email address (@aol.com)

The mail was then rejected

The mail system

<xxxx@aol.com> (expanded from <xxx@domain.tld>): host
    mailin-02.mx.aol.com[64.12.88.164] said: 521 5.2.1 :  (CON:B1)
    http://postmaster.info.aol.com/errors/554conb1.html (in reply to end of
    DATA command)

If I write directly to this address everything works.

AOL Mail updates DMARC policy to ‘reject’

So the question is, do I use aliases the wrong way or is this a mail-in-a-box config bug?

Cheers

2

Not sure it’s DMARC. Says the link in the SMTP reply:

The IP address has been blocked due to a spike in unfavorable e-mail statistics.

If it’s DMARC, then this would be related to whether the original message was properly DKIM signed. Forwarding via an alias shouldn’t affect that. To diagnose I’d have to see the headers on the message as AOL sees it (you could change the alias to forward to e.g. gmail and copy the headers it sees).

3

OK.

Return-Path: <sender@somedomain.tld>
X-Original-To: tofoward@someotherdomain.tld
Delivered-To: tofoward@someotherdomain.tld
X-policyd-weight:  NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_SPAMCOP=-1.5 NOT_IN_BL_NJABL=-1.5 IN_IPv6_RBL=4.25 (only DNSBL check requested)
Received: from box.mysupermailinabox.box (box.mysupermailinabox.box []) 
    (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
    (No client certificate requested)
    by (Postfix) with ESMTPS id 4D4119AC0241
    for <tofoward@someotherdomain.tld>; Tue,  7 Oct 2014 01:08:59 +0400 (MSK)
X-Greylist: delayed 492 seconds by postgrey-1.34 at box.mysupermailinabox.box; Mon, 06 Oct 2014 23:08:58 CEST
Received: from ( []) 
    by box.mysupermailinabox.box (Postfix) with ESMTP id 7A76B801E3
    for <aliase@mysupermailinabox.box>; Mon,  6 Oct 2014 23:08:58 +0200 (CEST)
Received: from [home] (somewhere []) 
    (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
    (No client certificate requested)
    (Authenticated sender: sender@somedomain.tld)
    by somedomain.tld (Postfix) with ESMTPSA id 154419AC0241
    for <aliase@mysupermailinabox.box>; Tue,  7 Oct 2014 01:00:44 +0400 (MSK)
Message-ID: <543302FB.2010308@xxxx>
Date: Mon, 06 Oct 2014 23:00:43 +0200
From: Sender <sender@somedomain.tld>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0 
To: aliase@mysupermailinabox.box
Subject: Test Mail
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi there

The sender sender@somedomain.tld sent an email to aliase@mysupermailinabox.box and the box forward it to tofoward@someotherdomain.tld

sender@somedomain.tld and tofoward@someotherdomain.tld are on the same box (not a mail-in-box installation, but soon :smile: ). And aliase@mysupermailinabox.box is a mail-in-a-box installation

@Edit Next try with gmail, i think this one is a bit better

Delivered-To: tofoward@someotherdomain.tld
Received: by 10.27.217.133 with SMTP id q127csp216015wlg;
        Mon, 6 Oct 2014 14:37:07 -0700 (PDT)
X-Received: by 10.152.170.227 with SMTP id ap3mr27753791lac.15.1412631426928;
        Mon, 06 Oct 2014 14:37:06 -0700 (PDT)
Return-Path: <sender@somedomain.tld>
Received: from box.mysupermailinabox.box ()
        by mx.google.com with ESMTPS id ao5si25854066lbc.58.2014.10.06.14.37.06
        for <tofoward@someotherdomain.tld>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Mon, 06 Oct 2014 14:37:06 -0700 (PDT)
Received-SPF: none (google.com: sender@somedomain.tld does not designate permitted sender hosts) client-ip={Box's IP};
Authentication-Results: mx.google.com;
       spf=neutral (google.com: sender@somedomain.tld does not designate permitted sender hosts) smtp.mail=sender@somedomain.tld
Received: from sender.domain.tld ()
    by box.mysupermailinabox.box (Postfix) with ESMTP id CE911801E3
    for <aliase@mysupermailinabox.box>; Mon,  6 Oct 2014 23:37:05 +0200 (CEST)
Received: from [home] (somewhere)
    (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
    (No client certificate requested)
    (Authenticated sender: sender@somedomain.tld)
    by sender.domain.tld (Postfix) with ESMTPSA id 00DED9AC0241
    for <aliase@mysupermailinabox.box>; Tue,  7 Oct 2014 01:37:04 +0400 (MSK)
Message-ID: <54330B80.5060208@dev-nu11.de>
Date: Mon, 06 Oct 2014 23:37:04 +0200
From: Some nice guy <sender@somedomain.tld>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0 
To: aliase@mysupermailinabox.box
Subject: Test
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Hi There gmail
4

Yeah gmail is helpful because it reports SPF and DMARC results, although in this case there’s no DMARC result so it’s probably not set for the domain anyway. The mail looks fine. AOL is probably just confused about the reputation of the IP address of your box?

5

Yes, this could be the reason. Thank you. My IP address is not blacklisted by spamhouse, but it is blacklisted by

Don’t know why, this is a new box / ip address i get from my provider 4 days ago and i don’t think its mail-in-a-box fault. I think the previous owner of the ip address is the problem. Damn it!

But thank you Josh for looking into this.

6

Submit a pull request to add automated checks for those blacklists? :slight_smile:

7

Good idea. First I have to gather more addresses :stuck_out_tongue: