Sam Varshavchik <[EMAIL PROTECTED]> writes: > Lloyd Zusman writes: > >> Therefore, putting an indication into the topmost Received header as to >> exactly how many Received-SPF that Courier writes is all that's needed >> in order to recognize only those Received-SPF headers that Courier has >> inserted. > > By the time the From: header is processed, the topmost Received: header > is but a distant memory.
Oh yeah ... I forgot about the need to read the entire message in order to do the SPF 'from' processing. >> It would probably take me a lot longer to dig through the code and >> figure out how to change the old Received-SPF headers to X-Received-SPF. > > That part is actually the easy solution, and that's what I'm going to do. Well OK! I was perfectly willing to try it on my own, but if it's easy for you and you're going to do it, then all I can say is "thanks!" This now will give us a nice, clean, deterministic solution. -- 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
