X-Spam-Orig-To headers inserted by spamass-milter

[Todd Lyons]

I am running spamass-milter-0.3.0 and sendmail-8.13.4.

I am (still) working on a quarantine system.  In my trials I found that
some spams weren't being stored in the database because they did not
contain the proper headers.  I started looking at the ones that got
through, and found that it did not have an X-Spam-Orig-To header.  Since
I was filtering on the X-Spam-Orig-To, this was why they were missed.
After a little more examination, I found that those emails contained a
header X-Envelope-To.

In examining the emails, all emails had only one or the other header.
After looking at the spamass-milter code, both headers seem to be
inserted by spamass-milter.  Can you quantify what occurs that makes it
insert one or the other?  My c/c++ is not very good, but it seems to me
like it wants to put an X-Envelope-To, but if it doesn't have an email
in assassin->recipients, then it puts  an X-Spam-Orig-To.  Am I reading
this correct?  Why is it like that?  Why not just always put one or the
other in?
-- 
Regards...              Todd
There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo.  Please use in that order. --Ed Howdershelt
Linux kernel 2.6.11-6mdksmp   3 users,  load average: 1.05, 1.25, 0.87