Just another "Cannot send only to Gmail" topic

Use this forum if you have installed hMailServer and want to ask a question related to a production release of hMailServer. Before posting, please read the troubleshooting guide. A large part of all reported issues are already described in detail here.
Post Reply
adrianmihai83
New user
New user
Posts: 14
Joined: 2018-01-26 17:19

Just another "Cannot send only to Gmail" topic

Post by adrianmihai83 » 2018-01-26 19:04

Dear all,

Well, I did search for results about this before posting here, also contacted Google via the contact form and provided every detail possible. I have checked that I have MX, PTR, SPF, DKIM, DMARC setup correctly:

https://intodns.com/fsgaz.ro
https://mxtoolbox.com/domain/fsgaz.ro/

Problem is that I cannot send to Gmail, to be more precise, Gmail rejects my email with: "Remote server replied: 550-5.7.1 [81.180.119.90 19] Our system has detected that this message is 550-5.7.1 likely suspicious due to the very low reputation of the sending 550-5.7.1 domain."

Code: Select all

Return-Path: 
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Return-Path: <>
Message-ID: <4C42C2BB-5AEA-4E7D-AE6D-35A0B8B6ACB3@mail.fsgaz.ro>
Date: Fri, 26 Jan 2018 18:03:46 +0200
From: mailer-daemon@mail.fsgaz.ro
To: admin@fsgaz.ro
Subject: Message undeliverable: test catre gmail
Content-Transfer-Encoding: quoted-printable
X-hMailServer-LoopCount: 1

Your message did not reach some or all of the intended recipients.\r\n\r\n   Sent: Fri, 26 Jan 2018 18:03:46 +0200\r\n   Subject: test catre gmail\r\n\r\nThe following recipient(s) could not be reached:\r\n\r\nadrianmihai83@gmail.com
   Error Type: SMTP
   Remote server (74.125.133.27) issued an error.
   hMailServer sent: .
   Remote server replied: 550-5.7.1 [81.180.119.90      19] Our system has detected that this message is
550-5.7.1 likely suspicious due to the very low reputation of the sending
550-5.7.1 domain. To best protect our users from spam, the message has been
550-5.7.1 blocked. Please visit
550 5.7.1  https://support.google.com/mail/answer/188131 for more information. g131si2776578wma.139 - gsmtp

\r\n\r\nhMailServer\r\n
Every other domain is ok, only Gmail is the one I have problems with. Went further and have checked response from verifier.port25.com and here it is:

Code: Select all

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 
<verifier-feedback@port25.com>. 

Thank you for using the verifier, 

The Port25 Solutions, Inc. team 

========================================================== 
Summary of Results 
========================================================== 
SPF check: pass 
"iprev" check: pass 
DKIM check: pass 
SpamAssassin check: ham 

========================================================== 
Details: 
========================================================== 

HELO hostname: mail.fsgaz.ro 
Source IP: 81.180.119.90 
mail-from: admin@fsgaz.ro 

---------------------------------------------------------- 
SPF check details: 
---------------------------------------------------------- 
Result: pass 
ID(s) verified: smtp.mailfrom=admin@fsgaz.ro 

DNS record(s): 
fsgaz.ro. 3428 IN TXT "v=spf1 mx a ip4:81.180.119.90 ~all" 
fsgaz.ro. 3428 IN MX 10 mail.fsgaz.ro. 
mail.fsgaz.ro. 3428 IN A 81.180.119.90 


---------------------------------------------------------- 
"iprev" check details: 
---------------------------------------------------------- 
Result: pass (matches mail.fsgaz.ro) 
ID(s) verified: policy.iprev=81.180.119.90 

DNS record(s): 
90.119.180.81.in-addr.arpa. 86228 IN PTR mail.fsgaz.ro. 
mail.fsgaz.ro. 3428 IN A 81.180.119.90 


---------------------------------------------------------- 
DKIM check details: 
---------------------------------------------------------- 
Result: pass (matches From: admin@fsgaz.ro) 
ID(s) verified: header.d=fsgaz.ro 

Canonicalized Headers: 
from:admin@fsgaz.ro'0D''0A' 
subject:test'20'email'0D''0A' 
date:Fri,'20'26'20'Jan'20'2018'20'17:05:42'20'+0200'0D''0A' 
message-id:<2.669fcfb7bdb080d42a52@SERVER-FSGAZ1>'0D''0A' 
to:check-auth@verifier.port25.com'0D''0A' 
mime-version:1.0'0D''0A' 
content-type:multipart/alternative;'20'boundary="----=_NextPart_000_BEB7_9BF727CF.A5C8F89D"'0D''0A' 
dkim-signature:v=1;'20'a=rsa-sha256;'20'd=fsgaz.ro;'20's=all;'20'c=relaxed/relaxed;'20'q=dns/txt;'20'h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type;'20'bh=iBivMu5brUTAGc57gvRNAkBuHpADxyVEBwhJyMYmTDA=;'20'b= 

Canonicalized Body: 
------=_NextPart_000_BEB7_9BF727CF.A5C8F89D'0D''0A' 
Content-Type:'20'text/plain;'0D''0A' 
'20'charset="utf-8"'0D''0A' 
Content-Transfer-Encoding:'20'quoted-printable'0D''0A' 
'0D''0A' 
test'0D''0A' 
------=_NextPart_000_BEB7_9BF727CF.A5C8F89D'0D''0A' 
Content-Type:'20'text/html;'0D''0A' 
'20'charset="utf-8"'0D''0A' 
Content-Transfer-Encoding:'20'quoted-printable'0D''0A' 
'0D''0A' 
<html><body>test</body></html>'0D''0A' 
------=_NextPart_000_BEB7_9BF727CF.A5C8F89D--'0D''0A' 


DNS record(s): 
all._domainkey.fsgaz.ro. 3600 IN TXT "k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxAQDCtp78BkfBFQWkPDQUIvPoByuuR+p717EA1X8DIvWx22kBfkwgyAfP8cDcYXZ946htIFX/IHvTPset/XE2VSUX0TpMOBOSzMiksroWAB2DH1WmC04opiWG0KcKOgJFLAowWSzqnUcZvpmNYNv+6SjaY7iuYYxs63Ws/AViThganR40z8l27uoqu/onxBi0kZ7QKKNqxm557zyDU7cDLx434LlEi+ynYF752LpN2rSw/wrr5lO2T44RdbAQJMF7hy+gjP0WLQJlYKY1OQDotl+mYMx8uY3OocB2Lz+52TXXB9i8f3FNjXtkJaYG2YuD7RPug3rFufZr6z/o4x5FwIDAQAB"

Public key used for verification: all._domainkey.fsgaz.ro (2048 bits) 

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. 

---------------------------------------------------------- 
SpamAssassin check details: 
---------------------------------------------------------- 
SpamAssassin v3.4.1 (2015-04-28) 

Result: ham (-0.1 points, 5.0 required) 

pts rule name description 
---- ---------------------- -------------------------------------------------- 
0.0 NO_DNS_FOR_FROM DNS: Envelope sender has no MX or A DNS records 
-0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay 
domain 
0.0 T_SPF_TEMPERROR SPF: test of record failed (temperror) 
0.0 T_SPF_HELO_TEMPERROR SPF: test of HELO record failed (temperror) 
-0.0 BAYES_40 BODY: Bayes spam probability is 20 to 40% 
[score: 0.3255] 
0.0 HTML_MESSAGE BODY: HTML included in message 
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's 
domain 
0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid 
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 



==============================================================
Explanation of the possible results (based on RFCs 7601, 7208) 
==============================================================


DKIM Results 
============ 

none: The message was not signed. 

pass: The message was signed, the signature or signatures were 
acceptable to the ADMD, and the signature(s) passed verification 
tests. 

fail: The message was signed and the signature or signatures were 
acceptable to the ADMD, but they failed the verification test(s). 

policy: The message was signed, but some aspect of the signature or 
signatures was not acceptable to the ADMD. 

neutral: The message was signed, but the signature or signatures 
contained syntax errors or were not otherwise able to be 
processed. This result is also used for other failures not 
covered elsewhere in this list. 

temperror: The message could not be verified due to some error that 
is likely transient in nature, such as a temporary inability to 
retrieve a public key. A later attempt may produce a final 
result. 

permerror: The message could not be verified due to some error that 
is unrecoverable, such as a required header field being absent. A 
later attempt is unlikely to produce a final result. 


SPF Results 
=========== 

none: Either (a) no syntactically valid DNS domain name was extracted from 
the SMTP session that could be used as the one to be authorized, or 
(b) no SPF records were retrieved from the DNS. 

neutral: The ADMD has explicitly stated that it is not asserting whether 
the IP address is authorized. 

pass: An explicit statement that the client is authorized to inject mail 
with the given identity. 

fail: An explicit statement that the client is not authorized to use the 
domain in the given identity. 

softfail: A weak statement by the publishing ADMD that the host is probably 
not authorized. It has not published a stronger, more definitive policy 
that results in a "fail". 

temperror: The SPF verifier encountered a transient (generally DNS) error 
while performing the check. A later retry may succeed without further 
DNS operator action. 

permerror: The domain's published records could not be correctly interpreted. 
This signals an error condition that definitely requires DNS operator 
intervention to be resolved. 


"iprev" Results 
=============== 

pass: The DNS evaluation succeeded, i.e., the "reverse" and 
"forward" lookup results were returned and were in agreement. 

fail: The DNS evaluation failed. In particular, the "reverse" and 
"forward" lookups each produced results, but they were not in 
agreement, or the "forward" query completed but produced no 
result, e.g., a DNS RCODE of 3, commonly known as NXDOMAIN, or an 
RCODE of 0 (NOERROR) in a reply containing no answers, was 
returned. 

temperror: The DNS evaluation could not be completed due to some 
error that is likely transient in nature, such as a temporary DNS 
error, e.g., a DNS RCODE of 2, commonly known as SERVFAIL, or 
other error condition resulted. A later attempt may produce a 
final result. 

permerror: The DNS evaluation could not be completed because no PTR 
data are published for the connecting IP address, e.g., a DNS 
RCODE of 3, commonly known as NXDOMAIN, or an RCODE of 0 (NOERROR) 
in a reply containing no answers, was returned. This prevented 
completion of the evaluation. A later attempt is unlikely to 
produce a final result. 




========================================================== 
Original Email 
========================================================== 

Return-Path: <admin@fsgaz.ro> 
Received: from mail.fsgaz.ro (81.180.119.90) by verifier.port25.com id hdd1sk2bkd08 for <check-auth@verifier.port25.com>; Fri, 26 Jan 2018 10:05:46 -0500 (envelope-from <admin@fsgaz.ro>) 
Authentication-Results: verifier.port25.com; spf=pass smtp.mailfrom=admin@fsgaz.ro; 
iprev=pass (matches mail.fsgaz.ro) policy.iprev=81.180.119.90; 
dkim=pass (matches From: admin@fsgaz.ro) header.d=fsgaz.ro 
dkim-signature: v=1; a=rsa-sha256; d=fsgaz.ro; s=all; 
c=relaxed/relaxed; q=dns/txt; h=From:Subject:Date:Message-ID:To:MIME-Version:Content-Type; 
bh=iBivMu5brUTAGc57gvRNAkBuHpADxyVEBwhJyMYmTDA=; 
b=eZnOPePdBoqK/qL/8mYZofzvyoYdx5EgtVWq0jsRwn+7wHk3z2Duf+FT4QRHzoWEYtXIXGN7rLW22BeKAkK7NWFVQB5sgQDfulTBXTMRyRCukRah5Jzy88Nk8q77iSBvlDKpwbz9ODnSIZB+S+DZlBr5ABiGdkvjVW4vY4pkturAIStVU9LMERI1+IFxUEVS2hg9rvFsw8O0GVb+P0P5JWIH8EvQI8rTjOo0jbEm8OmrcXn+A/SRZ0ViQi
FKGLqlyXI3yUCGRP3kNZhw/Y1nZWyTPLp14sO1lNywcmAh1Xm4fl5aT6ie7S24bzYHY7GsmB/K5tMhJDublcqIU6szqA==
Received: from fsgaz.ro (SERVER-FSGAZ1 [127.0.0.1]) 
by mail.fsgaz.ro with ESMTPA 
; Fri, 26 Jan 2018 17:05:42 +0200 
MIME-Version: 1.0 
X-Mailer: MailBee.NET 6.0.2.220 
X-Priority: 3 (Normal) 
From: admin@fsgaz.ro 
To: check-auth@verifier.port25.com 
Subject: test email 
Date: Fri, 26 Jan 2018 17:05:42 +0200 
X-Originating-IP: 95.77.149.71 
Message-ID: <2.669fcfb7bdb080d42a52@SERVER-FSGAZ1> 
Content-Type: multipart/alternative; 
boundary="----=_NextPart_000_BEB7_9BF727CF.A5C8F89D" 

------=_NextPart_000_BEB7_9BF727CF.A5C8F89D 
Content-Type: text/plain; 
charset="utf-8" 
Content-Transfer-Encoding: quoted-printable 

test 
------=_NextPart_000_BEB7_9BF727CF.A5C8F89D 
Content-Type: text/html; 
charset="utf-8" 
Content-Transfer-Encoding: quoted-printable 

<html><body>test</body></html> 
------=_NextPart_000_BEB7_9BF727CF.A5C8F89D-- 
Only comprehensive answer found was here and I did follow all the steps one week ago... https://community.spiceworks.com/topic/ ... ry-2804935

Any suggestions would be appreciated.

Regards,
Adrian

User avatar
jimimaseye
Moderator
Moderator
Posts: 8175
Joined: 2011-09-08 17:48

Re: Just another "Cannot send only to Gmail" topic

Post by jimimaseye » 2018-01-26 19:22

viewtopic.php?f=21&t=29763

In short, only Gmail will tell you.
HMS 5.6.6 B2383 on Win Server 2008 R2 Foundation, + 5.6.7-B2415 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

User avatar
mattg
Moderator
Moderator
Posts: 20300
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: Just another "Cannot send only to Gmail" topic

Post by mattg » 2018-01-27 01:55

You can also authenticate your domain with gmail by adding a DNS txt record >> https://support.google.com/mail/answer/6227174
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

adrianmihai83
New user
New user
Posts: 14
Joined: 2018-01-26 17:19

Re: Just another "Cannot send only to Gmail" topic

Post by adrianmihai83 » 2018-01-27 07:12

@mattg, thanks for the tip, I forgot to mention that it is already verified since 18th of January
004E9C59-DA02-4BE5-8BDA-5F57FCBFF5CD.jpeg
@jimimaseye, first thing I did was to contact goooglevthrough this form:
https://support.google.com/mail/contact/msgdelivery
After one week I don’t have any feedback nor is my problem solved... That was when I decided to post here, I don’t know what road should I go to, of course that I can contact them again but maybe they can’t be bothered...

User avatar
jimimaseye
Moderator
Moderator
Posts: 8175
Joined: 2011-09-08 17:48

Re: Just another "Cannot send only to Gmail" topic

Post by jimimaseye » 2018-01-27 09:41

Presumably you ready the article i referred you to in full. You will have found some tips for exactly your problem with gmail.
HMS 5.6.6 B2383 on Win Server 2008 R2 Foundation, + 5.6.7-B2415 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

adrianmihai83
New user
New user
Posts: 14
Joined: 2018-01-26 17:19

Re: Just another "Cannot send only to Gmail" topic

Post by adrianmihai83 » 2018-01-27 10:41

As I said before, in the last week I researched this and went every route that there is, and YES, I did read the article in full, MORE THAN ONCE.

0. Did ask them, no answer
1. Set
2. Set
3. Ip is static
4. No blacklist
5. Read the details from the bounce message and in the link provided and the references, and I have rule for email from that adress to not go to spam and mark it as important... Cannot unmark it as spam because it is rejected, not delivered... Generic further help: ha ha ha, I can assure you that before coming here I did read first 3 pages with results on Google about my error, as many others who have this problem...
6. Another joke, don’t know what I am supposed to say...
7. The main conclusion is that if everything is ok on your side, get lost, you will not find any answers here, because there aint one, and I can understand this.

BUT, there must be an answer to this problem, and taking into considerration that I am not the only one with this problem, I can only pressume that somebody did manage to solve it in a way or another. That is why we ask here and on google forums because the two links are, well : hmailserver and google, would have post on an automobile forum but I don’t yhink that would fit the context.

Either way, thank you for your time.

User avatar
jimimaseye
Moderator
Moderator
Posts: 8175
Joined: 2011-09-08 17:48

Re: Just another "Cannot send only to Gmail" topic

Post by jimimaseye » 2018-01-27 11:16

You seem a bit defensive there. No need, the article was not directed personally to you.

Anyway, as you have read it you will have noticed it told you to read the rejection:

 
"Remote server replied: 550-5.7.1 [81.180.119.90 19] Our system has detected that this message is 550-5.7.1 likely suspicious due to the very low reputation of the sending 550-5.7.1 domain."
You were also then be told to Google the message. And that would have take you here: https://www.google.co.uk/search?q=Our+s ... 7.1+domain.

Which would have offered this as a result (as well as others): https://support.google.com/mail/forum/A ... cK0/?hl=en

Which in turn would have pointed you to this https://support.google.com/mail/answer/188131 and also, in particular, the reply to that post which is very useful.

There were also other helpful replies and search results such as https://support.google.com/a/forum/AAAA ... hiQ/?hl=en

But then you knew this already due to following the guide. Right? (I did).

A 'reputation' is a 'reputation' and you can only work to improve it.
HMS 5.6.6 B2383 on Win Server 2008 R2 Foundation, + 5.6.7-B2415 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

User avatar
mattg
Moderator
Moderator
Posts: 20300
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: Just another "Cannot send only to Gmail" topic

Post by mattg » 2018-01-27 11:31

adrianmihai83 wrote:7. The main conclusion is that if everything is ok on your side, get lost, you will not find any answers here, because there aint one, and I can understand this.

BUT, there must be an answer to this problem, and taking into considerration that I am not the only one with this problem, I can only pressume that somebody did manage to solve it in a way or another.
The ONLY way forward is to ask them why they reject you.

There is nothing that anyone else can do
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

adrianmihai83
New user
New user
Posts: 14
Joined: 2018-01-26 17:19

Re: Just another "Cannot send only to Gmail" topic

Post by adrianmihai83 » 2018-01-27 12:47

@mattg, thanks man, I understood this from the beginning, it's ok, posted here just to hear others experience... in a constructive way and I thank you for that

@jimimaseye, I know that it is not directed to me and I know that there are a lot of topics regarding this problem. That was what I said, in the last week I have searched Google for that specific error and have read all the relevant results. As a matter a fact, i was on every page you specify and have filled every form and reports there, plus taken into consideration everything written there. I don't understand your attitude with questions that want to reveal things that are not as you think you are.

And to conclude, I can only use your phrase: But then you knew that I have visited all of the links specified by you in the previous post because you already read my complete first post where in the link named by me "comprehensive answer" it describes what you just told me and from there you are directed to all the forms in your sarcastic post... Right?

Anyway, back to my real objective of this topic, that is to solve a problem. I think that I will change my IP and see how that goes, the fact is that Google is so closed in communication and in explaining how stuff works that I don't know how this reputation is taking into consideration, per IP, per domain name... If I find something relevant than I will come back here with results.

User avatar
jimimaseye
Moderator
Moderator
Posts: 8175
Joined: 2011-09-08 17:48

Re: Just another "Cannot send only to Gmail" topic

Post by jimimaseye » 2018-01-27 13:14

I have no attitude. I was stating what was written on the hope you would take it in.

The links point you to the answer that Google's rejection of your email was based on your reputation. And it tells you how they conclude this and WHEN they will stop doing so and that there is nothing you can do about this (once you have ensured you are not sending out spam or nuisance emails). Yet still you continue to look and ask for a 'holy grail' answer that doesn't exist. Consequently my conclusion was that you clearly were NOT reading everything despite you saying you had. You mention (and fail to realise exactly that you are saying it) that many others have had the same problem and searched for the answer and, like you, didn't find the answer they wanted to see. Thought: perhaps THAT answer doesn't exist.

I wrote the article because people (like you) continue to search instead of reading what they are offered (including THE answers) and as forum helpers we are constantly repeating ourselves.

Still, fair play to you, you got extra time (and repetition) out of me despite me saying I wouldn't be doing that again once i completed the article. In doing so I did no more than follow the advice.

Good luck with your search. In the interest of others like you I ask if you wouldn't mind posting the answer that solves your problem if you find it.

(P.s your Spf is worthless in preventing spoofing with the ~all 'soft fail' on the end. You might as well not have it. Suggest changing it to -all 'hard fail'.)
HMS 5.6.6 B2383 on Win Server 2008 R2 Foundation, + 5.6.7-B2415 on test.
SpamassassinForWindows 3.4.0 spamd service
AV: Clamwin + Clamd service + sanesecurity defs : https://www.hmailserver.com/forum/viewtopic.php?f=21&t=26829

adrianmihai83
New user
New user
Posts: 14
Joined: 2018-01-26 17:19

Re: Just another "Cannot send only to Gmail" topic

Post by adrianmihai83 » 2018-01-27 14:11

In my experience, going with a strict approach regarding spf record did not bring any benefit, marking as soft fail and let the receiver decide was the way to go in order to prevent some cases. I have modified it to strict right now and will see how this goes over the next week.

I am not looking for the holy grail nor for an answer to a question that has none, I was looking for user experience and cases of people that had success with this. Of course that if I get some success with this I will come back and say it, maybe reputation needs one week or one year to reset, I will come back then.

Plan is as follows:
- change spf to strict - done
- wait one week, in this time, nobody from my domain can send emails to google
- after one week, if nothing has changed... change my IP
- any other thing/s that someone may suggest...???

User avatar
mattg
Moderator
Moderator
Posts: 20300
Joined: 2007-06-14 05:12
Location: 'The Outback' Australia

Re: Just another "Cannot send only to Gmail" topic

Post by mattg » 2018-01-27 16:14

Yes

Try harder to contact gMail and ASK THEM why they reject your mail. Perhaps there are other ways other than submitting a web form
Just 'cause I link to a page and say little else doesn't mean I am not being nice.
https://www.hmailserver.com/documentation

adrianmihai83
New user
New user
Posts: 14
Joined: 2018-01-26 17:19

Re: Just another "Cannot send only to Gmail" topic

Post by adrianmihai83 » 2018-02-19 17:27

I said that I will come back, didn’t I? :)

This is just my experience with this problem, now marked as solved :)

0. Make sure that none of your accounts pasword has been breached and you are not sending spam without your will
1. Implement all of Gmail bulk email good practices and make sure that your dns settings are in perfect order and of course that you are not in any blacklist
2. Register and validate your domain with Google Postmaster - done this on 18th of January 2018
3. Check that your emails are dkim signed and key is set ok - https://port25.com/authentication-checker/
4. Check your SenderScore - https://www.senderscore.org/ also check the volume of emils sent in the past, I was not aware of the past history of this domain, changing habbit in sending emails will decrease your score
5. Check your DMARC report daily and see who is sending emails in your behalf, also make sure that all your emails from your ip are passing both spf and dkim, all others will fail (make sure that your spf includes your IP and prohibit all others, -all at the end)
6. Open a topic on google help forums (uselss, will just give you crap recomandations, here is mine - https://productforums.google.com/forum/ ... hYVBhQ7y5Y )
7. Send as many reports to Google, don’t think that this helped me but... who knows, google will not give you any feedback... but this will keep youngoing :) https://support.google.com/mail/contact/msgdelivery
8. Last thing and this is the important part... WAIT 30 DAYS AND MAKE SURE THAT YOUR DOMAIN IS IN GOOD HEALTH AND YOU ARE NOT SENDING SPAM. MONITOR YOUR SERVER, I have 320 email addreses, more than 620.000 emails and 250 GB of data, things can get out of order very quickly, people do not understand that having an email like abc@domain.com and using the password abcdomaincom is not a good ideea :)

Here I am after one month and everything is ok. My feeling is that what helped the most is the 30 days of continuous monitoring and keeping things in order.

Many things could have been said here because I did try all of them, these are the ones that I think mattered.

Now that you can send to Gmail, check google postmaster and see how you are doing.

Post Reply