All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ralf Spenneberg <lists@spenneberg.org>
To: ads nat <adsnat@yahoo.com>
Cc: Netfilter <netfilter@lists.netfilter.org>
Subject: Re: SMTP HTTP problem
Date: 31 Aug 2003 09:41:54 +0200	[thread overview]
Message-ID: <1062315713.1607.6.camel@kermit> (raw)
In-Reply-To: <20030830143115.91071.qmail@web20705.mail.yahoo.com>

Hi,
Am Sam, 2003-08-30 um 16.31 schrieb ads nat:
> PROBLEM-1
> When I try to send email to squid emailing list I get
> following error.
> ****
> Hi. This is the qmail-send program at squid-cache.org.
> I'm afraid I wasn't able to deliver your message to
> the following 
> addresses.
> This is a permanent error; I've given up. Sorry it
> didn't work out.
> <squid-users@squid-cache.org>:
> ezmlm-reject: fatal: Sorry, I don't accept messages of
> MIME 
> Content-Type 'multipart/alternative' (#5.2.3)
Read the error message. Your email gets to the mailserver, but it did
not accept it! No netfilter issue!

> Also my LAN users can not send emails through outlook
> express.
Different story.

> STATUS:> Retrieving directory listing...
> COMMAND:> PORT 192,168,0,42,4,62
>  500 Illegal PORT command.
> STATUS:> Error opening data socket 
> *****
Did you load the inspection modules for ftp? ip_conntrack_ftp,
ip_nat_ftp?

Correct me if I am wrong, but your iptables script does not filter
anything, does it? Therefore you essentially do not have a firewall at
the moment which could block anything, do you?
Your Policy is ACCEPT and you do not have any DROP rules, only one NAT
rule. 

Cheers,

Ralf
-- 
Ralf Spenneberg
RHCE, RHCX

Book: Intrusion Detection für Linux Server   http://www.spenneberg.com
IPsec-Howto				     http://www.ipsec-howto.org
Honeynet Project Mirror:                     http://honeynet.spenneberg.org


      reply	other threads:[~2003-08-31  7:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-30 14:31 SMTP HTTP problem ads nat
2003-08-31  7:41 ` Ralf Spenneberg [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=1062315713.1607.6.camel@kermit \
    --to=lists@spenneberg.org \
    --cc=adsnat@yahoo.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.