I'm trying test dspam (latest git version). What seem for me quite unacceptable is displaying base64 (maybe quoted-printable too) Sender and Subject items as-is, which make them human-unreadable. Especially in managed groups - I'm now looking (as group manager) in web UI/history page at item with Sender: "=?iso-8859-1?B?RXVyb3BlIERlYnRjb2xsZWN0?= Subject: =?iso-8859-1?B?Q29sbGVjdCB5b3VyIHJlY2Vp?=
This makes any human classification unpossible, when not know Sender, Subject and without searching in logs neither recipients (as manager see items for all group members). What good is dspam perhaps excellent classification engine, when I'm not able learn it? I'm thinking several months ago there in list was mentioned that some patch solving this problem was accepted and included in, but is it true? Rem.: I'm using hash driver, but it probably don't matter, I think history items are taken from user's log (what in case managed group isn't optimal, better would be take system log and in webui display recipients too). I not know how is treated quarantine webui page. but same problem I see there too - but there at least I can display mail source ant decide on that. Thanks, Franta Hanzlik ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
