Avoiding Spam Filter in Gmail Cloudflare Webmail Integration

Hello,

I have successfully integrated emails routing through Cloudflare with my personal Gmail account.
There is no problem with sending and receiving my custom domain email through my personal gmail.

However, I am not able to send emails without avoiding spam filter.

When I look into incoming email header, I can see that, this email is sent by [email protected]. Probably that is why, spam filter is triggered.

What kind of DNS record should I use to prevent this? Can you guys help me to get over this?

Here is the example mail header:

Tes
This message was identified as junk. We'll delete it after 30 days. It's not junk
Retention: Junk Email (30 days) Expires: Fri 9/9/2022 7:31 PM
This message was identified as junk. We'll delete it after 30 days. Retention: Junk Email (30 days) Expires: Fri 9/9/2022 7:31 PM
CustomWebmail <[email protected]>

Received: from qweqweqwe.eurprd07.prod.outlook.com (::1) by
 qweqwewqe.eurprd07.prod.outlook.com with HTTPS; Wed, 10 Aug 2022 16:31:16
 +0000
Received: from qweqweqwe.eurprd03.prod.outlook.com (2603:10a6:4:3e::17)
 by wqeqwewqe.eurprd07.prod.outlook.com (2603:10a6:208:24::33) with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 125.20.125.29; Wed, 10 Aug
 2022 16:31:14 +0000
Received: from qweqweqweq.eop-EUR01.prod.protection.outlook.com
 (2603:10a6:4:3e:cafe::9f) by qweqweqwe.outlook.office365.com
 (2603:10a6:4:3e::17) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 125.20.125.121 via Frontend
 Transport; Wed, 10 Aug 2022 16:31:14 +0000
Authentication-Results: spf=pass (sender IP is 209.85.219.166)
 smtp.mailfrom=gmail.com; dkim=none (message not signed)
 header.d=none;dmarc=none action=none
 header.from= customwebmail.com;compauth=fail reason=001
Received-SPF: Pass (protection.outlook.com: domain of gmail.com designates
 209.185.219.166 as permitted sender) receiver=protection.outlook.com;
 client-ip=209.185.219.166; helo=mail-qv1-f66.google.com; pr=C
Received: from mail-qv1-f66.google.com (209.185.219.166) by
 qweqwewqewq.mail.protection.outlook.com (110.152.25.122) with Microsoft SMTP
 Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 115.201.125.11 via Frontend Transport; Wed, 10 Aug 2022 16:31:13 +0000
Received: by mail-qv1-f66.google.com with SMTP id l18so11337624qvt.13
        for <[email protected]>; Wed, 10 Aug 2022 09:31:13 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20210112;
        h=to:subject:message-id:date:from:mime-version:x-gm-message-state
         :from:to:cc;
       		S73kQ/+ADYojcRS57G+urFG8fBZFbq38OsNsw0r12qUFd
         cAD1NyhVZCR7papTJMFnyITYnu1Zf33AQozNPDREvYRhbzlZY20rhS6azVQ7tEBqKXTn
         LIyFNpYdGNeziSPnsdQTSonCsmRGUUpUsofGLlUbubokCtEQC8TluquIEf7hAzAf37O1
         lc+g==
X-Gm-Message-State: ACgBeokg7oS6QxfTiP12h7Q=
X-Google-Smtp-Source: AA6agR4H/cFHWkFU59BVEnKqD4oZR/NTb1TaWrst1NVWlrxqzVXV+uS0yj3LFA==
X-Received: by 2002:a0c:a99d:0:b0:474:7389:858b with SMTP id a29-20020a0ca99d000000b004747389858bmr24857242qvb.100.1660149072772;
        Wed, 10 Aug 2022 09:31:12 -0700 (PDT)
Return-Path: [email protected]
Received: from mail-yb1-f169.google.com (mail-yb1-f169.google.com. [209.185.219.169])
        by smtp.gmail.com with ESMTPSA id d10-adsdasdas.80.2022.08.10.09.31.12
        for <[email protected]>
        (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128);
        Wed, 10 Aug 2022 09:31:12 -0700 (PDT)
Received: by mail-yb1-f169.google.com with SMTP id sdasda.8
        for <[email protected]>; Wed, 10 Aug 2022 09:31:12 -0700 (PDT)
X-Received: by 2002:a25:d80a:0:b0:67c:25d3:f1f4 with SMTP id
 p10-adsdsa.78.1660149072366; Wed, 10
 Aug 2022 09:31:12 -0700 (PDT)
MIME-Version: 1.0
From: CustomWebmail <[email protected]>
Date: Wed, 10 Aug 2022 19:31:01 +0300
X-Gmail-Original-Message-ID: <[email protected]>
Message-ID: <[email protected]>
Subject: Tes
To: [email protected]
Content-Type: multipart/alternative; boundary="dasdasasddas"
X-MS-Exchange-Organization-ExpirationStartTime: 10 Aug 2022 16:31:13.8274
 (UTC)
X-MS-Exchange-Organization-ExpirationStartTimeReason: OriginalSubmit
X-MS-Exchange-Organization-ExpirationInterval: 1:00:00:00.0000000
X-MS-Exchange-Organization-ExpirationIntervalReason: OriginalSubmit
X-MS-Exchange-Organization-Network-Message-Id:
dasdasdasX-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 92dd429a-dasadsda-438b-94d4-481f20a06fc5:0
X-MS-Exchange-Organization-MessageDirectionality: Incoming
X-MS-PublicTrafficType: Email
X-MS-Exchange-Organization-AuthSource:
 dsadsadsa.eop-EUR01.prod.protection.outlook.com
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Office365-Filtering-Correlation-Id: dasdsaasd-dab7-4692-df59-08da7aedbde7
X-MS-TrafficTypeDiagnostic: dasdsadsa:EE_
X-MS-Exchange-AtpMessageProperties: SA|SL
X-MS-Exchange-Organization-SCL: 5
X-Forefront-Antispam-Report:
 CIP:209.185.219.66;CTRY:US;LANG:en;SCL:5;SRV:;IPV:NLI;SFV:SPM;H:mail-qv1-f66.google.com;PTR:mail-qv1-f66.google.com;CAT:SPOOF;SFS:(13230016)(4636009)(564344004)(83170400001)(356005)(7596003)(5660300002)(7636003)(3480700007)(55446002)(1096003)(58800400005)(8676002)(6666004)(22186003)(7116003)(33964004)(6916009)(26005)(336012)(9686003)(42186006)(42882007);DIR:INB;
X-Microsoft-Antispam: BCL:0;
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Aug 2022 16:31:13.7805
 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: adsdsa-dab7-dasdsa-df59-08da7aedbde7
X-MS-Exchange-CrossTenant-Id: dasasd-2afb-438b-94d4-adsdsa
X-MS-Exchange-CrossTenant-AuthSource:
 asddas.eop-EUR01.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-Transport-CrossTenantHeadersStamped: asdasd
X-MS-Exchange-Transport-EndToEndLatency: 00:00:02.3121541
X-MS-Exchange-Processed-By-BccFoldering: 15.20.5525.008
X-Microsoft-Antispam-Mailbox-Delivery:
	ucf:0;jmr:0;auth:0;dest:J;OFR:SpamFilterAuthJ;ENG:(910001)(944506458)(944626604)(920097)(930097)(3100021);RF:JunkEmail;
X-Microsoft-Antispam-Message-Info:
	=?us-ascii?Q?dsadsaadss+6I?=
 =?us-ascii?Q?qZvOXwr8ebU0+saddsadsadsadsa/O+tLytfJ7u2AArGu?=
 =?us-ascii?Q?dasdsaasd/u3U+chlYyl56sqi+gI5F5N/?=

Hi there, a few checks you may conduct. Firstly, cross check the configured dns records on the Cloudflare. Read this: Postmaster · Cloudflare Email Routing docs

Check all the records exist properly. Read this as well: https://www.cloudflare.com/learning/email-security/how-to-identify-a-phishing-email/

1 Like

Thank you for paying attention and suggestion. I think, I found the solution.

Authorizing Gmail as a sender wasn’t enough. I found Sendinblue for SMTP relay, which provides DKIM and DMARC check also. After signing in to Gmail with Sendinblue SMTP, the spam problem has gone.

I followed this video.
Youtube watch?v=nNGcvz1Sc_8

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.