[SOLVED]How-Come? X-ME-Content: Deliver-To=Junk but email was still delivered to \Inbox

Raise/discuss any potential issues with MailEnable for consideration in project issue register.
Post Reply
poweredge
Posts: 99
Joined: Sat May 29, 2021 11:16 am

[SOLVED]How-Come? X-ME-Content: Deliver-To=Junk but email was still delivered to \Inbox

Post by poweredge » Mon Jun 14, 2021 11:52 am

===============
Original Email
Message ID: 3893CC02E0724E78914F9B66E776598F.MAI
X-RBL-Result: Generic, Fail
X-ME-Content: Deliver-To=Junk
X-ME-Bayesian: 40.000000

===============

Received: from hotmail.com ([223.199.16.250]) by gateway.domain.com with
MailEnable ESMTP; Mon, 14 Jun 2021 11:10:44 +0800
From: ldkxjtrxfc@hotmail.com
Subject: Bitcoin
To: info@domain.com
Content-Type: text/plain;charset="GB2312"
Content-Transfer-Encoding: 8bit
Date: Mon, 14 Jun 2021 11:10:41 +0800
X-Priority: 3
X-Mailer: FoxMail 3.11 Release [cn]
Message-ID: <3893CC02E0724E78914F9B66E776598F.MAI@gateway.domain.com>
X-Envelope-Sender: ldkxjtrxfc@hotmail.com
X-RBL-Result: Generic, Fail
X-ME-Content: Deliver-To=Junk
X-ME-Bayesian: 40.000000
Return-Path: <ldkxjtrxfc@hotmail.com>



===============
Mail Trace Ultility
Message ID: 82EA4FCB4081430F831617700265CA4E.MAI
===============

Trace: Tracing message with Message ID [3893CC02E0724E78914F9B66E776598F.MAI] from the SMTP Inbound Queue

Status: Message ID [3893CC02E0724E78914F9B66E776598F.MAI] was routed by the MTA from the SMTP Inbound Queue to 1 destination queue(s)

06/14/21 11:10:45 Queue Route: Message ID [3893CC02E0724E78914F9B66E776598F.MAI] was routed by the MTA from the SMTP Inbound Queue to the Postoffice Connector (SF) Outbound Queue with a Message ID of [82EA4FCB4081430F831617700265CA4E.MAI]

06/14/21 11:10:46 [82EA4FCB4081430F831617700265CA4E.MAI] Delivered message from [SMTP:ldkxjtrxfc@hotmail.com] to PO=domain.com MBX=info FLD=\Inbox


===============
RBL Detected and Mark as Spam in header
X-ME-Content: Deliver-To=Junk
===============

SMTP-Debug-210614.log
06/14/21 11:10:44 ME-E0113: [1916] Message marked as spam: (223.199.16.250) was found in DNSBL Barracuda Reputation Block List.
06/14/21 11:10:44 ME-I0149: [1916] 3893CC02E0724E78914F9B66E776598F.MAI was received successfully and delivery thread was initiated


===============
Why doesn't MTA delivery it to PO's Junk?
===============

Post Office Debug
06/14/21 11:10:46 # [82EA4FCB4081430F831617700265CA4E.MAI] Delivered message from [SMTP:ldkxjtrxfc@hotmail.com] to PO=domain.com MBX=info FLD=\Inbox

* Postoffice level features already set "Delivery Junk to Junk E-Mail Folder"

How come it can bypass X-ME-Content: Deliver-To=Junk? Instead delivers to \Junk, it went straight to \Inbox instead?

Could this be a bug in v10.34 I wonder?

****************or Could it be this line explained the whole scenario why it went to \Inbox?)
X-ME-Bayesian: 40.000000

I understand it's the Overall Spam Score, anything below 40 means it's a Low suspected spam (correct me if I am wrong)
Low 40
Medium 60
High 80

Does it mean the probability of this email being spam is Low, so even it's RBL blacklisted, the email is still treated as non-spam, hence >\Inbox?
I thought failing the RBL alone is already enough to tag X-ME-Content: Deliver-To=Junk and send the email to \Junk ? No?

If it's the case, shall I decrease the number to Low 20 Medium 40 and High 60

Thanks
Last edited by poweredge on Thu Jun 17, 2021 4:38 am, edited 1 time in total.

MailEnable-Ian
Site Admin
Posts: 9483
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: How-Come? X-ME-Content: Deliver-To=Junk but email was still delivered to \Inbox

Post by MailEnable-Ian » Tue Jun 15, 2021 3:20 am

Hi,

If the RBL filter added X-ME-Content: Deliver-To=Junk header then it should have been delivered to the junk email folder for that mailbox. There is an issue in the current release where the setting for "Deliver Junk email to Junk email folder" reports as being by enabled by default but its not really enabled. To fix the problem you need to untick the option hit apply and then tick it again and hit apply so the value is written to the postoffice.sys file. This problem is addressed on the beta kit on our beta page.
Regards,

Ian Margarone
MailEnable Support

Post Reply