On Nov 28, 2006, at 6:03 PM, Professional Software Engineering wrote:
Generally speaking, I don't like to try to track what some given MUA's
formatting is, least of all M$ crap. There's a general "is it
formatted
within norms" test here already.
But this one is so obvious when you finally see it, and it hasn't
changed in months.
Here's the three that came to hand the easiest from the trash folder
I'm clearing out now:
Message-ID: <01c712ff$e0c732e0$6c822ecf(_at_)deboramsf>
Message-ID: <01c712db$9be56b70$6c822ecf(_at_)pej>
Message-ID: <01c712b2$be5af860$6c822ecf(_at_)lfnlxwrglds>
Now if we were to compare it to a single item from a real M$ LookOut
client:
Message-ID:
<004b01c7128c$838680e0$261ea8c0(_at_)strongmailsystems(_dot_)com>
And if we were to count the number of digits in the first subfield,
and compare...
An interesting pattern would emerge.
Well, across _many_ (but certainly not _all_) of the messages I see
hitting
one account, the last sequence of digits in the messageid is constant:
$6c822ecf
There's also some that have eight 0's there.
In any event, the recipe below is catching the variants on this.
My rule
of thumb is to avoid looking for hard-coded strings and to avoid body
searches, and this recipe does neither.
Hard-coded strings are sometimes useful.
And personally, I try to avoid the From, To, and Subject: headers, as
rules based on them have a tendency to fail first.
" Look in the places where they don't want you to look....
Aloha mai Nai`a!
--
"Please have your Internet License http://kapu.net/~mjwise/
and Usenet Registration handy..."
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail