I am using Google Apps for email - i’ve setup the TXT record to validate the emails as legitimate, but I am still getting marked and dumped for a lot of clients. Even more annoying is they are generally emailing me from their own accounts first.
Any easy ways to correct and get whitelisted? I am not down for paying some faggot company to whitelist me
email: see if you get a reply with "pass"
moar here:
|
email: see if you get a reply with "pass"
moar here: |
Everything seems to be passing, which is what annoys the shit out of me. dnswl seems to be low, but that is because it is a google email server
This message is an automatic response from Port25′s authentication verifier
service at verifier.port25.com. The service allows email senders to perform
a simple check of various sender authentication mechanisms. It is provided
free of charge, in the hope that it is useful to the email community. While
it is not officially supported, we welcome any feedback you may have at
<[email protected]>.
Thank you for using the verifier,
The Port25 Solutions, Inc. team
================================================== ========
Summary of Results
================================================== ========
SPF check: pass
DomainKeys check: neutral
DKIM check: neutral
Sender-ID check: pass
SpamAssassin check: ham
================================================== ========
Details:
================================================== ========
HELO hostname: mail-qy0-f182.google.com
Source IP: 209.85.216.182
mail-from:
———————————————————-
SPF check details:
———————————————————-
Result: pass
ID(s) verified: [email protected]
DNS record(s):
mydomain.me. SPF (no records)
mydomain.me. 7200 IN TXT "v=spf1 include:_spf.google.com ~all"
_spf.google.com. SPF (no records)
_spf.google.com. 300 IN TXT "v=spf1 ip4:216.239.32.0/19 ip4:64.233.160.0/19 ip4:66.249.80.0/20 ip4:72.14.192.0/18 ip4:209.85.128.0/17 ip4:66.102.0.0/20 ip4:74.125.0.0/16 ip4:64.18.0.0/20 ip4:207.126.144.0/20 ip4:173.194.0.0/16 ?all"
———————————————————-
DomainKeys check details:
———————————————————-
Result: neutral (message not signed)
ID(s) verified: [email protected]
DNS record(s):
———————————————————-
DKIM check details:
———————————————————-
Result: neutral (message not signed)
ID(s) verified:
NOTE: DKIM checking has been performed based on the latest DKIM specs
(RFC 4871 or draft-ietf-dkim-base-10) and verification may fail for
older versions. If you are using Port25′s PowerMTA, you need to use
version 3.2r11 or later to get a compatible version of DKIM.
———————————————————-
Sender-ID check details:
———————————————————-
Result: pass
ID(s) verified: [email protected]
DNS record(s):
mydomain.me. SPF (no records)
mydomain.me. 7200 IN TXT "v=spf1 include:_spf.google.com ~all"
_spf.google.com. SPF (no records)
_spf.google.com. 300 IN TXT "v=spf1 ip4:216.239.32.0/19 ip4:64.233.160.0/19 ip4:66.249.80.0/20 ip4:72.14.192.0/18 ip4:209.85.128.0/17 ip4:66.102.0.0/20 ip4:74.125.0.0/16 ip4:64.18.0.0/20 ip4:207.126.144.0/20 ip4:173.194.0.0/16 ?all"
———————————————————-
SpamAssassin check details:
———————————————————-
SpamAssassin v3.2.5 (2008-06-10)
Result: ham (-3.6 points, 5.0 required)
pts rule name description
—- ———————- ————————————————-
-1.0 RCVD_IN_DNSWL_LOW RBL: Sender listed at , low
trust
[209.85.216.182 listed in list.dnswl.org]
-0.0 SPF_PASS SPF: sender matches SPF record
0.0 HTML_MESSAGE BODY: HTML included in message
-2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1%
[score: 0.0000]
0.0 AWL AWL: From: address is in the auto white-list
standard, but can upgrade if I need to
I’d suggest upgrading (you will get 30 days free), and opening a ticket with them with your issue. If they dont solve it, i can try escalating via enterprise portal.