> The reason, that the mail was blocked is written clearly in the log: > [spam found] (DNSBL, 207.236.237.40 listed in dnsbl-1.uceprotect.net > dnsbl-2.uceprotect.net
I suspect that the implication of this is that there needs to be a change to assp. Here's my logic for that: 1) large telephone company ISPs are the source of quite a lot of spam, as well as being the source of legitimate e-mail; 2) in the real world, we'll never get these ISPs to react to requests to: a) fix their DNS records; b) prevent spam going out from their servers or computers on their networks. I suspect the only practical work around for this is for assp, once it knows that the domain is likely to be sending spam (i.e. after finding out that the IP and/or domain has badly configured DNS records, is in a DNSBL, or, say, has spammy content), to check the sender address against the whitelist, before sending the message to the spam folder. There's just no way we'll ever stop large ISPs sending spam as well as sending real mail. Reluctantly, we (i.e. assp) have to deal with this. It's not up to us (i.e. the receiving e-mail server admins) to remove these spamming ISPs from the DNSBLs. Anyone have any thoughts about other ways around this conundrum? T. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
