> In this case \x20 is encoded and this is not right - currently I've no > clue where this is comming from.
Nor I do, all I can say is that it sounds like only some headers (like the SPF one) are getting mangled that way that's why I think there may be a bug; not a big one but ... > But be care full - there are some ASSP - headerlines that has to > be MIME-encoded (if some contains a unsave character) - so any > application behind ASSP has to be able to decode MIME-words! I understand that, when a header carries informations coming from "the outside" it's advisable to clean them up to avoid "exploits" but in this particular case I can't see the need for such a thing, all in all that's just a number added directly by ASSP and not coming from "the external" ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
