On Wed, 2010-07-21 at 00:08 -0700, Daniel Lemke wrote:
> Ted Mittelstaedt wrote:
> > > How does SA scan binary attachments like .doc, .docx, .rtf, .xls, .zip,
> > > etc. in that case?
> >
> > It doesn't.
*nod*
> > At least, not like what you are thinking.
> > As you know an encoded attachment is a series of lines like:
> >
> > XXHUBKJVHLSJFWSJNDL:SANFKJHSBFSLJRWKSBF
> > DSKJNBFSHNF:LSJFLKSNFLKJSBFLK:SNFLKSNFS
> > FJSHBFLKSHNFLKNSFL:SF:LSNFLKSNFLK:SNFL:
> > KFSLKHFDSHNFKDNFLDKNFLKDNFLKJHDBIAVFBUB
> >
> > SA scans that. Of course, there is nothing there that matches
> > anything.
Nope, this is not how SA works in the general case.
As Henrik mentioned in an other sub-thread, this is correct only for the
rarely used 'full' rules. And in that case, applies to encoded text
parts just the same.
The most common rules are applied only to the (decoded) textual parts of
a message, and usually even a rendered, normalized version.
> Well in that case, I revoke my adoption regarding the mime types ;)
Don't. ;)
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
