|
I've thought that this might be possible as an external test in this
way, but I have yet to get around to testing it out. It could be that
the %HEADERCODE% variable isn't populated until later like %WEIGHT% was
before modification, and if so, enabling it should provide a sufficient
mechanism for those of us that care to achieve this level of detail.
An external test would also be available to all versions of Declude
instead of a solution by way of a filter that would only be appropriate
for Pro users, albeit more difficult to integrate for some. The only real footnote is that there is only one code returned for both SPAMHEADERS and BADHEADERS, and occasionally these will double hit. Personally I could do without the double hits and would prefer to score each code individually (some not at all). It certainly works into the framework of an external test quite well since it only one result is possible at one time. It would also help to have a list of the codes if one doesn't already exist. If we wanted definitions, we could look them up in the tool that is provided. Matt Scott Fisher wrote: -Scott, Would this be possible to check in an external test? Is the %HEADERCODE% variable available? Here's my early thoughts: -- ===================================================== MailPure custom filters for Declude JunkMail Pro. http://www.mailpure.com/software/ ===================================================== |
- Re: [Declude.JunkMail] Campaign for spamheaders filter variab... Scott Fisher
- Matt
