CMS Made Simple SUX!

[unknown]

Greetings,
OK, Now that I have your attention. I thought you should be aware that the CMS Made Simple
addresses (IP's) are all blacklisted! What does this mean, you ask? Specifically;
anyone interested in subscribing to these Forums (for example) whom are running/using
a reasonably large MX, or is being operated by a seasoned Postmaster, will NOT be
able to subscribe. As the IP list that cmsmadesimple uses is NOT owned, or managed
properly by CMS Made Simple. As such, the netblock which CMS Made Simple is on is considered
UNtrustworthy and listed in most (if not all) the RBL's (Remote Block/Black Lists) around the
world.
I have been administering domains since 1975 (yes, I did say 1975). At this time,
I am responsible for 74k (75 thousand) Domains and all the traffic/headaches they bring.
Because of this, I am fortunate(?), as I was able to turn the RBL feature off long enough to
obtain the "activation code".

To those managing the CMS Made Simple operations:
The following information should prove useful to you. The rejection notice follows:

Code: Select all

NOQUEUE: connect from 131.85.232.72.static.reverse.ltdomains.com [72.232.85.131] (may be forged)
dns 131.85.232.72.no-more-funn.moensted.dk. => 127.0.0.3
ruleset=check_relay, arg1=[72.232.85.131], arg2=127.0.0.3, relay=131.85.232.72.static.reverse.ltdomains.com [72.232.85.131] (may be forged), reject=550 5.7.1 Mail from 72.232.85.131 REFUSED! See http://moensted.dk/spam/no-more-funn/?addr=72.232.85.131

It should also interest you to know, that I took the liberty of Whitelisting you with this particular RBL.
BUT, this should ring an alarm to you that further investigation in this area must be performed.

As I stated, I only whitelisted the IP 72.232.85.131. I have no idea (or interest) in any other IP's you
may be attempting to manage/use. Nor do I have the time to investigate any further. Because, as you
might imagine, I already have more than enough responsibilities.

BTW: Sending your web client to:
http://moensted.dk/spam/no-more-funn/?a ... 232.85.131 or any other IP will reveal more information.

Best wishes.

[kermit]

Whoa.. cool down a bit.. perhaps to a mellow simmer.

Why were YOU rejecting mail from an IP based only on an entry in the somewhat obscure "nomorefunn" list, or the ONLY list I found the IP in, backscatter... use a more prominent list that is less prone to error when rejecting mail outright; or require multiple listings when including these 'other' lists. it's YOUR overly aggressive configuration that is to blame here, NOT CMS Made Simple.

The IP address is part of Layered Tech; one of the bigger server providers out there. Wishy cannot control what others within Layered Tech's address space do on their own servers and IPs; and the IP was likely either lumped-together with an entire /24 or something, or 'nomorefunn' simply copied the entry from 'backscatter' (which has nothing to do with sending SPAM).

"listed in most (if not all) the RBL's" is NOT TRUE; A current check at DNS Stuff shows ONE listing, that of 'backscatter'... and it is impossible for an IP to be delisted from "most (if not all) the RBL's" in the (less than) two days between your post and now.... so were you maybe just over-exaggerating during your bout of frustration?

[unknown]

Greetings,
Hey, just to clear things up; I was not the least "up tight" about the situation at all. cmsmadesimple.org
network administration is of no concern to me. I only mentioned it, as I felt that it might me of interest for
CMSMS & Co. to know that some "would-be" users of CMSMS might become quite frustrated attempting
to seek support, or ask questions about CMSMS in these forums. Because they would never receive
the "activation email". Frankly, speaking for myself, I could have acknowledged that the "activation email"
bounced and have done nothing, and I'd have been no worse because of it. But. Like I said, I thought
CMSMS might want to know. As it affects them, not me.

As for your assertion that I am using an "obscure" RBL; fact is I've been using 6 RBL's for the past 7yrs. and
have been providing 1 for 2. In that 7yrs. our servers have not lost/rejected one single valid email - not one.
Unless of course, you want to count the "activation email" from CMSMS. But if you do wish to count it,
please consider the fact that I did discover and reconcile the situation, and nothing lost but time. I'd
say that given some 250k email accounts without loss of valid email is a pretty impressive record. So
from my standpoint; I should change nothing. Like they say - If it ain't broke, don't fix it..

Indeed, Layered Tech is a widely used provider. Their policy is fairly relaxed. Which has been a large factor
in making them popular. Unfortunately for other network providers, this leads to volumes of undesirable
activity on our networks. I/we receive no less than 3 per day from their network. Layered Tech, and 2 other
networks (whom shall remain nameless) created so much email abuse that I felt compelled to create a
script that target the type(s) of behavior and pulled the offending IP and added it to a "blacklist". So that
all future attempts to send email from the offending IP will immediately be sent REJECT.
Did I complain about it? Sure I did. Did I send them evidence? Sure. I sent them volumes of log entries
of just the offenses from their network. I'm hopeful they followed through. But given the shear number
of continuing offenses, it became highly impractical for me to continue "baby sitting" their
customers. It's not like I was on their payrole. Besides, I have my own network/customers to babysit.
Hence the blacklist script.

no-more-funn.moensted.dk, as I mentioned placed Layered Tech's IP block in the blacklist because
of many complaints from ppl recieving spam from the block. Because of the shear volume, it appeared
to them that the netblock was not enforcing a TOS, or was quite possibly owned by a "SPAM friend". So
the policy they chose was to blacklist the entire netblock and allow individual IP's to become whitelisted
(as I did with cmamadesimple.org). The policy was not unreasonable, but of course could lead to
"false positives". On the other hand, anyone managing an MX should always be on the lookout for
being erroneously placed in an RBL anyway. It's not terribly uncommon.

The IP became whitelisted in less than 12hrs. from the time I whitelisted it at no-more-funn.moensted.dk.
That's a fact. DNSStuff is a darned poor choice for retrieving accurate (timely) information in this regard.
They have convenient tools. But in this case, a check against your own DNS would have given you far
more accurate results. eg; dig @black.list. .in-addr.arpa. as just one example.

Anyway, I wasn't the least bit up-tight. I'm sorry should I have appeared that way. But rest assured, I
was not.

Best wishes.

[streever]

Hey,

posting that the system "SUX" in big letters, then bolding/etc and saying how bad it is?? makes you sound uptight.

You implied that the people on the project know nothing because--gasp--they are using shared hosting.

Oh well, that's the breaks, man. Sometimes your hosting company does something bad. Sorry that we aren't all spending 200 bucks a month on some dedicated solution?

I really think it'd be reasonable & appropriate for you to change the subject of this... I don't think it's an appropriate post to be forever in google.