3 -0400 (EDT)
Original-recipient: rfc822;[EMAIL PROTECTED]
- Original Message -----
From: Mark Walmsley <[EMAIL PROTECTED]>
Date: Saturday, May 17, 2008 7:14 pm
Subject: how do you change the way spamassassin parses the recieved header.
To: users@spamassassin.apache.org
> The source
The source of my spamd problem is the way spamassassin parses the header.
Example I can't use whitelist_from_rcvd because java messaging server forms
it's header like this.
Return-path: <[EMAIL PROTECTED]>
Received: from azkaban.changingstreets.net ([209.255.5.37])
by hermes.changingstreets.com
anyway to see what the mta is passing to spamd?
- Original Message -
From: Matt Kettler <[EMAIL PROTECTED]>
Date: Tuesday, May 13, 2008 8:16 pm
Subject: Re: spamd
To: Mark Walmsley <[EMAIL PROTECTED]>
Cc: users@spamassassin.apache.org
> Mark Walmsley wrote:
> &g
Spamd is not using whitelist_from_rcvd or whitelist_from_spf in local.cf
but when i run a test msg spamassassin --test-mode < 113.msg
orspamassassin -D < 113.msg
The whitelist_from_rcvd and whitelist_from_spf are working
I've even tried setting the path. Here is how I'm launching spamd
/opt