On Friday 26 March 2004 16:58, John Peacock wrote: > If you (and others in your position) would do this (block outbound SMTP), > you would be doing the Internet as a whole an immense service. As long as > you make it an easy webform and advertise it well in advance of > implementation, your customers shouldn't complain too much. You could > proactively set your firewall to log all outbound SMTP transactions and > send the administrative account for that address a warning that this will > be blocked in X days unless they register.
Erm, I'd tell my cable provider precisely where to stick it they did that and yeah, I wouldn't complain too much, I'd just switch to someone else. Yeah, I have a cable connection with blueyonder, but I never use the email address of [EMAIL PROTECTED] and I'd be daft to do so - I have a domain of my own (or I use some 3rd party generic mail) and I send all my email via SMTP to the mail server provided by my hosting company - and I think you'll find plenty of other people do this too. Now, asking at signup time if you'd like this protection, with the option to say "no leave me alone" or "help me stay clean, block these ports except to these addresses" I don't object to, but please don't suggest that home users aren't allowed basic connectivity - if I wanted to be treated like a child I'd go back to school. -- Tim
