> Can we add the features
> "whitelist_envelope_from" and "blacklist_envelope_from" that will be based
on
> the from envelope instead of the From: header?
Would it maybe be better to keep the rulename the same, and just change the
code to use the envelope-from in preference to from: if it is available? I
can't see a lot of value to maintaining a whitelist rule that used a known
forgable field when it might be able to use a better one instead.
Maintaining the existing rule names but changing the code to use the
envelope from if available means that existing rulesets will still "just
work", only better (if the info is available.)
Loren