Folks,

When I do the follwong query at my remote Redhat 9.0 server,


tcp 0 0 new_domain_name:imap *:* LISTEN 20027/couriertcpd
...
tcp 0 0 *:smtp *:* LISTEN 22769/

Now I am sure my SMTP server works fine, through telnet 25 port remotely

But for my imap server, I got connection refused when I telnet 143 port remotely,
even login in the remote server, and do a local telnet, I got the follwing:

telnet 127.0.0.1 25 - connection refused

telnet real_ip_addr 25 - it's just fine

So my questions is if I can manage to change

tcp 0 0 new_domain_name:imap *:* LISTEN 20027/couriertcpd

to

tcp 0 0 *:imap *:* LISTEN 20027/couriertcpd

Will that fix my problem? If yes, how can I?

Thx,
HTM

What IP does new_domain_name resolve to? How did you define it, in /etc/hosts, in DNS, how?
Did you remember to open 143/TCP through your firewall???

I am sure port 143 (imap) is open, since when
I do the following query at my remote Redhat 9.0 server,

tcp 0 0 fake_domain_name:imap *:* LISTEN 20027/couriertcpd
...
tcp 0 0 *:smtp *:* LISTEN 22769/

The fake_domain_name was there is because I set up impad before
I ask my ISP to bind my domain name (different to domain_name)
to my real IP address

So my questions is if I can manage to change

tcp 0 0 fake_domain_name:imap *:* LISTEN 20027/couriertcpd

to

tcp 0 0 *:imap *:* LISTEN 20027/couriertcpd

Will that fix my problem? If yes, how can I? - done in
imap( where to do), ask my ISP to put fake_domain_name through
DNS (not a good way to go) or edit or /etc/hsosts?


Thx,
HTM

Thx,
HTM

No, I mean open through your firewall. You can't tell if there's a hole through your firewall by using netstat! You need to use telnet to test the port remotely (143). Note that it's not the same to ssh from box 1 to box 2, then telnet (from your ssh session) to box 2, that will only test from box 2 to itself. You need to telnet from box 1 to box 2 on port 143 and see if you get the IMAP banner.

You still didn't answer where you mapped the domain name, I can't help you unless you tell me that. Also, use the -n flag to netstat so it doesn't resolve domain and hostnames, that would be much more helpful.

I suggest that if you want help, you should answer the questions that people ask you, instead of coming up with your own answers to different questions.

Yeah, I did try that as well remotely from my server in my LAN:

telnet real_ip_addr 143

Now if I do the same on port 25, it works

telnet real_ip_addr 25

I am suspecting that is because I could not go through

telnet 127.0.0.1 143 (but telnet real_ip_address 143 OK at the remote server)

The mapped domain name story is as follows:

The remote server was named temporailiy named new_domain.com before
I move my domain from hostway.com to my own remote server, and imap
was installed before the server was renamed from new_domain.com to domain.com,
how come imap record my old domain name? I am gathering that may cause
my local telnet 25 problem as well as remote telnet 25 problem?

Thx,
HTM


> No, I mean open through your firewall. You can't tell if there's a hole through your firewall by using netstat! You need to use telnet to test the port remotely (143). Note that it's not the same to ssh from box 1 to box 2, then telnet (from your ssh session) to box 2, that will only test from box 2 to itself. You need to telnet from box 1 to box 2 on port 143 and see if you get the IMAP banner.

> You still didn't answer where you mapped the domain name, I can't help you unless you tell me that. Also, use the -n flag to netstat so it doesn't resolve domain and hostnames, that would be much more helpful.

>I suggest that if you want help, you should answer the questions that people ask you, instead of coming up with your own answers to different questions.