From: "Gáspár Lajos" <swifty@freemail.hu>
To: Thomas Jacob <jacob@internet24.de>
Cc: John Little <jlittle_97@yahoo.com>, netfilter@vger.kernel.org
Subject: Re: Using iptables with high volume mail
Date: Thu, 01 Oct 2009 18:40:51 +0200 [thread overview]
Message-ID: <4AC4DB93.6060707@freemail.hu> (raw)
In-Reply-To: <1254412984.11386.63.camel@enterprise.ims-firmen.de>
Thomas Jacob írta:
> This all really depends on the number of new connections and packets per
> time, rather than the number of emails.
>
Agree.
But I would also check the upstream bandwidth and concurrent connections
per time or per destination.
Swifty
next prev parent reply other threads:[~2009-10-01 16:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 11:42 Using iptables with high volume mail John Little
2009-10-01 11:54 ` Richard Horton
2009-10-01 12:45 ` John Little
2009-10-01 16:03 ` Thomas Jacob
2009-10-01 16:40 ` Gáspár Lajos [this message]
2009-10-01 19:39 ` John Little
2009-10-02 12:31 ` Thomas Jacob
2009-10-02 13:50 ` John Little
2009-10-02 14:52 ` Thomas Jacob
2009-10-02 15:08 ` Michele Petrazzo - Unipex
2009-10-02 19:04 ` John Little
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=4AC4DB93.6060707@freemail.hu \
--to=swifty@freemail.hu \
--cc=jacob@internet24.de \
--cc=jlittle_97@yahoo.com \
--cc=netfilter@vger.kernel.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