WeMasterz5

Well-Known Member
Feb 24, 2003
360
0
166
Miami
but.... (hehe always a but eh? ) :p

I dont use outlook type email systems but I have some clients that do...one asked about using imap...I have read most of the post dated 2002 here in these forums with a search for imap settings..I have done just about all that everyone suggested...I tried using outlook set to imap and it would not connect...pop3 works fine...

can someone suggest something to maybe help me get this going

were on WHM 6.2.0 Cpanel 6.4.1-E31 RedHat 8.0

thanks
 

lhpnet

Member
Apr 27, 2003
20
0
151
It's likely that port port 143 is not open for imap connections.

vi /etc/sysconfig/iptables

add the line to ACCEPT connections on port 143 (you'll know what line to add when you're there) , remember it's udp not tcp protocol, udp does not use --syn either.

then:
/etc/init.d/iptables restart

ML
 

WeMasterz5

Well-Known Member
Feb 24, 2003
360
0
166
Miami
Thanks


vi /etc/sysconfig/iptables
I dont see that...

/etc/sysconfig/.iptables.swp

is what I see there

when running that..I get

E325: ATTENTION
Found a swap file by the name "/etc/sysconfig/.iptables.swp"
owned by: root dated: Thu May 8 17:22:27 2003
file name: /etc/sysconfig/iptables
modified: no
user name: root host name: bliss.cyberwirecafe.net
process ID: 15576 (still running)
While opening file "/etc/sysconfig/iptables"

(1) Another program may be editing the same file.
If this is the case, be careful not to end up with two
different instances of the same file when making changes.
Quit, or continue with caution.

(2) An edit session for this file crashed.
If this is the case, use ":recover" or "vim -r /etc/sysconfig/iptables"
to recover the changes (see ":help recovery").
If you did this already, delete the swap file "/etc/sysconfig/.iptables.swp"
to avoid this message.
"/etc/sysconfig/iptables" [New File]
Hit ENTER or type command to continue
 

lhpnet

Member
Apr 27, 2003
20
0
151
It's the swap file when you vi iptables the last time and got disconnected (quit without closing the file)

You need to recover that file for the firewall to work.
this is what /etc/iptables should have:
--------------------
# Firewall configuration written by lokkit
# Manual customization of this file is not recommended.
# Note: ifup-post will punch the current nameservers through the
# firewall; such entries will *not* be listed here.
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:RH-Lokkit-0-50-INPUT - [0:0]
-A INPUT -j RH-Lokkit-0-50-INPUT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 25 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 80 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 21 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 22 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 23 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p udp -m udp --dport 53 -j ACCEPT

-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 110 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 143 --syn -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p udp -m udp --dport 27015 -j ACCEPT

-A RH-Lokkit-0-50-INPUT -i lo -j ACCEPT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 0:1023 --syn -j REJECT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 2049 --syn -j REJECT
-A RH-Lokkit-0-50-INPUT -p udp -m udp --dport 0:1023 -j REJECT
-A RH-Lokkit-0-50-INPUT -p udp -m udp --dport 2049 -j REJECT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 6000:6009 --syn -j REJECT
-A RH-Lokkit-0-50-INPUT -p tcp -m tcp --dport 7100 --syn -j REJECT
COMMIT



----------------
nevermind, imap uses tcp protocol. :)

ML
 

WeMasterz5

Well-Known Member
Feb 24, 2003
360
0
166
Miami
ok...kinda worried about doing this...have never messed with the iptables...all the normal ports are open now...so putting this does what?


thanks
 

lhpnet

Member
Apr 27, 2003
20
0
151
It will open port 143 to accept connections for imap server.

Right now, on your box try :
telnet localhost 143
If you see something, try FROM HOME:
telnet <your IP> 143 see if you have the same.

If not work, it's because you don't have port 143 open (it's NOT open by default by cpanel).
You can try /etc/init.d/iptables stop and telnet (FROM HOME) again.
If it works, you can turn iptables back on and fix the config file. then restart iptables.

ML
 

WeMasterz5

Well-Known Member
Feb 24, 2003
360
0
166
Miami
* OK [capability imap4rev1 login-refeffals auth=login] bliss.####.net imap4rev1 2002.235-cpanel at todays date and time
 

lhpnet

Member
Apr 27, 2003
20
0
151
if you can telnet to your server port 143 FROM OUTSIDE then you don't need to change anything.

ML