On Mon, Mar 15, 2004, Mike's List wrote: > On Mon, 15 Mar 2004, Michael Schloh von Bennewitz wrote: >>On Mon, Mar 15, 2004, Mike's List wrote: >>> Is is a postfix problem (doesn't seems like it) or PINE problem or >>> something else I need to explore. I test my ports by telneting to that >>> particular port and use nmap. Thanks. >>> >> I suggest you install the package 'netcat' and use it as a fake server to >> see what pine is sending out the wire. Once you've installed netcat, stop >> the postfix server and use telnet to test that the SMTP port is indeed >> closed. Then start netcat in server mode (something like 'nc -l 192.168.2.3 >> -p 25') and send a message from pine in another terminal window. You should >> see SMTP opcodes echoed out by netcat. If you suspect that netcat is not >> doing its job, then just telnet to it as before and type anything at all >> into the connection. >> > I keep getting "Invalid port -port: Invalid argument" when executing > "nc -l 192.168.2.5 -p 25" I stopped postfix and cannot telnet to the > port as expected. > The example netcat command I suggested was just a rough estimate taken from memory. Here is a more exact suggestion:
echo 'Some fake SMTP Banner' | nc -l -p 25 Now run pine in another terminal window and send an email normally. I'm not sure how pine works, but I would expect that it just pipes its message data to the local sendmail program and doesn't ever connect to port 25 on the localhost. I don't know, I'll leave it up to you to learn how to use pine. The scheme I just mentioned is what the MUA called mutt does. In any case if pine does indeed try to connect to port 25 on the localhost, then your netcat server will reply, echoing all the junk that pine sends to it. It's a rather good way to troubleshoot client connections. -- [EMAIL PROTECTED] Development Team, Operations Northern Europe Cable & Wireless Telecommunications Services
pgp00000.pgp
Description: PGP signature
