Jeroen van Aart schreef: > Pascal Nobus wrote: >> I want to kick-in in this. >> As a system administrator myself maniging email for about 5.000 domains, >> Some examples: users get (if they want) every night a list of mail which >> was attended to them, but blocked by assp. > > Why not make it easier for yourself and them. If an email is found to be > spam send an error to the sending email server. So the email doesn't > just disappear into void silently and the sender knows something went > wrong. Then put those users who can't handle any false positives being > blocked at all on spamlovers (and they can deal in whatever way they see > fit with email marked as spam). In my experience most users tend to find > a notification about possible spam waiting to be checked also spam.
Well, that's exactly what happens! Whe block mail before its delivered to our mailboxes. That's why assp is in front of your mailserver! The problem is that not only people send emails, robots do as well (mailinglist, accounts which must be renewed etc. etc.) With the daily report users can put this emailadresses to the whitelist, senders cannot do that, and robots don't usually read mail (just send them). > The whole concept of junk folders and quarantines or whatever fancy term > has been thought up is just flawed and ends up being ignored and even hated. Well, that why we _don't do that_ regarding your other question (why not run 1.3.3.1?) see my previous mail: 1.3.3.1 hit our boxes with 100% CPU, which is fixed in 1.3.3.3... best regards, Pascal ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
