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.
...
Thoughts?
Why not just "X-" modify any already existing SPF-Received headers? That is, if a message coming in already has SPF-Received, modify that header to be X-SPF-Received, and then let your instance of courier slap on the new set.
Doing otherwise strikes me is leaving users open to receiving spoofed SPF-Received headers.
best, Jeff
------------------------------------------------------- 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
