On Feb 25, 2009, at 8:14 AM, Ray Corbin wrote:
It depends on your environment. I've seen where it is helpful and
where it is overwhelming. If you are a smaller company and want to
know why you keep getting blocked then those should help. If you are
a larger company and get a several hundred a day, but you send 100k
emails to AOL then it is not as big of a deal. If you are a shared
hosting provider and you get a lot of them you should look into what
is being sent to AOL, such as forwarded spam from customers 'auto
forwards' (isolate the auto forwards to a separate IP address and
simply don't sign up for the FBL for it).... If you have a good
setup where only customer-originated email is being sent through the
IP's you have a FBL on, then it is useful and you shouldn't get as
many complaints.
Ray, you don't get it. What comes from AOL is literally every step
in a mother-daughter conversion. You get to read the entire thread.
Loving chat, mother and daughter back and forth. But one of them is
hitting SPAM on the e-mail *AFTER* replying to it and writing a nice
letter back.
This is abuse of the abuse department. This isn't spam. Reading
through ~3k of these not-spams every day doesn't help us solve any
actual abuse problems.
Feedback loops will not be useful until the providers of the feedback
loops accept reports about use of the spam reporting tools, and are
willing to go fix their user behavior.
--
Jo Rhett
Net Consonance : consonant endings by net philanthropy, open source
and other randomness