On Mon, 22 Sep 2003, Pat Lashley wrote:
Can't you get what you want using the "envelope" extension?
Probably. "But..." the rules are being generated by smartsieve. Relying on smartsieve to know that return-path is special (compared to any other random header) and that it should use envelope seems a little goofy. I can also see some utility in having the return-path and other generated headers in the header cache.
I would think that the right solution would be to make smartsieve know about the envelope extension and have it explicitly offer comparisons against envelope sender and envelope recipient rather than the Return-Path and possible Envelope-To headers.
Anyway, the attached (compiled but untested) patch splits fill_cache() into a second piece (insert_cache_element()), and uses the new function to insert the return-path into the header cache.
So you wind up with sieve scripts that won't work as expected on other conformant sieve implementations.
-Pat
