Hi all,
I was sure this would have come up somewhere but i can't make a search
produce any results. This also tells me that it's most likely my error
if no-one else has the problem
Mails to "AdminCC" are sent as a BCC, but there is no To: or CC: fields,
so spam filtering marks all the mails as spam.
1.2 MISSING_HEADERS Missing To: header
1.9 REPLYTO_WITHOUT_TO_CC REPLYTO_WITHOUT_TO_CC
I have made a workaround solution by putting a To: header in the admincc
template that sends the mail to a /dev/null mailbox, but that's hardly ideal.
Below are the full headers of the mail
thanks in advance for any suggestions
Woody.
Return-Path: <[email protected]>
Received: from deliver ([unix socket])
by math.xxx.net (Cyrus v2.3.16-Fedora-RPM-2.3.16-13.el6_6) with LMTPA;
Mon, 07 Dec 2015 08:30:55 +0000
X-Sieve: CMU Sieve 2.3
Received: from bodge.xxx.org ([xxx.xxx.xxx.xx])
by math.xxx.net with esmtp (Exim 4.72)
(envelope-from <[email protected]>)
id 1a5rCA-0001wG-7Q; Mon, 07 Dec 2015 08:30:55 +0000
Received: from www-data by bodge.x.org with local (Exim 4.82)
(envelope-from <[email protected]>)
id 1a5rC4-0001D1-VW; Mon, 07 Dec 2015 08:30:49 +0000
Subject: Re: Fw: WTGxxxx Jeep Cherokee 2006
From: [email protected]
Reply-To: [email protected]
In-Reply-To:
<of58896a89.e13aa1e4-on43257f14.002e92ba-43257f14.002eb...@unvienna.org>
References: <[email protected]> <RT-Ticket-82786@Wild
Things Safaris> <rt-4.2.9-3596-1449475587-1262.82786-7-0@Wild Things
Safaris> <[email protected]>
<[email protected]>
<of58896a89.e13aa1e4-on43257f14.002e92ba-43257f14.002eb...@unvienna.org>
Message-ID: <[email protected]>
X-RT-Loop-Prevention: WT
X-RT-Ticket: WT #82786
X-Managed-BY: RT 4.2.9 (http://www.bestpractical.com/rt/)
X-RT-Originator: [email protected]
Content-Type: multipart/mixed; boundary="----------=_1449477048-4190-15"
Precedence: bulk
Date: Mon, 07 Dec 2015 11:30:48 +0300
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-Spam-Score: 2.5 (++)
X-Spam-Report: Spam detection software, running on the system "math.xxx.net",
has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: Ticket URL: http://rt.xxx.com/Ticket/Display.html?id=82786
Hi Woody, No idea whether it has been skimmed before. The previous owner
is not contactable, so I cannot check with him. He had it from new, and I'm
not aware of any earlier problems. [...]
Content analysis details: (2.5 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
-0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low
trust
[xx.xx.xx.xx listed in list.dnswl.org]
-0.0 SPF_PASS SPF: sender matches SPF record
1.2 MISSING_HEADERS Missing To: header
0.0 TVD_FW_GRAPHIC_NAME_MID BODY: Medium sized image attachment name
0.0 HTML_MESSAGE BODY: HTML included in message
1.9 REPLYTO_WITHOUT_TO_CC REPLYTO_WITHOUT_TO_CC
This is a multi-part message in MIME format...
------------=_1449477048-4190-15
Content-Type: multipart/alternative; boundary="----------=_1449477048-4190-14"
This is a multi-part message in MIME format...
------------=_1449477048-4190-14
RT-Attach-Message: yes
Content-Type: text/plain; charset="utf-8"
X-RT-Original-Encoding: utf-8
Ticket URL: http://rt.xxx.com/Ticket/Display.html?id=82786
Hi Woody,
Regards,
