Opening ports

Curtis Vaughan curtis at npc-usa.com
Fri Dec 17 10:52:04 PST 2004


Forget all my questions!
I was right. Postfix was choking on my access file (or the lack 
thereof). Once I got it fixed then postfix started working and 
listening on port 25.

Curtis

On 17 Dec, 2004, at 10:37, Lucas Holt wrote:

> Does courier-imap do smtp?  Sendmail doesn't listen for outside mail 
> by default, but in some cases it does listen on port 25 witout 
> accepting connections.  look at /etc/rc.conf and see what you have 
> enabled. (firewall, courier and sendmail related variables)
>
>
>
> On Fri, 17 Dec 2004, Curtis Vaughan wrote:
>
>>
>> On 17 Dec, 2004, at 09:24, Curtis Vaughan wrote:
>>
>>> I realized that apparently by default most all ports are closed on 
>>> my 5.3-Release box. The reason I say this is because besides port 
>>> 22, 80 and 10000 no other port seems to be open (based on a port 
>>> scan). I just installed postfix and courier-imap and wanted to test 
>>> ports 25 and 110, but they do not respond even though postfix is 
>>> running, I have enabled the ports in master.cf. Also they are in 
>>> /etc/services.
>>> Looking over documents and checking my install, /etc/rc.firewall is 
>>> not enabled in /etc/defaults/rc.conf.
>>> I assume I could go through rc.firewall and set it up for those 
>>> ports I need opened, and enable it in rc.conf, but whereas we have a 
>>> gatewall/firewall for our company, I don't see a lot of
>>> reason for having all the ports closed down on this server. Is there 
>>> an easy way to enable them all?
>>> Curtis
>>
>> OK, I've got courier-imap running now and it opened port 143, but 
>> there is still no reply on 25. Which makes me think that the problem 
>> isn't the fact that ports are closed, but that nothing is listening.
>> However, netstat shows:
>>
>> cod# netstat -na | grep LISTEN
>> tcp4       0      0  *.143                  *.*                    
>> LISTEN
>> tcp6       0      0  *.143                  *.*                    
>> LISTEN
>> tcp4       0      0  *.80                   *.*                    
>> LISTEN
>> tcp4       0      0  *.25                   *.*                    
>> LISTEN
>> tcp4       0      0  *.10000                *.*                    
>> LISTEN
>> tcp4       0      0  *.22                   *.*                    
>> LISTEN
>> tcp6       0      0  *.22                   *.*                    
>> LISTEN
>>
>> So, something is listening on port 25, but why no response to telnet 
>> requests?
>>
>> Curtis
>>
>> _______________________________________________
>> freebsd-questions at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to 
>> "freebsd-questions-unsubscribe at freebsd.org"
>>



More information about the freebsd-questions mailing list