----- Original Message ----- From: "Jesse Keating" <[EMAIL PROTECTED]> Sent: Tuesday, April 30, 2002 11:19 AM
> Do you have something like tripwire, or any other intrusion detection system? > Some of them bind them selves to your closed ports, and could have > accidentally > been configured to bind to 25. > Nothing is installed, and no errors exist on system.. Strange I tell you, I paused for a moment to do the following as root: /etc/rc.d/init.d/courier stop cd /home/courier/courier-0.37.3 make install /etc/rc.d/init.d/courier start I'll give you one guess as to what happened next :) a quick nmap tells me that port 25 is now open.. [root@pegasus courier-0.37.3]# telnet localhost 25 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 mail.holburn.com ESMTP Now the question is, can anyone explain to me why this would happen. I dont want to get too far off the courier topics but it seems a bit strange that it would just stop responding untill I reinstalled perhaps it's something hardware. What is your (The list's) choice in linux distro's? Anyone had experience with the promise controllers and linux? The machine is as follows: Red Hat 6.2 Kernel 2.2.14-5.0 PIII - 800EB Promise FT-2 IDE controller 2x40G IDE drives mirrored 512M RAM _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
