Domain emails flaged as spam by google mail

[Issam]

Dear Experts,

We own a domain www.seha.ma and using the emails from yandex. Our domain is delegated to Cloudflare. However, google mail flag each email from us (xx.xx@seha.ma) as spam, although we are not. We tried to contact google but without any answer. Such a. Desperate situation, because our platform is a medical teleconsultation and patient start to miss appointments.

Any help is appreciated.

Best,

Dr. Issame Outaleb

[StephenHind]

@Issam a quick check using the Google Admin Toolbox - MX Check gives you various steps you should take, so that's the first thing to do:

https://toolbox.googleapps.com/apps/checkmx/check?domain=seha.ma&dkim_selector=

[BoI_Admin]

@Issam I was about to recommend the exact same thing as @StephenHind 👌

[Issam]

Thx @StephenHind and @Bol_Admin . Our domain is in Yandex and not in google. So why SpF should allow Google server tobsend email on our behalf? Yandey does. Help me to understand pls. We only want google mail to de-spam our emails. Thx for your help in advance.

[Issam]

Thx @StephenHind and @bol_admin. Our domain is in Yandex and not in google. So why SpF should allow Google server tobsend email on our behalf? Yandey does. Help me to understand pls. We only want google mail to de-spam our emails. Thx for your help in advance. 

[StephenHind]

@Issam The tool I used is a Google Workspace tool and you've posted to the Google Workspace Discussion so I naturally assumed that you're using Google Workspace.  If you're not using Google Workspace you probably want to look to asking in a different discussion group.

If you're not using Google Workspace in any way (i.e. not for Google Docs or Drive) then you probably don't need to set the SPF to all Google Workspace to send on your behalf. The rest of the advice is all useful though, e.g. DKIM is not set up so do that following your service provider's instructions.

My guess is you need to ask these questions with your service provider, not in the Google Workspace Discussion since you're not using Google Workspace.

[Issam]

@StephenHind i got the answer from Yandex admins "

According to the text of the non-delivery report, the recipient's mail server identified your email as spam and refused to accept it.

This means that the message is rejected not because of the fact that it was sent from Yandex.Mail, but because of the recipient's spam filters. Unfortunately, it is impossible to resolve this situation from our side.". I also wanted to use google for our business emails and domain, then decided to drop it due to high prices for us as a startup. Buz why google is considering our emails as spam is weired. Hmm? 

[tad_hawkins1]

Reiterating what @StephenHind just said about reaching out to your source email provider. You can look at the email in questions header as well, it should give you some idea as to why these are being marked as spam.

[Issam]

According to the text of the non-delivery report, the recipient's mail server identified your email as spam and refused to accept it.

This means that the message is rejected not because of the fact that it was sent from Yandex.Mail, but because of the recipient's spam filters. Unfortunately, it is impossible to resolve this situation from our side. This was the answer from Yandex, our provider 

[tad_hawkins1]

Check the headers of the message marked as spam

[Issam]

Delivered-To: 'PII removed by Staff'
Received: by 2002:a54:2249:0:0:0:0:0 with SMTP id f9csp1454015eco;
        Wed, 9 Feb 2022 05:47:28 -0800 (PST)
X-Google-Smtp-Source: ABdhPJxLPr9El+nIeiJa2eTlxkwucqkR0ejSFHf7Z2VUK0NO73SZbcBvtAGco0eQQeniy8uJUh58
X-Received: by 2002:a05:6512:1506:: with SMTP id bq6mr1630756lfb.561.1644414448465;
        Wed, 09 Feb 2022 05:47:28 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1644414448; cv=none;
        d=google.com; s=arc-20160816;
        b=07O9mny/Tx4/3N8TiB2Ts3CYweBpwo/jldv6T/iAsY09Qsc3wjGTlRFD+sJAa0rhey
         H+rkmafFBFbx9WSnabpO93aH+NXhUqGTo3idjQ+5tlMTJ0s1/cpqJ1JIxkr7J1eRaQsS
         gh2WOpG1rSLPi3TEums/laKv9iSBeK8QfvVvcSkfDl8gJTPUBkV2UAXs3GCOi19B5rlt
         itTvAGxTQHYEeufTx3y3wFBDvYNCA4YnD4Ynm9s/kdkA8tWKPvnJIUXA0Cw/KTnGaeMC
         6nHgH9iOO5f2EZopGKfZOyU3T3SneiWQayhi1VCx+XGwSHXsWGnpUj/q3ByTQVoGVYe8
         1jEQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=content-transfer-encoding:message-id:date:mime-version:subject:to
         :from:dkim-signature;
        bh=081Y/p/koWMw7Wnoelrx+b8lDBvX8I9wo9kxUIpdOt4=;
        b=v0HsFHSOsvprcSCfsi4cGKQ1gNIzCKMWAD+DV4bafBrO5EaQyBYC5OoIPp9tNjYr1c
         Ntxdo/To0ioMgpUWx7ozmJA43ZtRimHG9AW8YDkFn+QtZKeyeJxLIqY/0mNoM2zxNBAd
         axKVZc8jqWEkEnDP/eOhFlwIikOb9XLd6RvE1rlY3X8kC6MamBvmI5DoM2sdyR5jK0Jc
         V6GHwYhIMMWHWqWi0XRCIpcwM+KHZN90eSAx9xOHpYbTkz1weu+XZb2oBimvdXcZbQkt
         996nAo4wqLkbj+M1iazLHP936dtATls9Rg6LHiARfVxn7KJqBktKvim0enSc1xOvHyV6
         wF1A==
ARC-Authentication-Results: i=1; mx.google.com;
       dkim=pass header.i=@seha.ma header.s=mail header.b=DdbNIMbv;
       spf=pass (google.com: domain of i.outaleb@seha.ma designates 2a02:6b8:0:801:2::106 as permitted sender) smtp.mailfrom=i.outaleb@seha.ma;
       dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=seha.ma
Return-Path: <i.outaleb@seha.ma>
Received: from forward103j.mail.yandex.net (forward103j.mail.yandex.net. [2a02:6b8:0:801:2::106])
        by mx.google.com with ESMTPS id a17si12430073ljm.62.2022.02.09.05.47.28
        for <outaleb.consulting@gmail.com>
        (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);
        Wed, 09 Feb 2022 05:47:28 -0800 (PST)
Received-SPF: pass (google.com: domain of i.outaleb@seha.ma designates 2a02:6b8:0:801:2::106 as permitted sender) client-ip=2a02:6b8:0:801:2::106;
Authentication-Results: mx.google.com;
       dkim=pass header.i=@seha.ma header.s=mail header.b=DdbNIMbv;
       spf=pass (google.com: domain of i.outaleb@seha.ma designates 2a02:6b8:0:801:2::106 as permitted sender) smtp.mailfrom=i.outaleb@seha.ma;
       dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=seha.ma
Received: from myt6-fd890da583f9.qloud-c.yandex.net (myt6-fd890da583f9.qloud-c.yandex.net [IPv6:2a02:6b8:c12:1d80:0:640:fd89:da5]) by forward103j.mail.yandex.net (Yandex) with ESMTP id EB3F71011DD for <outaleb.consulting@gmail.com>; Wed,
  9 Feb 2022 16:47:27 +0300 (MSK)
Received: from 2a02:6b8:c12:149c:0:640:7dfd:652 (2a02:6b8:c12:149c:0:640:7dfd:652 [2a02:6b8:c12:149c:0:640:7dfd:652]) by myt6-fd890da583f9.qloud-c.yandex.net (mxback/Yandex) with HTTP id RlZftf0ci0U1-lRcOaH9b; Wed, 09 Feb 2022 16:47:27 +0300
X-Yandex-Fwd: 1
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=seha.ma; s=mail; t=1644414447; bh=081Y/p/koWMw7Wnoelrx+b8lDBvX8I9wo9kxUIpdOt4=; h=Message-Id:Date:Subject:To:From; b=DdbNIMbvkI6x8lX/L+2A5s3KuqtVgltLxUGqOZ7T9xTbf7x+D0G0JBrnMp8LgUXXZ
	 MAbbh6+xnSXzb7ruloI1HdegY2Y/gzv2Iih5qkJlmJksy7wQamxer3+5Z4tTLbZy4c
	 ki51IBlH9pjKEpKjHeehpJAh9TvP9zytWf5KPrI0=
Authentication-Results: myt6-fd890da583f9.qloud-c.yandex.net; dkim=pass header.i=@seha.ma
Received: by myt5-7dfd06528d3d.qloud-c.yandex.net with HTTP; Wed, 09 Feb 2022 16:47:27 +0300
From: Issame outaleb <i.outaleb@seha.ma>
To: outaleb.consulting@gmail.com
Subject: Test
MIME-Version: 1.0
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Wed, 09 Feb 2022 14:47:27 +0100
Message-Id: <5599351644414447@myt5-7dfd06528d3d.qloud-c.yandex.net>
Content-Transfer-Encoding: 8bit
Content-Type: text/html; charset=utf-8

Ok dok test <br /><br />-- <br />Sent from Yandex.Mail for mobile

[Issam]

@tad_hawkins1 see above the original message.

[tad_hawkins1]

Sorry, I cannot help you, if you won't help yourself

[Issam]

@tad_hawkins1 i tried to post it 4 times, each time its gone. no sign of any spam or so. can i send it per email to check

[Issam]

hi @tad_hawkins1 any response or feedback on the screen shot.?

[Issam]

@StephenHind can you give it a try pls . see above the original message. if possible. i dont see any spam issue in the header. and thx for your help really.

[tad_hawkins1]

My thought was to suggest looking through the mail logs but now I see you do not have a Google domain, but rather a consumer Gmail account. Had this been a Google Workspace domain, you could have written rules to accept to bypass spam for this sender.  Your only recourse may be to go into the spam folder and mark the message as not spam.

[Issam]

Appreciate. Seha.ma has been a workspace domain indeed but only for the 14 days trial. We deleted it actually. I think this is causing the problem for sure.

My main concern is our users when they get emails from us. I can bypass set petnfolter rules, but the patients wont understand it.

And taughts? 

[Issam]

@tad_hawkins1 i answered 🙂