From: Pete <pete@nrth.org>
To: netfilter@vger.kernel.org
Subject: Re: Advice on best way to set up multi-route NAT for lots of IPs
Date: Mon, 2 Jan 2012 18:01:15 +0000 [thread overview]
Message-ID: <20120102180115.GA17749@pusher.nrth.lab> (raw)
In-Reply-To: <op.v7fekow7x1lyi3@debiandesk2.net>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
On Sun, Jan 01, 2012 at 04:11:02PM -0600, Lloyd Standish wrote:
> On Sun, 01 Jan 2012 14:41:24 -0600, Anton Melser
> <melser.anton@gmail.com> wrote:
>
> Think Mailchimp just a little smaller. Lots of clients need lots
> > of IPs (it's a reputation thing, and quite an interesting computing
> > problem, see
> > http://blog.mailchimp.com/should-you-send-from-a-dedicated-ip-address/
> > or just search for "email marketing dedicated ip" for an intro).
[..]
>
> Frankly, this looks to me like bulk-email-laundering. That is, it's a
> way to convey email "reputation" from one of 3-8 "trusted" IPs to the
> 1600 "unknown" ones.
This discussion is very intriguing to myself, no matter how OT. I'm
quite sure I'm not the only one.
It sounds to me like someone needs help on how to hide a botnet using an
iptables script at first glance. It can't be that of course so why are
1600 hosts wanting to send bulk email ?
spam has given email marketing such a bad reputation that I'd really
like to know why there are 1600 hosts that need to send
business/marketing email. Why 1600 ?
Sorry I'm new to the list and I realise I am contributing to the
OT-ishness of this thread.
Regards,
Pete.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3952 bytes --]
next prev parent reply other threads:[~2012-01-02 18:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-01 16:10 Advice on best way to set up multi-route NAT for lots of IPs Anton Melser
2012-01-01 20:24 ` Lloyd Standish
2012-01-01 20:41 ` Anton Melser
2012-01-01 21:36 ` Anton Melser
2012-01-01 22:11 ` Lloyd Standish
2012-01-02 9:00 ` Anton Melser
2012-01-02 16:10 ` Lloyd Standish
2012-01-02 22:14 ` Anton Melser
2012-01-03 0:46 ` Lloyd Standish
2012-01-03 8:56 ` Anton Melser
2012-01-04 15:15 ` Anton Melser
2012-01-05 7:37 ` Andrew Beverley
2012-01-02 18:01 ` Pete [this message]
2012-01-02 21:14 ` Anton Melser
2012-01-02 12:38 ` Ed W
2012-01-02 13:17 ` Anton Melser
2012-01-27 23:54 ` Ed W
2012-01-05 7:35 ` Andrew Beverley
2012-01-05 8:15 ` Anton Melser
2012-01-05 17:06 ` Andrew Beverley
2012-01-05 18:39 ` Rob Sterenborg (Lists)
2012-01-06 5:15 ` Anton Melser
2012-01-06 7:28 ` Andrew Beverley
2012-01-05 8:59 ` Rob Sterenborg (lists)
2012-01-05 11:59 ` Anton Melser
2012-01-05 13:17 ` Rob Sterenborg (lists)
2012-01-05 16:59 ` Andrew Beverley
2012-01-05 17:08 ` Rob Sterenborg (lists)
2012-01-05 17:14 ` Andrew Beverley
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=20120102180115.GA17749@pusher.nrth.lab \
--to=pete@nrth.org \
--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;
as well as URLs for NNTP newsgroup(s).