|
|||||||||
|
|||||||||
| |||||||||
|
|
|
| |||||||||
 |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
Dev Shed Forums Sponsor:
|
|
Stop making mediocre tutorials.The best tutorials are video! Camtasia Studio makes it easy to create engaging, buzz-building screen videos at any size, in any popular format. Download the free trial!
|
|
#1
April 25th, 2008, 11:08 PM
|
|||
|
|||
|
Mail Server Problem? Port Blocked?
I wanted to ask this here because whenever I post questions to the Qmail list I subscribe to, I get mercilessly slapped around like the mail server noob I am... And this probably isn't a mail server question anyway.
Today and about noon, my email reader (Thunderbird) started having problems connecting to my mail server, which is a basic Qmail install. The error was: "Unable to connect. Connection Refused" I haven't done anything with my firewall, and I have a Business Account that allows me to run a mail server. And, I can still access the mail server via webmail (in this case, SquirrellMail), so IMAP is alive and well. When I log in and telnet localhost 110, everything seems fine: Quote:
So with all that I've said, does it seem reasonable to assume that Qmail is functioning but that port 110 is being blocked from the outside world?
|
|
#2
April 25th, 2008, 11:37 PM
|
||||
|
||||
|
Quote:
If you can log in with one client and not another, it's probably not a port block issue. But my question is that you mention using Squirrelmail for IMAP... Port 110 is for POP, not IMAP. Port 143 is IMAP. What protocol are you using in Thunderbird? If POP, try using IMAP instead. What OS are you running?
|
|
#3
April 25th, 2008, 11:51 PM
|
|||
|
|||
|
Quote:
Squirrelmail (webmail) uses IMAP (port 143). I can get to my mail with Squirrelmail, no problem. So, port 143 is open to the the web server running SquirrelMail. And this tells me that Qmail is working. Thunderbird, of course uses POP3 (port 110). Not connecting. Yet, as you can see from the quoted snip above, when I telnet into the server and access port 110, I can connect. HOWEVER, when I open a CMD window on my desktop here at home and try to telnet xxx.xxx.xxx.xxx 110 or telnet xxx.com 110, or as I said try to connect with Thunderbird, it's no-go. I think this tells me that something (not my machine) is blocking 110 (my ISP?) Last edited by Weekend Coder : April 25th, 2008 at 11:55 PM.
|
|
#4
April 25th, 2008, 11:56 PM
|
||||
|
||||
|
Quote:
Yes... I'm assuming port 110 is opened in any firewalls and forwarded in any routers?
|
|
#5
April 26th, 2008, 12:19 AM
|
|||
|
|||
|
The thing is, I can still receive and send mail. I just have to do it with the webmail (which runs off the same machine). But if I send myself something from, say, Gmail, I get it. So port 25 must be open.
I can use nmap to see what ports are open / closed. I'll have to read up on how to do that... [EDIT] Well, I think I've answered my question. Code:
Starting nmap V. 3.00 ( www.insecure.org/nmap/ ) Interesting ports on localhost.localdomain (127.0.0.1): (The 1587 ports scanned but not shown below are in state: closed) Port State Service 21/tcp open ftp 22/tcp open ssh 25/tcp open smtp 80/tcp open http 106/tcp open pop3pw 110/tcp open pop-3 111/tcp open sunrpc 143/tcp open imap2 443/tcp open https 631/tcp open ipp 783/tcp open hp-alarm-mgr 993/tcp open imaps 3306/tcp open mysql 6000/tcp open X11 Last edited by Weekend Coder : April 26th, 2008 at 12:33 AM.
|
|
#6
April 27th, 2008, 08:49 PM
|
|||
|
|||
|
You can use grc.com to check what ports at your site are visible to the "outside world"
__________________
====== Doug G ====== "Hide, hide witch! The good folk come to burn thee. Their keen enjoyment hid behind their gothic mask of duty." -Mark Clifton
|
|
| Viewing: Dev Shed Forums > Operating Systems > Linux Help > Mail Server Problem? Port Blocked? |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
 |
|
|
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
