From: Ray Leach <raymondl@knowledgefactory.co.za>
To: "Netfilter Mailing List (E-mail)" <netfilter@lists.netfilter.org>
Subject: Re: pop3 and dns
Date: Tue, 04 May 2004 11:40:47 +0200 [thread overview]
Message-ID: <1083663647.1481.59.camel@raylinux.internal> (raw)
In-Reply-To: <F22386C3FEB012449238672E38ED61E706C2D5@overlord.overturemedia.com>
[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]
On Tue, 2004-05-04 at 11:40, Fritz Mesedilla wrote:
> Greetings!
> I have been looking for the answer to this through google...
>
> How do I allow POP3 through my iptables rules?
>
> I have done this...
> $IPTABLES -A FORWARD -p tcp --dport 53 -j ACCEPT
> $IPTABLES -A FORWARD -p udp --dport 53 -j ACCEPT
>
> $IPTABLES -A FORWARD -p tcp --dport 110 -j ACCEPT
>
> I included the dns forward rule to allow the internal clients to be able to resolve pop3 domain names.
>
> The problems:
> 1) They still can't resolve domain names.
> 2) POP3 can't seem to pass through going outside from the internal clients.
>
> Please advise me to what I still need to add. Thanks.
>
From what you show above, it's difficult to say. Are you using nat and
private ips on the inside? Are you just forwarding all traffic via your
iptables router and all your clients have public ips? Are you using
private ips on the inside and doing nat at the router?
> Cheers,
>
> fritz <www.mesedilla.com>
> ---
> + Basta Ikaw Lord
>
>
>
> ----------------------------------------------------------------------
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the sender immediately by e-mail and delete this e-mail from your
> system. Please note that any views or opinions presented in this
> email are solely those of the author and do not necessarily represent
> those of the company. Finally, the recipient should check this email
> and any attachments for the presence of viruses. The company accepts
> no liability for any damage caused by any virus transmitted by this
> email.
>
> Overture Media, Inc.
> Direct Line: (632) 635-4785
> Trunkline: (632) 631-8971 Local 146
> Fax: (632) 637-2206
> Level 1 Summit Media Offices, Robinsons Galleria EDSA Cor. Ortigas Ave., Quezon City 1100
--
--
Raymond Leach <raymondl@knowledgefactory.co.za>
Network Support Specialist
http://www.knowledgefactory.co.za
"lynx -source http://www.rchq.co.za/raymondl.asc | gpg --import"
Key fingerprint = 7209 A695 9EE0 E971 A9AD 00EE 8757 EE47 F06F FB28
--
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-05-04 9:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-04 9:40 pop3 and dns Fritz Mesedilla
2004-05-04 9:40 ` Ray Leach [this message]
2004-05-04 10:09 ` Antony Stone
2004-05-11 13:37 ` Peter Marshall
2004-05-12 4:22 ` Alexander Samad
2004-05-12 7:15 ` Ray Leach
2004-05-12 19:14 ` Dana Bourgeois
2004-05-12 19:34 ` Cedric Blancher
2004-05-12 21:21 ` Dick St.Peters
-- strict thread matches above, loose matches on Subject: below --
2004-05-05 4:42 Fritz Mesedilla
2004-05-05 4:58 Fritz Mesedilla
2004-05-05 10:24 ` Antony Stone
2004-05-05 12:30 ` Alistair Tonner
2004-05-07 5:21 Fritz Mesedilla
2004-05-13 1:40 cldavis
2004-05-13 23:49 ` Mark E. Donaldson
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=1083663647.1481.59.camel@raylinux.internal \
--to=raymondl@knowledgefactory.co.za \
--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