On 3/21/2013 2:32 PM, Thomas Eckardt wrote: > I don't think that this will be possible in V2. It is planed to have full > recipient/domain based lists (addresses/domains/IP's) in V3. > > How ever: > > - the user does not know anything about IP's > - IP's are global for all recipients and domains - ones spam is others ham > - from which lists should the IP's be removed ? > - should a user be able to add IP's to noprocessing (the only setting that > bypasses nearly all black lists) ? > - what IP's should be removed / added - the sending, all on the routing > way, the originating ... any combination of them ? > - should assp retrieve the SPF record for the domain to make all possible > sending IP's (white, NP, not black )? > > I think this list of questions is expandable. At least you would have to > predefine/maintain every possible case - a very, very large rule set. >
Couple items: - Checking SPF would be excellent - Checking DNS MX records in the absence of SPF also (unless that is done by the default SPF override) - All IP's that block or delay mail should be removed from block/black/grey lists - If an IP is ham for any user, then it needs to be not blocked by the system - Automatic non-processing may not be good - simply removing from the black lists and possibly adding to whitelists is sufficient. However, what might be good would be an email to admin - showing such removals and allowing for adding to the noprocessing. Kind of like the spam summary report - but this one instead shows either addresses/servers that have been removed from blacklists, or just new servers that users are communicating with. -- Daniel ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
