|
From: Lionel B. <lio...@bo...> - 2007-01-19 18:33:06
|
Micha Silver wrote the following on 19.01.2007 19:25 : > Dan Faerch wrote: > > >> I agree with Lionel. >> Its best letting sqlgrey do all this since you really cant tell who is >> valid senders if you dont temporally reject first, and then sees who >> comes back. (which is what greylisting does) >> >> If you are worried that delaying all mail for 5 minutes at the same day >> you enable sqlgrey, consider using the "discrimination" feature from >> 1.7.4+. That will let you, via regular expressions, select what to >> greylist and what to just let through . Good way of slowly introducing >> greylisting by making the discrimination rules more and more restrictive. >> >> >> > Where can I see more details on this 1.7.4 version, and the > "discrimination" feature? > We've been using greylisting for several months, and while spam has > indeed decreased dramatically, we have to spend time every day or two > adding new entries to the client_fqdn_addr.local file because of false > postivies. I think the problem is mostly mail servers that resend almost > immediately and get marked as spam. > What do you mean by "marked as spam"? mails should either be rejected or received in the end never "marked as spam" (at least by SQLgrey). If you need to add entries to client_fqdn_addr.local in order to receive mail from them, I'd like to know them. Lionel. |