On Tue, 22 Nov 2016 12:18:14 -0500
Bill Cole wrote:
> On 22 Nov 2016, at 0:48, Pedro David Marco wrote:
>
> > Thanks Bill,
> >> . I don't know why some spammers do this sort of lame
> >> Received fakery, since it fingerprints their mail as spam, but it
> >> has been a fairly common practice fo
On 22 Nov 2016, at 0:48, Pedro David Marco wrote:
Thanks Bill,
. I don't know why some spammers do this sort of lame
Received fakery, since it fingerprints their mail as spam, but it has
been a fairly common practice for a long time.
But SA did not trigger any rule about the forgering...
I'
On Tue, 22 Nov 2016 05:48:29 + (UTC)
Pedro David Marco wrote:
> Thanks Bill,
> >. I don't know why some spammers do this sort of lame
> >Received fakery, since it fingerprints their mail as spam, but it
> >has been a fairly common practice for a long time.
> But SA did not trigger any rule
Thanks Bill,
>. I don't know why some spammers do this sort of lame
>Received fakery, since it fingerprints their mail as spam, but it has
>been a fairly common practice for a long time.
But SA did not trigger any rule about the forgering... and debug mode does not
showany message about unparse
On 21 Nov 2016, at 17:54, Pedro David Marco wrote:
Hi,
i have spam emails with a Received line like this:
Received: by 9-30-239-23.uocdn.net (Postfix) with ESMTPSA id 693A0C56B
with (unknown [158.69.130.12]) ; Sun, 20 Nov 2016 21:06:55 -0300
there is no parsing perl code for lines like this in
Hi,
i have spam emails with a Received line like this:
Received: by 9-30-239-23.uocdn.net (Postfix) with ESMTPSA id 693A0C56B with
(unknown [158.69.130.12]) ; Sun, 20 Nov 2016 21:06:55 -0300
there is no parsing perl code for lines like this in Received.pm module so the
relay 158.69.130.12 is neve
