Sam Varshavchik <[EMAIL PROTECTED]> writes: > Lloyd Zusman writes: > > [ ... ] > >> Well, there is a difference in the BOFHSPFHARDERROR setting. It >> causes an SPF error to return either a 517 message or a 417 message, >> depending on whether the error condition is matched. But what I want >> is _neither_ to be returned during the SPF step. What I want to do >> is to have all the SPF checking to be performed and then for the >> SPF-Received headers to be set, and for the message to be passed to >> the next processing steps as if no error occurred, even in the case >> of an SPF failure. Then, I want to look at the SPF-Received headers >> within my courierfilter, and to decide at that point whether I want >> to accept the message, bounce it with a 5xx error, reject it with a >> 4xx error, or whatever. Is there any way to do that? > > Yes -- by listing all possible SPF status results as acceptable, using > =all.
But I now am using "=all", and SPF failures are still always triggering either 417 or 517 responses before the courierfilter gets invoked (depending on the existence/setting of BOFHSPFHARDERROR). This is the same behavior as when I was specifying all the statuses explictly in the "opt BOFHSPF*" settings. -- Lloyd Zusman [EMAIL PROTECTED] God bless you. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
