Why is APEWS included by default in the DNSBL? APEWS is notoriously
overeager, blacklisting huge subnets that are "guilty by association" or
inaccurately listing entire ISP subnets as dynamic IPs. I think a huge
percentage of ASSP users would fall under the latter, being small
businesses that host their own email on static DSL/cable lines. That
seems like we're biting the hand that feeds us.
All my clients using ASSP are inaccurately listed under APEWS as
dynamic, even though they're all static. Even my servers are listed,
and I've had a true "legacy" static IP for over 7 years, not those fake
PPPoE "sticky" IPs. And before anyone says it, netblocks are not
subject to APEWS normal 7-day automatic deletion and no, there is no way
to get removed from an APEWS netblock.
Shouldn't APEWS be removed and just listed below as optional like the
UCEPROTECT lists are?
--Bennett
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
