On Sun, 02 Sep 2012 18:48:15 -0400
drew@gmail.com wrote:
> Gentlemen,
>
> Thanks for replying so quickly. I'm quite the newbee in this area and
> am grateful for your advise. While the new header entries were first
> noticed after enabling SA, it was not obvious that Exim could be
> another
Gentlemen,
Thanks for replying so quickly. I'm quite the newbee in this area and am
grateful for your advise. While the new header entries were first
noticed after enabling SA, it was not obvious that Exim could be another
suspect. I will investigate whether it can configured to interpose or
On 2012-09-02 23:14, Dave Funk wrote:
> Not sure where that 'X-Identified-User' header comes from, maybe
> it's an Exim thing. It's not a SA header. All headers that SA adds
> start with 'X-Spam-' (eg: X-Spam-Report: or X-Spam-Status: ).
>
> It could be that the "glue" you're using to connect SA
Why are you blaming SpamAssasin for those headers?
The 'Received:' header is a standard "trace" header that your MTA is
supposed to add to each message that it processes (see RFC-2822).
Note the end of the header you quoted, it even has Exim's name in it.
Not sure where that 'X-Identified-User
Hello,
I've poked around the archives and faq and cannot find a solution for my
case. Our Church has a website hosted by a popular service and recently
we setup email accounts plus SpamAssassin. It is all working nicely
except for one alarming thing I found in spamassassin generated headers.
On Sat, 2012-09-01 at 01:14 +0100, Ned Slider wrote:
> Hi list,
>
> Would anyone from ReturnPath care to take a look at the following:
>
> Received: from mail5.eventbrite.com (mail5.eventbrite.com [67.192.45.102])
>
> which just spammed a contact@ address scraped off website and has -5pts
> awa
