From: Georgi Alexandrov <tehlists@hotpop.com>
To: netfilter@lists.netfilter.org
Subject: Re: POP3 (Port No. 110)
Date: Tue, 31 May 2005 10:59:40 +0300 [thread overview]
Message-ID: <429C196C.8080303@hotpop.com> (raw)
In-Reply-To: <429C0D3A.9060703@riverviewtech.net>
Taylor, Grant wrote:
>> I have Sendmail configured on my server and I am able to send and
>> receive mails in the intranet. Now I want to be able to access the
>> mails from outside world also but i dont want to open the port for
>> every one. I want to open the pop3 port for the perticular IP (it may
>> be static or dynamic IP) in the IPTABLES and close the port when not
>> needed to access from outside.
>>
>> Please some one tell me how to do this and can I have some script
>> which will open the port when i need and close when not needed so that
>> I don't have to enter into the iptables every time.
>>
>> How to open the pop3 port for a perticular external ipaddress
>
>
> Presuming that you are not filtering on output it is easy to allow a
> specific IP access to your POP3 server.
>
> iptables -t filter -A INPUT -s ! ${known_external_ip_address} -p tcp
> --dport 110 -j DROP
>
> This will drop any traffic that comes to port 110 that is not from the
> known external ip address.
>
> If you are wanting more help setting up a script to manage this for
> you such that you can say pop_open and / or pop_close let me know and
> I'll see what I can whip up.
>
>
>
> Grant. . . .
>
>
I think he is talking about port knocker.
"iptables -t filter -A INPUT -s ! ${known_external_ip_address} -p tcp
--dport 110 -j DROP "
that rule is heavily dependant on his chain policies. E.g. if he has
DROP policy on the INPUT chain (-t filter) that rule won't help much as
${known_external_ip_address} will continue traversing the rules until it
hits the DROP policy.
georgi ...
georgi
prev parent reply other threads:[~2005-05-31 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-31 6:39 POP3 (Port No. 110) Vinod H
2005-05-31 7:07 ` Taylor, Grant
2005-05-31 7:59 ` Georgi Alexandrov [this message]
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=429C196C.8080303@hotpop.com \
--to=tehlists@hotpop.com \
--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