> > Yes, but this is the price for a managed whitelist ;) > > I think this addon may be added and not be a replacement of the > > present engine for the From line. > > > If adding such functionality, then using configurable options in > dspam.conf would be from my viewpoint the best way to go. For example: > > For the original algorithm (off by default): > FuzzyWhiteList Off > > For the new, less accurate (from a statistical viewpoint) algorithm: > FuzzyWhiteList On >
Why not, but I don't understand why you say this is less accurate. DSPAM will continu to compute tokens as it was done before, and at the end it will check if email address is in the whitelist and tag the mail with "X-DSPAM-Result: Whitelisted". It is the same way of present whitelist, but management could be done by the end-user. > > > Whitelisting on the MTA level may be harder to manage depending on > > your network architecture. > > I have some people who send report when DSPAM make a mistake but > > every email are different, so one email address could take long > > time before being whitlisted. > > In the first times of using a email address, the user's dictionary > > is building, this can take some time. People don't want to report > > many and many mail for corresponding with others. > > > Are you now talking about an automatic way? I had the impression you > talked earlier about a manual intervention by the user. Aka: Adding > domain or email into a whitelist for DSPAM by hand/manual. I could > name a bunch of possibilities how to handle whitelisting on the MTA > level. On Postfix for example you could use a policy service with > restriction classes to handle whitelisting on the MTA level. Or you > could use PCRE tables to handle whitelisting on the MTA level. Or you > could use a database to handle the whitelisting (for example the same > way as Amavisd-new does it), etc... I really don't see such a big > problem in handling this on the MTA level. I talke about a manual intervention by the user. I have 3 DSPAM servers running with Qmail, whitelisting on the MTA level is not impossible, but with a centralized DSPAM database, this is much more simple and clean. > > > > I talk about a managed whitelist. > > > By managed you mean managed by the end-user and not by DSPAM. Right? > Right ;) !DSPAM:1011,4869ed7f150921917512041!
