Keith, you have good stories.  BTW, I was one of those folks working in Corporate CYA America was a webmaster.  I didn't last long.  Couldn't stand the way things worked.  Our firewall administrator didn't even know the basics of TCP/IP, and it took several weeks and meetings to get him to stop routing private IP space out to the Internet.  He's probably still working there.  Lucky him.  He probably thinks that I'm an a** h***.  I have very low tolerance for that type of thing in the quantity that existed.  The lead network guy for a worldwide company once blamed me for a problem of his because he didn't know you could bind more than one IP to a NIC...  I've got more too :)

Anyway, I'm not sure if you were acknowledging my suggestion about DNS or exploring it further.  For the sake of this reply, I'll assume the latter.  If you start up the MS DNS service on your box and enable forwarders to look at your linux box, it will cache locally without needing to open all of those connections.  Even though your local DNS server is on fast ethernet, there's still lots of local overhead there.  If most of what you have is cached already, that would save a bunch of resources I would think.  Stress on the "think."  It's easy to try and back out of though.

It's interesting that Microsoft is sending an engineer.

Matt


Keith Anderson wrote:
As far as the Microsoft update status, I've been granted a Microsoft
engineer who is paying us a visit this week to witness all of this for
himself.

  
Regarding that one problem customer posting their entire
directory on the Web; you might want to suggest that they
    

It's not on their web page anymore, but the damage is done.  You can't pull
them back off the spam lists once they get out there.  And to make sure
someone took the blame, they fired their web designer who put the names
online, even though I'm pretty sure they asked him to do what he did.
Welcome to Corporate CYA America.

  
Since your question about outgoing E-mail hasn't been
answered yet, I'll try.  Anything in your Global.cfg that
says WARN, IGNORE, HOLD, or other actions seen in your
    

Yes, but aren't the tests done anyway, just not triggering an action?
Doesn't matter, since I don't want to disable it anyway, but I was curious.
As soon as I dig myself out, I'm going to check out Hijack.

  
something to look in to.  Also, when you say that you have a
caching server in front of Declude, is that on the same box?
    

Seperate box running Linux on a separate LAN.  Mail send, receive and DNS
lookups are all done on different NICs.  I can't be sure, but I don't think
there's another Imail installation that looks anything like this one.
Frankly if I had been able to predict that it would grow this big, I
wouldn't have used Windows or Imail, but migrating it at this point would be
a negative experience.

  
Someone else mentioned to me the problem of WAP recently.
Hopefully there will evolve a blocklist for these things, and
considering that they problem should be for the time being,
    

What we really need is stronger encryption and authentication standards on
wireless systems, and for corporate IT guys to realize that you can actually
get on their LAN from the parking lot.  It's amazing how many IT people are
completely ignorant of that fact.  I've been on many business trips where
the hotel Internet access is limited to dialup, but a good antenna hanging
out the hotel window will pickup someone's WAP and give you the use of
someone's T1 line to the Internet.  I've never tried, but I betcha on most
of these you could get into their corporate servers in a matter of minutes.

In fact, I helped a client move his business once, and we moved his WAP
system, only to discover several weeks later that their DSL line hadn't been
working the whole time, and they had been going out to the Internet on the
neighboring company's T1 through their WAP.  When we discovered this (by
accident), the owner actually considered continuing as it was.  They were
always curious why too many systems showed up in Network Neighborhood...

  

Reply via email to