In the absence of any response to my recent email (quoted at the bottom
of this message), I am hereby proposing a patch to the latest version of
Courier which will solve the problem of us not being able to tell which
Received-SPF headers were added by Courier's message processing, and
which may have been sitting around in the message since before Courier
got a hold of it.

If there is a consensus as to the value of this patch, I will write the
code and submit this patch, myself.

In the email below, I put forth 3 alternatives for solving this problem.
The one that I am proposing here is the first one I mentioned.

I propose that within the topmost Received header that Courier inserts
into every incoming message, an extra line be added when SPF processing
has taken place.  It would look like this:

  spf helo=result mailfrom=result from=result

The "result" will be any of the valid SPF result codes ("pass",
"softfail", etc.).

Each parameter ("helo=result", etc.) is optional, and only appears if
that particular SPF test is performed.

Examples:

- All three SPF tests were performed, and in each case, their
  result is "none":

    spf helo=none mailfrom=none from=none

  From this, we know that Courier has added 3 Received-SPF headers.

- The 'helo' and 'mailfrom' tests were performed and passed.  Because
  of the 'mailfromok' parameter in the 'from' test in the 'bofh'
  file, this causes the 'from' test to be skipped.

    spf helo=pass mailfrom=pass

  From this, we know that Courier has added 2 Received-SPF headers,
  one for the 'helo' test, and one for the 'mailfrom' test.

- Only the 'mailfrom' test is performed, and it resulted in a
  softdnserr result.

    spf mailfrom=error

  From this, we know that Courier has added 1 Received-SPF header
  for this 'mailfrom' test.

- No SPF tests are performed.

    No 'spf' line is added to the topmost Received header.
    (alternative:  "spf none" is added)

  From this, we know that Courier hasn't added any Received-SPF
  headers to the message.

Thoughts?



Lloyd Zusman <[EMAIL PROTECTED]> writes:

> Sam Varshavchik <[EMAIL PROTECTED]> writes:
>>
>> [ ... ]
>>
>> Yes; however note that Courier will leave any existing Received-SPF:
>> headers, perhaps inserted by the previous mail relay, untouched (except
>> that they will be moved to the end of the existing headers, so that
>> Courier's headers always come first).  And, the previous relay can
>> easily be configured to use the same hostname.
>
> Understood.  Thanks.
>
> So how can I know for sure which of the Received-SPF headers were
> inserted by my Courier instance, and which were hanging around from
> before?  The number of Received-SPF headers that Courier writes is
> variable, and furthermore, it depends on the settings in my 'bofh' file
> at the moment that the email is going through my system ... which could
> change by the time any given message is being handled by my own filters.
>
> Is there some deterministic way for us to always know exactly how many
> Received-SPF headers that Courier writes into a given message?
>
> If not, how about putting the count of Courier-written Received-SPF
> headers into the topmost Received header that Courier writes?  It would
> then be irrefutably accurate.
>
> Or if that's not possible, could the older Received-SPF headers be
> changed to X-Received-SPF headers?
>
> Or how about putting one more place-holding header into the message,
> right after the final Received-SPF header and before any others that
> other hosts might have written ... maybe something like
> X-Courier-SPF-Info which contains some sort of summary of Courier's SPF
> processing.  Upon encountering this header, we could be sure that there
> are no more Courier-inserted Received-SPF headers to process.
>
> Thoughts?
>
>
> -- 
>  Lloyd Zusman
>  [EMAIL PROTECTED]
>  God bless you.
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by BEA Weblogic Workshop
> FREE Java Enterprise J2EE developer tools!
> Get your free copy of BEA WebLogic Workshop 8.1 today.
> http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
> _______________________________________________
> courier-users mailing list
> [EMAIL PROTECTED]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
>

-- 
 Lloyd Zusman
 [EMAIL PROTECTED]
 God bless you.



-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to