On Sun March 14 2004 01:33 pm, Stephen Bosch wrote: ugh.. ok well how about this scenario... we use surgemail as our pop3 server. it has a place to shell out to spamassassin and then come back for delivery. would that work? i do not want anything delivering to our users mailboxes except surgemail, otherwise too many user features will break. however, since the spam quarantine area can be defined separately and used via spamd's web facility, can it work in that fashion?
> Chuck wrote: > > On Sun March 14 2004 12:29 pm, Cody Baker wrote: > > > > from all the reading i have done so far, it looks like it can be called > > like sa or your a/v program. if it finds spam it will quarantine it and > > if it is clean then it returns and the qmail system carries on to deliver > > the mail. I hope I am right.. if so it will be almost a plugin changeover > > (not including database/user-quarantine area/web interface).. > > > > my only concern in using it in this fashion is if it creates user areas > > for each held message, then it will make a LOT of user areas that will > > never get used since we use qmail only as an smtp gateway, and many > > domains use it just for its capabilities and we forward mail on to their > > private pop3 servers. i suppose we can offer the user admin spam area as > > a perk:) > > Whoa, whoa whoa... time for me to pipe in here. > > I've been on the dspam list for some time now. I've even looked at the > header files for the library to get a better idea of what it does and how. > > 1. This discussion is a dead end -- dspam assumes a monolithic MTA and > that it will act as an intermediary to the local delivery agent. If it > is to be used before messages are queued (as qmail-scanner is with > qmail) it will have to be rewritten. Some people have already started > discussing this -- you'd use the libdspam library to accomplish this task. > > 2. Using qmail-scanner with dspam totally defeats the design philosophy > of dspam, which is to ensure fast execution times and allow its use on > high volume servers. qmail-scanner is written in perl and is simply too > slow for that. > > 3. User dictionaries complicate things. If dspam can be made to include > user information in the global dictionary, it may not matter, but this > is an outstanding question. > > If you guys are serious about a pre-queue spam filter and if you have > any programming skills, I would suggest you join the dspam-dev list and > take up this discussion there -- there's going to be a lot of work > needed to get where you want to go from here. > > -Stephen- > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IBM Linux Tutorials > Free Linux tutorial presented by Daniel Robbins, President and CEO of > GenToo technologies. Learn everything from fundamentals to system > administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click > _______________________________________________ > Qmail-scanner-general mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general -- Chuck "...and the hordes of M$*ft users descended upon me in their anger, and asked 'Why do you not get the viruses or the BlueScreensOfDeath or insecure system troubles and slowness or pay through the nose for an OS as *we* do?!!', and I answered...'I use Linux'. " The Book of John, chapter 1, page 1, and end of book ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
