Am 18.04.2014 17:37, schrieb Steffan A. Cline:
> Clearly this list is for postfix related issues which I do use regularly
> but there is a great deal of respected expertise here and am hoping
> someone will have come across this before.
> 
> I¹ve run into an issue with a postfix server I set up for a friend when
> connecting to Gmail. The message returned contains the following headers
> but has varied until finally just this:
> 
> <azgoldsavi...@gmail.com> <mailto:azgoldsavi...@gmail.com>: host
>     gmail-smtp-in.l.google.com[2607:f8b0:400e:c01::1a] said: 550-5.7.1
>     [2605:d400:0:b:216:3eff:fe63:ca2f      12] Our system has detected
>     550-5.7.1 that this message is likely unsolicited mail. To reduce the
>     amount of 550-5.7.1 spam sent to Gmail, this message has been blocked.
>     Please visit 550-5.7.1
>     http://support.google.com/mail/bin/answer.py?hl=en&answer=188131 for
> 550
>     5.7.1 more information. sf3si14947663pac.452 - gsmtp (in reply to end
> of
>     DATA command)
> 
> From using some of the generic tools out there that test your mail server,
> the configuration I have seems to be working correctly.
> 
> 
> The messages are not unsolicited spam. He has a service that people sign
> up for and then he communicates the sales options.
> 
> I have moved his server to different IPs. That worked for only a few
> messages then back to these headers.
> 
> The SPF is as follows:
> 
> ;; ANSWER SECTION:
> saguarogold.net.      38400   IN      TXT     "v=spf1 ip4:65.39.69.253 ?all²
> 
> rDNS - 
> ;; ANSWER SECTION:
> 253.69.39.65.in-addr.arpa. 86400 IN   PTR     mail.saguarogold.net.
> 
> Postfix also answers for another domain on the same server but next IP.
> 
> 
> 
> ;; ANSWER SECTION:
> goldsavings.com.      38400   IN      TXT     "v=spf1 ip4:65.39.69.254 ?all"
> 
> rDNS - 
> ;; ANSWER SECTION:
> 254.69.39.65.in-addr.arpa. 86400 IN   PTR     mail.goldsavings.com.
> 
> 
> Both domains have the same issue with Gmail.
> 
> 
> Reading on their site, they talk about DKIM and DMARC.
> 
> Is anyone using these and are they effective for this issue?
> 
> Suggestions?
> 
> Has anyone else successfully combatted these issues with gmail?
> 
> I have filled out the gmail form to report the issue several times with no
> changes.
> 
> 
> Thanks
> 
> Steffan
> 
> 
> 

If you use ipv6, use an ip4 special transport for google
they simply have problems with ipv6

i.e like this

http://tanguy.ortolo.eu/blog/article109/google-ipv6-smtp-restrictions

dont forget include your ipv6 address in spf for domain and mailhost
prefer TXT before SPF record, or have both matching

additional check mailhost A/PTR/HELO matching


Best Regards
MfG Robert Schetterer

-- 
[*] sys4 AG

http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München

Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein

Reply via email to