From: Jim Laurino <nfcan.x.jimlaur@dfgh.net>
To: netfilter@lists.netfilter.org
Subject: Re: Vijay - port 25 to be blocked (nfcan: addressed to exclusive sender for this address)
Date: Tue, 28 Dec 2004 13:05:43 -0500 [thread overview]
Message-ID: <20041228180543.GA30059@salty> (raw)
In-Reply-To: <200412281624.iBSGOEHc027426@gourmet.spamgourmet.com> (from +nfcan+jimlaur+38cfe066fc.vijay#calsoftinc.com@spamgourmet.com on Tue, Dec 28, 2004 at 11:22:46 -0500)
On 2004.12.28 11:22, Vijay Kumar - vijay@calsoftinc.com wrote:
> Hi,
>
> I want to allow my internal network to only connect to some specific email
> servers.
> Apart from these mail server I want to block port 25 and 110 from my
> internal network to anywhwere. I am doing the following :
>
> iptables -I INPUT -I eth0 --dport 25 -d !<ip addr of mail server> -j
> REJECT
>
> This does not seem to block the port 25 traffic. Where am I going wrong?
The INPUT rules only apply to packets destined for the firewall computer.
Try this in FORWARD instead.
Another thing, a default drop policy might be simpler to administer.
Then only specifically allowed packets would be forwarded.
This approach more closely matches your intention, stated above.
Also, the approach above is hard to extend to multiple mail servers.
If you do this though, it is a good idea to log unexpected dropped
packets and analyze them to see what is being blocked.
>
> Kindly help.
>
> Regards,
> Vijay Kumar
>
--
Jim Laurino
nfcan.x.jimlaur@dfgh.net
Please reply to the list.
Only mail from the listserver reaches this address.
parent reply other threads:[~2004-12-28 18:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200412281624.iBSGOEHc027426@gourmet.spamgourmet.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041228180543.GA30059@salty \
--to=nfcan.x.jimlaur@dfgh.net \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox