I have considerable experience running SMTP servers (Postfix), and I =
problem with having 1600 hosts. =C2=A0I understand that these hosts w=
spread out among your 3-8 mail servers, so the number of hosts served=
be about 200 per SMTP server. =C2=A0What might be a worry is the fact=
normally send bulk email. =C2=A0You may want to ask your customers to=
bulk mail at certain times, to avoid overload.
This is what may be causing the confusion. The point of the exercise
is actually for each client to be able to send with their own IP 24/7
with no downtime. If a public IP is tied to a physical MTA machine
then if you want to take that machine offline for maintenance (or it
goes offline without you wanting!), the IP can no longer send. If you
have 200 customers on an MTA, then that's 200 customers that can't
send while you are doing maintenance. And if all 200 customers decide
to send at the same time then our poor MTA will not be happy, and
neither will the client whose newsletter takes 15 hours to send! Yes,
it is possible to move IPs, but there are ARP cache problems and this
is most definitely not HA (you have to move queues, etc.). There is
also bonding or any number of other HA solutions but I'll bet trying
to do that with MTA software and many machines is much more
problematic than doing it with just one or two failover FW machines.
It seems relatively easy to cluster iptables for HA with conntrack and
other tools, so FW uptime can be assured easily (and cheaply) that
way. It is also vastly preferable not to have machines directly
accessible from the internet, meaning there will be some sort of
firewall (transparent proxy) anyway. NATing seemed to me to be a
pretty good way of being able to do maintenance at reasonable times of
the day (like a Monday morning at 10am instead of Monday morning at
2am) and add/remove capacity, etc. Clients never, ever like downtime,
that is a given I think. They also don't like being told "you need to
send starting from 1am" - their research has shown them that their
subscribers want their emails at 10:30am (or whatever), so if we can't
send at that time then a competitor will... The idea is to provide a
secure, robust, flexible platform with (almost) no downtime and
without costing many hundreds of thousands of $$$.
So nothing really nefarious here except liking sleep and wanting to do
things with FOSS as much as possible (and saving money)...
In a nutshell, one client =3D one IP =3D one reputation =3D many MTAs (=
redundancy and capacity and for no other reason) is the goal.
If you set up your machines as relays, Postfix and other MTAs will wr=
public IP of the sender into each email in the first "Received" line.=
the receiving ISPs can check the reputation of each sender IP. =C2=A0=
your goal ("...newsletters from an IP that is used by only ONE client=
agree, this is how it should be."), that's the proper way to do it. =C2=
customers would each require only an email client running on a regula=
not a full-fledged mail server as you imply. =C2=A0I'm sure that plen=
ty of email
clients suitable for sending bulk email are available.
However, I don't think you want those public IPs in the bulk emails, =
on the link you sent
=C2=A0The whole idea of that service, which you pointed out as an exa=
mple of your
own, is to circumvent the time-consuming process of building an IP's =
reputation by sending it from another, "trusted" IP. =C2=A0Isn't that=
trying to do?
Nope, see above.
Of course, this mailing list is not the place to debate this.
Since SNAT is done in the POSTROUTING chain, you can't use SNAT to tr=
remove evidence of your customers' public IPs from mail sent on the *=
machine that does the SNAT. =C2=A0Even if you use a NATting router to=
email to mail servers running on other machines, the MTAs will know t=
origin IP and will ignore the NAT IP when they write the mail header.
Hiding the true sender IP is a violation of protocol. =C2=A0One way t=
protocol is to do something like remove the Received header that cont=
your sender's public IP. =C2=A0That can easily be done, but I won't g=
:-). That is most certainly not the idea at all! The idea IS to have a
big black box that sends newsletters - no one cares whether the actual
physical machine that generates an email is the one that queues it for
sending, or whether an IP points to a firewall machine or a physical
MTA. The "true" sender IPs are fully referenced in the whois database
with full contact details, including physical company address and
contact phone numbers. No one wants to hide anything. Email addresses
included in the whois databases are regularly checked and any
complaints are dealt with promptly and seriously. Any of our clients
who do not comply with the various anti-spam laws or our much stricter
terms of service are immediately cut off and contracts nulled. That is
the only way to have good working relationships with the ISPs - we get
called by postmasters "client X is causing complaints, get rid of
them", not blocked like what happens to some irresponsible industry
players. Transparancy and openness is the only way forward for email
marketing, and the only way to maintain good relations with the
receivers. ISPs don't want a sender (one "end client" of ours) using
lots of different IPs. They also prefer to have a single sender on an
IP if possible - that makes it much easier for them to classify and
filter if necessary. The best way to make sure newsletters get
accepted into subscribers' inboxes is to do what the ISPs/MSPs want.
ISPs/MSPs want their users to be happy, which means receiving the
newsletters they subscribe to in their inboxes and putting the spam in
the spam folder (or not at all). That is what we want to - it is a
sustainable and responsible business and has a future.
As for limiting access to the spoofing mail server to your network ra=
that's not necessary since your relaying mail servers will require
iptables -A INPUT -p tcp -m state --state NEW -s x.x.x.x/23 -j ALLOW
I think you will need this (one rule only) to allow email negotiation=
iptables -A INPUT -p tcp -m state --state ESTABLISHED,RELATED -j ALLO=
iptables -P INPUT DROP
Thanks for the tips, particularly on the LAN-local sending IP in the
headers, I had forgotten about that... and it will need to be replaced
with the clients' dedicated public IPs when it leaves the FW. That
might be a job for a netfilter module?
ps. Sorry about the dancing email "anton at linux dot com" and the
gmail. I thought I'd finally use my linux.com address (support the
cause!) but gmail defaults to my default address for replies and I
missed it. What I don't understand is why the list accepted my gmail
address when I subscribed with @linux.com...
To unsubscribe from this list: send the line "unsubscribe netfilter" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html