> At 03:00 AM 9/24/1999 -0700, you wrote:
> >Another thing that ISP coulds start doing (we are in process with
> >this now, but on a monitoring only basis, instead of a deny we
> >just log them) is to block all outbound from AS tcp 25 setup packets.
>
> Hmm, maybe I'm interpreting this wrong (I hope so), but I interpret this as
> saying that basically you'd only be able to mail things through your local
> isp's mailhost. It means that if you use several different mail servers,
> all mail would still have to go through the local isp's. Personally, I
Yep, thats exactly what I am saying.
> would immediately unsubscribe to any isp that decided this was acceptable
> behavior on their part. I use the mail server at work for all my outgoing
> mail. Why? Because the machine is lightly loaded and I don't have to
> worry about my mail getting lost in the depths of my isp's mail server for
> a couple hours because their loads tend to run high. (Hell, I don't
> generally even use the email account provided by the local isp because of
> load issues, my work account is so much more reliable).
Our outbound smarthost smtp server is carefully monitor, has never lost
a single mail message, and screaming fast at getting email out. After
all we also run commercial opt-in bulk emailing for large clients and
we do know how to get 100's of thosands of messages out in a real fast
way. Probably mork work has been put into our smarthost than any company
has bothered to put into thier smtp relay.
Your work also has a serious security concern if it allows this you to
directly attatch to it's port 25. Can you say firewall circumvention...
I thought so.
--
Rod Grimes - KD7CAX - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
