|
This is an Off Topic post. Due to the possibility of causing grief to some on this list with an Off Topic post’s sometimes excessive amount of responses, please reply to me in private with your policies, thoughts, or responses. Also, this is really two questions in one e-mail, so it may generate more e-mails than most would want to see on the list anyway. J
1). As an ISP, what is the general consensus of allowing anyone (or everyone) to have the ability to have an SMTP server in operation on their machine while connected to the ISP’s network?
This question arises from time to time because we get complaints from various other people of spam being relayed from one of our IP Addresses and upon verifying who was using that IP Address at the time the relaying occurred, it comes back to dynamically assigned IP Address pools (both dialup and DSL).
2). As an ISP, what has everyone done to guard against bandwidth hogging infected machines (the latest seems to have been the Nachi or Welchia worm outbreak)?
A. Did everyone choose to disable this by blocking those ports the worm uses (which incidentally blocks the ability to use ping and tracert as testing tools)? B. Or, is there another way to do this that still lets us test across the network with ping and tracert?
|
- [Modus] OT: Allowing SMTP on an ISP's Network + Nachi (Wel... Mike McTee
- [Modus] OT: Allowing SMTP on an ISP's Network + Nachi... Mike Roberts
- [Modus] OT: Allowing SMTP on an ISP's Network + Nachi... Frank M. Cook
- [Modus] OT: Allowing SMTP on an ISP's Network + Nachi... Ronnie Franklin
- [Modus] OT: Allowing SMTP on an ISP's Network + Nachi... Jim Barstow
- [Modus] OT: Allowing SMTP on an ISP's Network + Nachi... Mark Thornton
