You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by Nicolás <ni...@devels.es> on 2014/08/20 16:24:03 UTC
Help determining what is causing mails being marked as Spam
Hi all,
I know this is not necessarily related to SpamAssasin itself, but I'm
having a hard time trying to make my sent mails (from an own domain) not
being marked as Spam on Gmail, so I was wondering if someone of you
could have a look at the headers below and find out a reason why is my
mail categorically marked as spam?
I must mention that I have never done bulk sends (not even now, I'm
refering to one-to-one mails), never an account has been compromised on
this domain, obviously I have never sent spam, so I just don't
understand why is it all marked as spam.
The only one tip I have right now is that the reverse DNS query of the
server's resolves to a different host than the one sent in EHLO, but in
that case I don't know how to avoid that since the hosting where the
dedicated server is located automatically assigns their own host to each
IP. Could this have something to do with it?
The IP is: 92.222.24.114
The mail server is: mail.devels.es
The reverse DNS assigned by the hosting to that IP is: 114.ip-92-222-24.eu
Below I'm including the headers, I'd be very grateful for any help to
find out why is every mail marked as spam since I've already run of
ideas... Thanks!
Delivered-To: agmailaccount@gmail.com
Received: by 10.64.231.7 with SMTP id tc7csp124091iec;
Wed, 20 Aug 2014 06:26:33 -0700 (PDT)
X-Received: by 10.60.67.34 with SMTP id k2mr38266595oet.52.1408541193378;
Wed, 20 Aug 2014 06:26:33 -0700 (PDT)
Return-Path: <se...@devels.es>
Received: from mail.devels.es (114.ip-92-222-24.eu. [92.222.24.114])
by mx.google.com with ESMTPS id
y11si29607456oep.28.2014.08.20.06.26.32
for <ag...@gmail.com>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256
bits=128/128);
Wed, 20 Aug 2014 06:26:33 -0700 (PDT)
Received-SPF: pass (google.com: domain of services@devels.es
designates 92.222.24.114 as permitted sender) client-ip=92.222.24.114;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of services@devels.es designates
92.222.24.114 as permitted sender) smtp.mail=services@devels.es;
dkim=pass (test mode) header.i=@devels.es
Received: by mail.devels.es (Postfix, from userid 111)
id D99F41202940; Wed, 20 Aug 2014 14:26:31 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=devels.es;
s=mail;
t=1408541191; bh=ykRtuaP0t7bumAv86BRHpkisY8xRTGEWixUOr2eU/RM=;
h=From:To:Subject:Date:From;
b=EjcZcnd8RjwwfAi/sP98ArGfQrm9ls3MN6jafEi44KFqTvgc0qzd3sEA4BX7vFeY2
b/mYt63balL89g+uGntuI1ZMnbaiwG6DprilQ4mHube8VsjOkte3fOwpt9gmu8K2jf
nFc2jixDolFsR1OxQ/c6zxme6usOZoZW6m149MAM=
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
vps81276.ovh.net
X-Spam-Level:
X-Spam-Status: No, score=0.5 required=3.0 tests=ALL_TRUSTED,MISSING_DATE,
MISSING_MID,T_DKIM_INVALID autolearn=no autolearn_force=no
version=3.4.0
Received: from rpi.devels.es (unknown [77.231.204.119])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
(Authenticated sender: services@devels.es)
by mail.devels.es (Postfix) with ESMTPSA id E4011120291F
for <ag...@gmail.com>; Wed, 20 Aug 2014 14:26:30 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=devels.es;
s=mail;
t=1408541191; bh=ykRtuaP0t7bumAv86BRHpkisY8xRTGEWixUOr2eU/RM=;
h=From:To:Subject:From;
b=ftYApmVO4tNY0pXbs+dCPmYhmYG3C/FYPl/hSUQWAmQ06zYO3SNptS/mpvAGRaiYg
YCKekKipmoS3jNnMujyZltOYQRXfc7XkuO5NUuv0IbJN3h41rhpaiETl8frhEc2yOz
IXFw6/z0KC69xDPwJva5or//SAmCR+XsduMa0yKE=
From: Test account <se...@devels.es>
To: test55 <ag...@gmail.com>
Subject: This is a test
MIME-Version: 1.0
Content-type: text/plain; charset=UTF-8
Message-Id: <20...@mail.devels.es>
Date: Wed, 20 Aug 2014 14:26:31 +0100 (BST)
This is a test
Re: Help determining what is causing mails being marked as Spam
Posted by Axb <ax...@gmail.com>.
On 08/21/2014 12:11 PM, Nicolás wrote:
> El 21/08/2014 11:07, Matus UHLAR - fantomas escribió:
>>>> On Wed, 20 Aug 2014, Nicolás wrote:
>>>>> Ok, already done that, waited a few hours and now the 'correct' DNS
>>>>> host appears in the header, but is still marked as spam.
>>
>> On 20.08.14 20:14, Nicolás wrote:
>>> This would be the latest test:
>>
>>> X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
>>> vps81276.ovh.net
>>> X-Spam-Level:
>>> X-Spam-Status: No, score=0.5 required=3.0
>>> tests=ALL_TRUSTED,MISSING_DATE,
>>> MISSING_MID,T_DKIM_INVALID autolearn=no autolearn_force=no
>>> version=3.4.0
>>
>> this does not say it's spam. it says it is NOT spam.
>>
>>
>
> I guess this is the header added by my own SpamAssassin for outgoing
> mails (vps81276.ovh.net is my server). However, the problem is still the
> same: Although this mail doesn't seem to be spam, it is always marked as
> it would be by Google. I just don't understand what makes Google think
> it is!
Suggest you move this thread to the mailops list and/or contact Google.
Re: Help determining what is causing mails being marked as Spam
Posted by Nicolás <ni...@devels.es>.
El 21/08/2014 11:07, Matus UHLAR - fantomas escribió:
>>> On Wed, 20 Aug 2014, Nicolás wrote:
>>>> Ok, already done that, waited a few hours and now the 'correct' DNS
>>>> host appears in the header, but is still marked as spam.
>
> On 20.08.14 20:14, Nicolás wrote:
>> This would be the latest test:
>
>> X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
>> vps81276.ovh.net
>> X-Spam-Level:
>> X-Spam-Status: No, score=0.5 required=3.0
>> tests=ALL_TRUSTED,MISSING_DATE,
>> MISSING_MID,T_DKIM_INVALID autolearn=no autolearn_force=no
>> version=3.4.0
>
> this does not say it's spam. it says it is NOT spam.
>
>
I guess this is the header added by my own SpamAssassin for outgoing
mails (vps81276.ovh.net is my server). However, the problem is still the
same: Although this mail doesn't seem to be spam, it is always marked as
it would be by Google. I just don't understand what makes Google think
it is!
Re: Help determining what is causing mails being marked as Spam
Posted by Matus UHLAR - fantomas <uh...@fantomas.sk>.
>>On Wed, 20 Aug 2014, Nicolás wrote:
>>>Ok, already done that, waited a few hours and now the 'correct'
>>>DNS host appears in the header, but is still marked as spam.
On 20.08.14 20:14, Nicolás wrote:
>This would be the latest test:
> X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on vps81276.ovh.net
> X-Spam-Level:
> X-Spam-Status: No, score=0.5 required=3.0 tests=ALL_TRUSTED,MISSING_DATE,
> MISSING_MID,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0
this does not say it's spam. it says it is NOT spam.
--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
REALITY.SYS corrupted. Press any key to reboot Universe.
Re: Help determining what is causing mails being marked as Spam
Posted by Nicolás <ni...@devels.es>.
El 20/08/2014 19:55, John Hardin escribió:
> On Wed, 20 Aug 2014, Nicolás wrote:
>
>> El 20/08/2014 15:29, Axb escribió:
>>> get fcRDNS ...OVH lets you set a correct rdns for you hostname.
>>
>> Ok, already done that, waited a few hours and now the 'correct' DNS
>> host appears in the header, but is still marked as spam.
>>
>> Any other idea?
>
> Please post headers from the latest test.
>
This would be the latest test:
Delivered-To: agmailaccount@gmail.com
Received: by 10.217.170.201 with SMTP id gx51csp651014web;
Wed, 20 Aug 2014 11:41:49 -0700 (PDT)
X-Received: by 10.60.70.65 with SMTP id k1mr51483241oeu.61.1408560108791;
Wed, 20 Aug 2014 11:41:48 -0700 (PDT)
Return-Path: <se...@devels.es>
Received: from mail.devels.es (mail.devels.es. [92.222.24.114])
by mx.google.com with ESMTPS id ow18si30489820oeb.94.2014.08.20.11.41.46
for <ag...@gmail.com>
(version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 20 Aug 2014 11:41:47 -0700 (PDT)
Received-SPF: pass (google.com: domain of services@devels.es designates 92.222.24.114 as permitted sender) client-ip=92.222.24.114;
Authentication-Results: mx.google.com;
spf=pass (google.com: domain of services@devels.es designates 92.222.24.114 as permitted sender) smtp.mail=services@devels.es;
dkim=pass (test mode) header.i=@devels.es
Received: by mail.devels.es (Postfix, from userid 111)
id EFDE21202940; Wed, 20 Aug 2014 19:41:44 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=devels.es; s=mail;
t=1408560104; bh=a/A6+BYLAO2+vq8y7s8N7Wz+VNNllrhxtir8ONLj5hU=;
h=From:To:Subject:Date:From;
b=ixZZbRmkSq0le67WlxbCx0rwHVvx7+STI8HCYxBSKpiaIzfdw4OA8vwmblHbiRprD
3iNJ0Mddik3EsB0zP6QI4JsyvVbXdtDPaHmelSCnPMlh62inYFMwNQCuRdUhnhU8+C
WwkqBK2UCdap2RXJPhYIy5ASn2xSUJV2eTFUx5XY=
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on vps81276.ovh.net
X-Spam-Level:
X-Spam-Status: No, score=0.5 required=3.0 tests=ALL_TRUSTED,MISSING_DATE,
MISSING_MID,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0
Received: from rpi.devels.es (unknown [77.231.204.119])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
(Authenticated sender: services@devels.es)
by mail.devels.es (Postfix) with ESMTPSA id ED0DE120293C
for <ag...@gmail.com>; Wed, 20 Aug 2014 19:41:43 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=devels.es; s=mail;
t=1408560104; bh=a/A6+BYLAO2+vq8y7s8N7Wz+VNNllrhxtir8ONLj5hU=;
h=From:To:Subject:From;
b=IFOjy8rFQMkMLqAgJ0HoL/ajpd5Rlj+acd3vPbgTFuHELY+e+sWsRwY2GA7IgOPVz
3qQXalitm4c5nR1Nnkt3MUKinyqx1xEpyo8Ted4Lopzga8meQy6+fL2t6FLe9NuG6A
YtpgBG8HKpZfdfThz2RKkArKD1R/kUOYINgbmdFs=
From: Test account <se...@devels.es>
To: Another user <ag...@gmail.com>
Subject: This is a test
MIME-Version: 1.0
Content-type: text/plain; charset=UTF-8
Message-Id: <20...@mail.devels.es>
Date: Wed, 20 Aug 2014 19:41:44 +0100 (BST)
This is a test
Re: Help determining what is causing mails being marked as Spam
Posted by John Hardin <jh...@impsec.org>.
On Wed, 20 Aug 2014, Nicolás wrote:
> El 20/08/2014 15:29, Axb escribió:
>> get fcRDNS ...OVH lets you set a correct rdns for you hostname.
>
> Ok, already done that, waited a few hours and now the 'correct' DNS host
> appears in the header, but is still marked as spam.
>
> Any other idea?
Please post headers from the latest test.
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhardin@impsec.org FALaholic #11174 pgpk -a jhardin@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
One difference between a liberal and a pickpocket is that
if you demand your money back from a pickpocket
he will not question your motives. -- William Rusher
-----------------------------------------------------------------------
4 days until the 1935th anniversary of the destruction of Pompeii
Re: Help determining what is causing mails being marked as Spam
Posted by Nicolás <ni...@devels.es>.
El 20/08/2014 15:29, Axb escribió:
> On 08/20/2014 04:24 PM, Nicolás wrote:
>>
>> The only one tip I have right now is that the reverse DNS query of the
>> server's resolves to a different host than the one sent in EHLO, but in
>> that case I don't know how to avoid that since the hosting where the
>> dedicated server is located automatically assigns their own host to each
>> IP. Could this have something to do with it?
>
> get fcRDNS ...OVH lets you set a correct rdns for you hostname.
>
>
Ok, already done that, waited a few hours and now the 'correct' DNS host
appears in the header, but is still marked as spam.
Any other idea?
Thanks
Re: Help determining what is causing mails being marked as Spam
Posted by Axb <ax...@gmail.com>.
On 08/20/2014 04:24 PM, Nicolás wrote:
>
> The only one tip I have right now is that the reverse DNS query of the
> server's resolves to a different host than the one sent in EHLO, but in
> that case I don't know how to avoid that since the hosting where the
> dedicated server is located automatically assigns their own host to each
> IP. Could this have something to do with it?
get fcRDNS ...OVH lets you set a correct rdns for you hostname.