> First ask which issue you want to solve, do you want to just filter or
> do you want to fix the customer end? See the list of questions in my mail.
Baiscally, you want to filter and protect yourself. Your are an ISP not a security
assessment company. Warn the customer and send them and dos and dont's about emails.
> Thus the case where an IP has sent spam and you already got an abuse report?
> Which was already, in part, harmed by the above, you already have an
> abuse report.
Yes, that's right. How else could it be?
That's the whole point of this message ;-)
> Do I understand correctly that you will have:
> { Hosting Network } ---> { SMTP cluster with filtering} -> { Internet }
Yes, that is about right.
> and do not allow any of the other IPs in the Hosting Network to send
> outbound SMTP? Depending on the type of customer (see the question in
> previous mail) they might not want to rely on your SMTP server for instance.
Sorry, but who cares? Either they use the setup you offer them, either they
have their own SMTP servers and the problems is no longer your technical responsability.
If something happens, they are liable for it, period.
Out of scope for my request.
> SPAM / UCE / UBE is very well defined.
> and various other places.
Yes, now the question is how do you define the border between prospecting and spamming?
Not expecting an answer here, only a court ruling would have any value here.
I refer to customers who are sending UBE and are not even aware of it!
> Actually the exact same techniques apply it just depends if you want to
> invest money (hence the question about that) in if you want to educate
> them properly or not... (hence the question about how you contact them).
One must live in the Disneyland® realm to believe that providers to educate their customers.
Back to earth please!
Anything to suggest so far or are we just stuck into a loop of ping-pong email replies that will go nowhere?
Cheers,
Gregory