> "last" received? or "first"? (meaning to say, the oldest). anyway, > yeah, that's probably accurate enough. Subject should also be a good one, > except for the few spams that put your name (or what they think your name > is) into the subject. You could also check reply-to or mailer-agent (or > whatever its called).. From doesn't always work so well since a lot of > times it falls into the undisclosed.recipients@my-server or > new.customer@my-server, or whatever. I'll start paying attention to that > info, too...
Yes I meant oldest... the one furthest in in the headers. :-) Subjects being slightly different shouldn't be a problem because you can do soundex or "like" searches when you have the data set. I was debating the reply-to and from but maybe it's best just ot use all of them for now. Aww what the hell, parse up all the headers... it's only disk space and CPU time. :-) I can always drop data that doesn't seem to be helping later but i need most everything at the start to make some decent analyses. Regards, Andrew _______________________________________________________________ Hundreds of nodes, one monster rendering program. Now that’s a super model! Visit http://clustering.foundries.sf.net/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
