Hello All,
I am still trying to figure out why smtp/pop3 requests take so long
to respond or process when users try to send/retrieve mail off of the
server...
Machine Specs:
Pent-133, 32MB, 1.6GB HD, CD-ROM, 2 Intel EEPro NIC's
eth0 has static class C IP address connected to D-Link Switch
for internet access (Cisco 4700 router with T-1 connected)
eth1 has private ip address of 192.168.3.1 which several machines
go thru to get internet access via IP chains (No problems observed)
Distro is OpenLinux 2.2 (Caldera) with latest security RPM updates
tcp.smtp.cdb allows 127.0.0.1, 192.168.3. and 192.168.2., and any
machine assigned to our class C...The lan segment also has IPX/SPX
traffic on it as we use Novell 3.12 for a file server...
Machine runs caching DNS on port 53 (no problems observed)
Machine runs ssh 1.2.2x on port 22 (no problems from work or home)
Ipchains in rc.local looks like this:
/sbin/ipchains -P forward DENY
/sbin/ipchains -A forward -j MASQ -s 192.168.3.0/24 -d 0.0.0.0/0
other commands in rc.local (before above lines) are:
/sbin/ifconfig eth1 192.168.3.1 netmask 255.255.255.0 up
# enable ip forwarding
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/tcp_syncookies
Here are the start lines for qmail script in init.d
start)
echo -n "Starting: "
env - PATH="/var/qmail/bin:/usr/local/bin" \
qmail-start ./Maildir/ /usr/local/bin/accustamp \
| /usr/local/bin/setuser qmaill /usr/local/bin/cyclog /var/log/qmail &
echo -n "qmail "
env - PATH="/var/qmail/bin:/usr/local/bin" \
tcpserver -H -R -c100 0 pop-3 /var/qmail/bin/qmail-popup \
nermal.xxxxx.com \
/home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir &
echo -n "pop3 "
env - PATH="/var/qmail/bin:/usr/local/bin" \
tcpserver -H -R -x /etc/tcp.smtp.cdb -c100 -u7791 -g2108 0 smtp \
/var/qmail/bin/qmail-smtpd 2>&1 > /dev/null &
echo "smtp"
;;
stop)
echo -n "stopping qmail"
killall qmail-send
killall tcpserver
echo
;;
Does anyone have any idea or clues why smtp/pop3d would take so
long to process...This used to work fine under a 2.0.36 >= kernel when
I ran OpenLinux 1.2 Base (what I mean by this is issuing send/receive
on OutLook Express or the same in Eudora Light ran in less than 5 seconds,
but now runs in anywhere from 3 seconds to a full minute in some cases)...
I'm going to cross-post this to the caldera list to see if anyone
there has any ideas (it's driving me and my users crazy, a little at a
time, so I have a woeful look on my face)...
-Bill