Hi Oleg, Thanks for your help. My iptables rules were set to reject port 143. Problem solved.
Mark > Hello Mark, > I'm not sure but you can try to check ipchains or iptables. It's > possible that imap port is closed there. > > Mark Stanislawek wrote: >> Hi- >> >> I recently install courier-imap 1.7.1 and am having trouble connecting >> to imap remotely. I have searched through the archives of this list >> and haven't found a similar problem. I am wondering if this is >> something simple that I am missing. >> >> description: >> I can connect to imap locally (127... or FQDN), but I cannot connect >> to it remotely. (telnet to 143 from a remote host results in >> connection refused.) >> >> Here is my progress so far: >> >> 1. netstat -a | grep imap >> tcp 0 0 *:imaps *:* >> LISTEN tcp 0 0 *:imap *:* >> LISTEN unix 2 [ ACC ] STREAM LISTENING 81743 >> /var/run/authdaemon.courier-imap/socket.tmp >> >> 2. checked the startup script for couriertcpd and made sure it does >> not include any blocked addresses. >> >> 3. checked /etc/hosts.allow and /etc/hosts.deny. Both files are >> empty. >> >> 4. checked connections for for smtp and http remotely. I am able to >> connect to both remotely. >> >> Are there other things I should check to diagnose this problem? >> Thanks. >> >> >> >> >> ------------------------------------------------------- >> This sf.net email is sponsored by:ThinkGeek >> Welcome to geek heaven. >> http://thinkgeek.com/sf >> _______________________________________________ >> courier-users mailing list >> [EMAIL PROTECTED] >> Unsubscribe: >> https://lists.sourceforge.net/lists/listinfo/courier-users >> > > -- > Best regards. > > Oleg [EMAIL PROTECTED] > (nic-hdl) OKU11 > Fax: +1 801 749 3182 ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
