On 6/27/2015 4:02 AM, Noel Butler wrote:
Although what you describe is a "workaround", the key is to keep your
house in order so you don't get listed, especially if you have not
actually fixed up the problem,
Oh Noel, why are you giving me fish in a barrel to shoot?
OK, now that you put your foot in it, please elaborate on how a
"house is kept in order" that will protect it from idiots. This is
going to be fun!
Oh and don't forget to define the difference between chronic offenders
and just regular people who get nailed for no reason.
DNBSBL's are just like local sys admins,
they get tired of adding in /32's after /32's for the same @$#holes,
thats when the /32's get removed and /24's get added, it wont take too
long to end up blocking all of your ranges. In fact since you've made
public your stance, it is likely anyone blocking your IP range, and
discovering its your service, may decide to block all of your IP ranges
first off to avoid wack-a-mole games.
Did it ever, possibly, occur to you that my 'workaround' wouldn't work
if someone has a chronic problem? Nor would it work if someone was just doing
it because they were too lazy to fix an open relay because
the backup IP would just instantly get RBLed again.
Why do you think I RECOMMENDED doing it? Do you think that _I_ want to
get spammed by the OP if he doesn't know WTF he is doing?
The beauty of my suggestion is if the OP is just going to try doing
it because he doesn't want to clean up his setup, it won't work.
Get it, now?
That's precisely why anyone out there reading this who is running an RBL
is going to ignore "my stance" as you put it.
They know that if I can defeat their RBL by simply switching IP's then
their RBL has a problem. Because, switching IPs is what snowshoe spammers do
every day and if they cannot block me switching an IP then
they cannot block them and their RBL isn't worth a bucket of hog slop.
Not many people I know have any faith in reputation services that try
"whitelist", but there are a tiny minority that apparently do, though
I've not known or in 25 years heard of, anyone getting blocked because
your using a new IP address on a system sending mail
Nor have I which is one of the primary reasons I thought that what
Reindl said about new IPs was a load of baloney.
(why should we care
if its a new IP, or a 20yo IP - whats more of interest to us is how new
your "domain" is, who your registrar is, what your authoritative NS's
are, thats where we spam score you, backing off a bit as days and weeks
go by), I'd be more concerned for the users of such a wacky reputation
service than the fact they might block a new IP of mine or whosever.
Agreed. Unfortunately, there ARE such wacky reputation service out there -
fortunately they are in the minority - and occasionally users will want to email
people who are using them and you have to know how
to get around those wacky services.
Ted
Given most medium and large networks use multiple servers for sending
customer mails, when the load balancers are showing the existing cluster
needs expanding, we add more into the cluster, so I cant see anyone
stupid enough to use a service blocking new IP's, if they do, they
deserve all the hell they bring upon themselves :)
On 27/06/2015 02:43, Ted Mittelstaedt wrote:
Heh Heh Heh Heh Heh
Since you and Charles have obviously never done this before why do you
feel qualified to comment?
Go ahead and not do this based on these logic castles you have built
that are not founded on any experience of reality. Your customers will
be suffering for a few days while you wait to get off a blacklist
while mine won't.
I have used this trick over many years while waiting for
AOL/Barracuda/etc. to pull their heads out on a de-list request. Of
course, adding a little sophistication in use helps. I ASSUMED I could
point you mules-heads in the right direction and you would use your
brains to figure out how to properly do this instead of figuring out
how to justify ass-sitting and not even trying it out.
But since your obviously too lazy to put any thought into the
technique, I don't see why I should waste my time elaborating any
further on it.
Jered, feel free to email me privately and I'll explain what you need to
do and how to set this up so that it works, if your interested.
Disgustedly,
Ted
On 6/23/2015 12:32 PM, Reindl Harald wrote:
Am 23.06.2015 um 21:28 schrieb Charles Sprickman:
One thing to keep in mind is that you may need to rotate your spare
IPs in now and then. Others can correct me, but my understanding is
that all the major email providers are going to treat an IP that
regularly sends email to them very differently than a "new" IP. You'd
essentially be starting to send from an IP that has no reputation (or
a reputation based on it's neighbors).
and *because* you have *no* reputation you will get a bad result if it
comes to greylisting and similar spam prevention by treat a completly
new IP as suspect and hence premature rotate IP's until something bad
happened is exactly what you should *not* do
