Steven W. Orr writes: > > > And this is my point. SA *DOESN'T* work on messages after they have been > received. Since I use spamass-milter, SA sees the messages before > reception is completed. (You're free to do otherwise.) Then when SA > decides that the message doesn't conform to its high standards, the report > of that fact goes back to spamass-milter which then returns status back to > sendmail. The current result is a reject 5xx status. So all we need is for > SA to manage one extra table and to allow some sort of reportage that > spamass-milter could be mucked to understand. > > Is this making sense? > Yes. And if you can manage to do the heavy lifting a lot of people will thank you. (I have little problem accepting that you can do pretty much anything via milter. But there's enough stuff that looks tricky that I'd be surprised if it goes high on anybody's todo list)
To get back to your original point (memory resident versus databases) there are some interesting setups that you can look at using mimedefang. http://whatever.frukt.org/mimedefangfilter.text.shtml and from the wiki: http://www.mimedefang.com/kwiki/index.cgi?Greylisting I understand, you're probably not interested in mimedefang. Still worth a look IMO.
