All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Timothy Earl" <mehimx@gmail.com>
To: netfilter@lists.netfilter.org
Subject: TR: Redirecting mail
Date: Fri, 8 Apr 2005 13:50:41 +0200	[thread overview]
Message-ID: <42567013.37e18d74.4d3a.3b90@mx.gmail.com> (raw)

Forgot to send to list...

> -----Message d'origine-----
> De : Timothy Earl [mailto:mehimx@gmail.com]
> Envoyé : vendredi 8 avril 2005 13:48
> À : 'Ilo Lorusso'
> Objet : RE: Redirecting mail
> 
> Hi,
> 
> iptables v1.2.5: Unknown arg `--dports'
> 
> changes --dports to --dport when not using multiport...
> 
> Regards,
> 
> Tim
> > -----Message d'origine-----
> > De : netfilter-bounces@lists.netfilter.org [mailto:netfilter-
> > bounces@lists.netfilter.org] De la part de Ilo Lorusso
> > Envoyé : vendredi 8 avril 2005 13:38
> > À : Rob Sterenborg
> > Cc : netfilter@lists.netfilter.org
> > Objet : Re: Redirecting mail
> >
> > > The networks seem to be connected, so can't you just configure a
> > > smtp-forwarder in your MTA configuration ? That would be easier I
> think.
> >
> > I'd prefer just using iptables, so i can redirect when i need to..
> >
> >
> >
> > > There is no need to use multiport because you only DNAT 1 port : smtp.
> > > But that should not be a problem.
> > >
> > > iptables -t nat -A OUTPUT -p tcp --dports smtp \
> > > -j DNAT --to-destination 192.168.12.56
> >
> >
> > if I try it without the multiport option i get the following error..
> >
> > [root@posjia0h01 root]# iptables -t nat -A OUTPUT -p tcp --dports smtp -
> j
> > DNAT --to-destination 192.168.12.56
> > iptables v1.2.5: Unknown arg `--dports'
> > Try `iptables -h' or 'iptables --help' for more information.
> >
> >
> >
> > And no I dont have any rules blocking this from working as shown below,
> > but
> > would i need any iptables rules to make it work maybe? (like enable
> > ipforwarding and maybe a forward rule, im not sure)
> >
> >
> >
> > [root@prxsaa0z02 root]# iptables -L
> > Chain INPUT (policy ACCEPT)
> > target     prot opt source               destination
> >
> > Chain FORWARD (policy ACCEPT)
> > target     prot opt source               destination
> >
> > Chain OUTPUT (policy ACCEPT)
> > target     prot opt source               destination
> > [root@prxsaa0z02 root]# iptables -L -t nat
> > Chain PREROUTING (policy ACCEPT)
> > target     prot opt source               destination
> >
> > Chain POSTROUTING (policy ACCEPT)
> > target     prot opt source               destination
> >
> > Chain OUTPUT (policy ACCEPT)
> > target     prot opt source               destination




                 reply	other threads:[~2005-04-08 11:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=42567013.37e18d74.4d3a.3b90@mx.gmail.com \
    --to=mehimx@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.