My understanding of iptables was it read top to bottom and you could either specify a default policy or the $iptables -A INPUT -j drop at the last line. To see if it would make any difference I removed the last line and instead specified a default policy of drop for all incoming packets then left the rest. I still get the same error message trying to log into squirrelmail.
Marc Powell mentioned: >Just a suggestion but instead of just guessing what iptables might be >doing why don't you reject and log? That way you'll know exactly what >it's seeing and can more easily determine why it's dropping the packets. I tried adding a -LOG rule and then testing it. I then searched the kern.log messages and syslog files and wasn't able to find anything in the logs from my ip to the linux box port 143 or 80. Perhaps you could show me the syntax you would use for testing. I may not have used the correct one. Any other suggestions are greatly appreciated. ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php -- squirrelmail-users mailing list Posting Guidelines: http://www.squirrelmail.org/wiki/MailingListPostingGuidelines List Address: [email protected] List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users
