B
B
boodda2012-10-17 11:40:07
gmail
boodda, 2012-10-17 11:40:07

Gmail accepts emails as spam

For a long time there is a dedicated server, on one of the sites there was a need to send mail.
Postfix + opendkim was installed in the ISP manager, a mailbox was created, the settings were checked, letters are signed with a dkim key, a public key was added to the TXT record of the domain, but when trying to send test letters to different mailboxes from different mail services, mail.ru, yandex .ru accepted mail as it should be in the "inbox", but gmail sent letters to sms.

here is the email in Gmail.

Delivered To: [email protected]
Received: by 10.194.13.66 with SMTP id f2csp96681wjc;
        Fri, 5 Oct 2012 03:14:10 -0700 (PDT)
Received: by 10.216.201.198 with SMTP id b48mr637927weo.126.1349432050881;
        Fri, 05 Oct 2012 03:14:10 -0700 (PDT)
Return-Path: <[email protected]*****.com>
Received: from mail.ama*****.com ([XX.228.XX.177])
        by mx.google.com with ESMTPS id k29si11302736weo.59.2012.10.05.03.14.10
        (version=TLSv1/SSLv3 cipher=OTHER);
        Fri, 05 Oct 2012 03:14:10 -0700 (PDT)
Received-SPF: neutral (google.com: XX.228.XX.177 is neither permitted nor denied by best guess record for domain of [email protected]*****.com) client-ip=XX.228. XX.177;
Authentication-Results: mx.google.com; spf=neutral (google.com: XX.228.XX.177 is neither permitted nor denied by best guess record for domain of [email protected]*****.com) [email protected]* ****.com; dkim=pass header.i= ama *****.com
Received: by mail.ama*****.com (Postfix, from userid 0)
	id E25E28D803B; Fri, 5 Oct 2012 10:05:19 +0200 (CEST)
X-DKIM: OpenDKIM Filter v2.6.7 mail.ama*****.com E25E28D803B
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ama*****.com;
	s=mail; t=1349424319;
	bh=tPD4ev0rwuvtSENhg+zLSQOMy1aGdz8WUUj63Qd60nY=;
	h=To:Subject:Date:From;
	b=VRw2is8zeAfgGjnE/+bEA24YRXPLKOvmBK/lfm8kNFS59o9Xged8a1H00Ji3XWovm
	 IbHTEPiBiiCtodmV1NbalW2SWWU0ux40T0eWz8EzWUypQKxYwszieWtqwyo8QYDxuk
	 QmJ+PEQv8Ev1NhH5eZLsoJEUCVqeE39NTPadIs6E=
To: [email protected]
Subject: Hello from the server
Message-Id: <[email protected]*****.com>
From: [email protected]*****.com (root)

Test letter

Answer the question

In order to leave comments, you need to log in

9 answer(s)
S
Sergey, 2012-10-17
@bondbig

SPF did not, judging by the headlines.

P
Puma Thailand, 2012-10-17
@opium

ptr record is also not configured, hire an admin who handles mail, he will look at your letters and they will fall where they need to, it makes sense to configure them if spf and prt are not there.

L
la0, 2012-10-17
@la0

Most likely the problem is the lack of reverse DNS for IP. As mentioned above, this is a PTR record.
Regarding it - to the host.

I
Inori, 2012-10-17
@Inori

Authentication-Results: mx.google.com; spf=neutral (google.com: XX.228.XX.177 is neither permitted nor denied

But it’s not at all a fact that it will help, I had both SPF and DKIM done and it still went to spam.
After much torment, I had to resort to an external SMTP server

B
boodda, 2012-10-17
@boodda

here, as it were, initially there was an attempt to configure the sending of letters from the gmail account. But it was the same there, everything went to spam, and simple test letters with registration codes. Therefore, we decided to raise the mail service on the server. IP no spam databases checked.

S
s0L, 2012-10-17
@s0L

I also encountered this at one time, it was decided only by experiments with the wording of the subject and text of the letter.

B
boodda, 2012-10-17
@boodda

Help setting up SPF...

V
Vladimir Dubrovin, 2012-10-17
@z3apa3a

Check the letter for compliance with standards. For example, in the Subject field you have eight-bit characters, which is a violation of the standards, encode them, From: not only violates the standards, but also has a form that is not found in real letters. Make sure that the mail.ama*****.com domain has an MX record (most likely you have a host address there instead of a domain name) - or use the correct address in an existing domain for From: and MAIL FROM:.

B
boodda, 2012-10-18
@boodda

thanks to everyone, I see a lot of problems, besides, if I understand correctly, the SPF record does not point to mail.ama*****.com, but simply to ama****.com, and all other MX records and others with them point to him. but the newsletter comes from mail.ama*****.com

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question