Thanks. Fortunately, the Exchange Server is behind a firewall with most of the inbound TCP/IP ports blocked....so I think our only vulnerability would be from within. Being a small organization, I'm not too terribly concerned about that. -----Original Message----- From: Jeffrey Robillard [mailto:jrobill@xxxxxxxxxxxxx] Sent: Thursday, January 24, 2002 8:42 AM To: [ExchangeList] Subject: [exchangelist] RE: Exchange Server 5.0 http://www.MSExchange.org/ If that exchange server has no inbound firewall rules blocking it then your probably already being spammed. Exchange 5.0 has no "authentication" functions relating to outbound mail. Thus, anybody that can see its IP address on the internet can use it to send mail to anybody and make it appear that it came from a totally different source. Having no DNS pointers to it doesn't matter because it can be targetted directly via IP. The only fix for this is to try and go around the problem with a duck-tape repair approach or get rid of problem and thus remove exchange 5. Exchange 5.5 and 2000 do not have this flaw. -----Original Message----- From: Chris Thompson [mailto:chris@xxxxxxxxxxxxxxxxxxxxxxxxx] Sent: Wednesday, January 23, 2002 5:02 PM To: [ExchangeList] Subject: [exchangelist] Exchange Server 5.0 http://www.MSExchange.org/ Hello, I recently inherited a small site with a single Exchange Server. The site is a small business and they had purchased Microsoft Exchange Server 5.0 way back in 1997 but never installed it. Last year, they hired a consultant to come in and upgrade the hardware on their single Windows NT 4.0 Server as well as install Exchange. For incoming Internet email, they're using a single POP3 account with a catch-all domain forwarding service to forward all emails for their domain to this POP3 account. On the server, they have an application running called POPCon, which retrieves all the email from this POP3 account, parses the headers looking for the intended recipient, and then hands off the email to the correct Exchange recipient via SMTP. For outgoing email, they're using the Exchange Server native SMTP services to relay all email to their ISP's SMTP servers for delivery. This is all being done over an ADSL line with a Hawking Router. What I'm looking for from any of you is the following: 1. Exchange Server 5.0, it's old and antiquated. However, the IT budget is virtually non-existent, so upgrades at this time isn't an option. Any suggestions on what I should do to ensure the stability and performance of my Exchange 5.0 Server? It seems MS stopped at Service Pack 2 for Exchange Server 5. 2. Is it possible to add a disclaimer to all outgoing email messages in Exchange Server 5 as I've seen posts illustrate for Exchange Server 5.5? Thanks in advance. Regards, Chris Thompson Chris Thompson Center Support Engineer Spirent Communications Email: chris.thompson@xxxxxxxxxxxxxx Cell: (925) 381-7964 Pager: 1-800-skytel2 (Pin: 1162761) ICQ: 142426425 | AIM: turlock_aviator ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: jrobill@xxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub') ------------------------------------------------------ You are currently subscribed to this MSExchange.org Discussion List as: chris@xxxxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')