mouss wrote: > Alessandro Vesely wrote: >> mouss wrote: >> >>> 3- never block your own users with methods designed for "inbound" mail. >>> This includes DNSBLs, spamassassin rules, ... etc. >> >> One exception is when you have methods that can determine that mail >> is being sent by automated malaware. Viruses, e.g., are dropped from >> external relays and customers alike. > > well, I really meant "designed for". so this is not an exception, > because virus filtering is not designed "for inbound" mail. it is > designed for all mail. I don't mean one should not filter outbound mail. > but the methods to do so are not the same as those that apply to inbound > mail.
Anti-virus was an example. Email Service Providers could also use anti-spam rules to monitor their own subscribers. It's not just software reuse: not distinguishing between inbound and outbound mail the original SMTP protocol allows to _design_ filters generically. OTOH, existence of port 587 may indicate there is something wrong with that approach... In facts, there are also services designed for monitoring customers' outbound mail, e.g. some of those provided by ProjectHoneyPot or CAUCE, that we may consider complementary to DNSBLs, in that sense. -- ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
