On Fri, Mar 15, 2002 at 02:23:37PM -0800, Harry Putnam wrote: > > Did you make and adjustments to disallow any traffic from the internet > on 143? (Or I guess 110 in your case) I wondered how to make it so > only 192.XXX.XXX is allowed to connect to it. Or even so that it > isn't even seen from the internet. So a scan would not show it open > or running.
I've got a Linksys firewall between my Linux system and the outside world. The Linksys only passed a few pre-defined ports through (like 25 and 80). Everything is blocked by default. You could do the same thing using ipchains or similar. I believe you should be able to do in your xinetd.d config file. See http://www.xinetd.org/sample.shtml for a sample config that restricts access this way. > So, with imapd running and accounts with mail in them in > /var/spool/mail/$USER. A network computer with a setting of popserver > aimed at the linux box would press send/recieve or something and her > software would connect to port 143. The imapd would know what to do > from there, and handles the uid/passwd negotiation.. and pass out the > mail? > > Do there actually have to be user accounts on the machine, or just > a file in /var/spool/mail/$USER? You actually have to have a user account since that account is the only one that has access to the mail file. imapd/popd does the username/password negotiation, and the username doesn't exist, you're dead in the water. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
