On Mon, 30 Nov 2009, Per Jessen wrote:
On 30.11.09 16:41, Per Jessen wrote:
Anyway, how about a way to make spamd refuse to process a message
when it appears to to have any?
MTA is postfix, I call spamd directly using the spamc protocol (but
not spamc).
I have my own smtp proxy which calls spamd. (amongst other things).
Then that is where the decision to scan or not scan must be made. spamd
will scan whetever is sent to it.
That proxy shouldn't pass a message to spamd unless it has a Received:
header, and I would suggest that it should not pass a message to spamd
unless it has a Received header that was added by the local MTA; otherwise
you will have to make your SMTP proxy add a fake local Received: header
for spamd to interpret, including such data as the IP address of the
client, its rDNS name, etc. - all the information that the _real_ MTA
would put in the Received: header it adds.
WAG for the cause: you're scanning a message that is direct sender-to-you
before your local MTA has had a chance to put in the first Received:
header; in other words your glue is too early. In the messages that fail
in this manner is there only a single Received: header, for the local MTA
hop?
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
The yardstick you should use when considering whether to support a
given piece of legislation is "what if my worst enemy is chosen to
administer this law?"
-----------------------------------------------------------------------
15 days until Bill of Rights day
