Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Stephan Viljoen" <steph@gabswave.net>
To: 'IPTables Mailing List' <netfilter@lists.netfilter.org>
Subject: RE: Weird routing problem. (I think)
Date: Thu, 6 Nov 2003 16:44:36 +0200	[thread overview]
Message-ID: <004f01c3a474$7fc9a970$0200010a@Tinkerbell> (raw)
In-Reply-To: <1068129245.22285.1.camel@main.tqmcube.com>

It works 100% fine from outside of the network. I'm getting the problem
from some off my users on a private subnet. The thing that baffles me is
that they can connect to any other server on the same IP subnet as the
mail server with no problems.




-----Original Message-----
From: David C. Hart [mailto:DCH@TQMcube.com] 
Sent: Thursday, November 06, 2003 4:34 PM
To: Stephan Viljoen
Cc: Iptables Mailing List
Subject: Re: Weird routing problem. (I think)

On Thu, 2003-11-06 at 09:21, Stephan Viljoen wrote:
> Some off my clients started complaining that they're having problems
> connecting to my mail server. Now all this worked fine up until
> yesterday. I'm not blocking any ports nor am I blocking ICMP on the
> network.
> 
Rather slow but  . . . 

[root@mail2 root]# telnet 217.10.176.138 25
Trying 217.10.176.138...
Connected to 217.10.176.138.
Escape character is '^]'.
EHLO *****
220 gabswave.net ESMTP Exim 4.24 Thu, 06 Nov 2003 16:28:14 +0200
501 Syntactically invalid EHLO argument(s)
quit
221 gabswave.net closing connection
Connection closed by foreign host.




  parent reply	other threads:[~2003-11-06 14:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06 14:21 Weird routing problem. (I think) Stephan Viljoen
2003-11-06 14:34 ` David C. Hart
2003-11-06 14:43   ` Antony Stone
2003-11-06 14:44   ` Stephan Viljoen [this message]
2003-11-06 15:52 ` Ramin Dousti

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='004f01c3a474$7fc9a970$0200010a@Tinkerbell' \
    --to=steph@gabswave.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