I have one more question for those who have the time to answer. I ran a
deleverability test and am getting this warning. *Reverse DNS is not a
Valid Hostname*

What should I do to clear this up? Here is my header once again.

Delivered-To: mikemc...@gmail.com
Received: by 10.36.51.18 with SMTP id k18csp1628559itk;
        Mon, 15 Jun 2015 16:12:14 -0700 (PDT)
X-Received: by 10.52.240.198 with SMTP id wc6mr42953689vdc.34.1434409934009;
        Mon, 15 Jun 2015 16:12:14 -0700 (PDT)
Return-Path: <talk...@inform.mymodeltalk.com>
Received: from mymodeltalk.com (MyModelTalk.com. [52.0.148.79])
        by mx.google.com with ESMTP id
fa3si18397936vdb.22.2015.06.15.16.12.13
        for <mikemc...@gmail.com>;
        Mon, 15 Jun 2015 16:12:13 -0700 (PDT)
Received-SPF: pass (google.com: domain of talk...@inform.mymodeltalk.com
designates 52.0.148.79 as permitted sender) client-ip=52.0.148.79;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of talk...@inform.mymodeltalk.com
designates 52.0.148.79 as permitted sender) smtp.mail=
talk...@inform.mymodeltalk.com;
       dkim=neutral (no signature) header.i=@mymodeltalk.com
Received: from inform.mymodeltalk.com (localhost.localdomain [127.0.0.1])
by mymodeltalk.com (Postfix) with ESMTPA id 5A44333CE4
for <mikemc...@gmail.com>; Mon, 15 Jun 2015 19:12:13 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mymodeltalk.com;
s=default; t=1434409933;
bh=3XaW4YGQFDV4fAXcIZGdCk5JNu/5qoKKTkyrahEnW4o=;
h=Date:To:From:Subject;
b=XeD24kGDfDY1BRGTr4m2ZQxsFva+J11tNuiqi6LEcehPS2L22v2nkWlGFy13D4y/e
 MgWYopilu0I9AbQIhQ6sauNqKvmOsqAwDxjJ38w0HcuPi1lbyTivErtoAkqZZN2BBy
 1CYr3A675di+thsPecbnXYWwLk9G8lQ4CxKFynGc=
Date: Mon, 15 Jun 2015 23:12:13 +0000
To: mikemc...@gmail.com
From: MMT Hot Castings <casti...@mymodeltalk.com>
Subject: Atlanta Daily Casting Call Digest - MyModelTalk
Message-ID: <1be90f23e5ec5cb3112d6555f65b4...@inform.mymodeltalk.com>
X-Priority: 3
X-Mailer: PHPMailer [version 1.73]
X-Mailer: phplist v2.10.19
X-MessageID: 6696
X-ListMember: mikemc...@gmail.com
Errors-To: talk...@inform.mymodeltalk.com
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="b1_1be90f23e5ec5cb3112d6555f65b47d3"


--b1_1be90f23e5ec5cb3112d6555f65b47d3
Content-Type: text/plain; charset = "utf-8"
Content-Transfer-Encoding: 8bit


--
Mike McKoy
*404.590.7176*
http://MyForeverHair.com
http://www.MyModelTalk.com
http://InCrowdUSA.net
http://www.google.com/profiles/mikemckoy

On Mon, Jun 15, 2015 at 9:20 AM, Viktor Dukhovni <postfix-us...@dukhovni.org
> wrote:

> On Mon, Jun 15, 2015 at 08:49:51AM -0400, Mike McKoy wrote:
>
> > Ok i'm the kind of guy you guys probably hate. I'm having header issues
> and
> > getting blocked repeatedly I'm not sure if received from is referring to
> > the hostname but I think it is.
>
> Generally, the "HELO name", which by default Postfix also derives
> from the "myhostname" setting in main.cf.   Your PTR record is
> fine by the way:
>
>     $ dig +noall +ans +nocl +nottl -x 52.0.148.79
>     79.148.0.52.in-addr.arpa. PTR   MyModelTalk.com.
>
> > Received: from ip-172-30-1-113.localdomain (MyModelTalk.com.
> [52.0.148.79])
> >         by mx.google.com with ESMTP id
> n6si7418515qgd.76.2015.06.15.04.23.41
> >         for <mikemc...@gmail.com>;
> >         Mon, 15 Jun 2015 04:23:42 -0700 (PDT)
> > Received-SPF: pass (google.com: domain of i...@mymodeltalk.com
> designates
> > 52.0.148.79 as permitted sender) client-ip=52.0.148.79;
> > Authentication-Results: mx.google.com;
> >        spf=pass (google.com: domain of i...@mymodeltalk.com designates
> > 52.0.148.79 as permitted sender) smtp.mail=i...@mymodeltalk.com
>
> Something is setting "myhostname" or at least "smtp_helo_name" to
> to "ip-172-30-1-113.localdomain".  Don't do that.  Use a real
> domain name, perhaps:
>
>         myhostname = mymodeltalk.com
>
> as reflected in the message id and "From:" headers:
>
> > Message-ID: <20150615111200.b8e087e66...@mymodeltalk.com>
> > From: "MyModelTalk Free Casting Calls for Models and Actors!" <
> i...@mymodeltalk.com>
>
> --
>         Viktor.
>

Reply via email to