DavidT

Memberp
  • Content count

    2,395
  • Joined

  • Last visited

Community Reputation

0 Neutral

About DavidT

  • Rank
    Been There

Contact Methods

  • ICQ
    0
  1. ...and yet now, due most likely to false reporting (I've taken a look at the 90-day window of reports in the system), I'm seeing several sending IPs of MailChimp's servers on the SCBL. I just disabled all tests for the SCBL on my server, so at least the stuff I want won't be affected, but I run mailing lists for a number of non-profits, and their deliverability will be affected. In my experience, the SCBL is worthless (YMMV).
  2. ...and yet now, due most likely to false reporting, I'm seeing several sending IPs of MailChimp's servers on the SCBL. I just disabled all tests for the SCBL on my server, so at least the stuff I want won't be affected, but I run mailing lists for a number of non-profits, and their deliverability will be affected. In my experience, the SCBL is worthless.
  3. He will indeed be both rememered and missed.
  4. I used Constant Contact's services for about five years with several non-profits, but have moved on to MailChimp, as on any given day, a number of CC's outbound server IPs are listed on the SCBL, which caused deliverability problems. The links in commercially-broadcast emails are almost all encoded to give the senders useful tracking info about open rates, click-through rates, and list segment targeting. The reputable broadcast email providers take various measures to avoid harboring spammers, but as their lists aren't all double opt-in, customers who don't follow the rules can add purchased/harvested addresses and cause problems. DT
  5. I've heard good things about using Anti-spam SMTP Proxy (ASSP) to filter/block. I have a VPS with cPanel and my rbls + SpamAssassin just aren't doing the trick any more, so I'm looking at a third party who installs ASSP Deluxe onto cPanel/WHM setups to make my life easier. Here's the Wiki page on ASSP: http://en.wikipedia.org/wiki/Anti-Spam_SMTP_Proxy and the sourceforge link: http://sourceforge.net/projects/assp/ DT
  6. ...and that worked as well. I think you've managed to fix another of the most significant bugs here--thanks!
  7. It worked. Now post something to "Now is the time," which I've been trying to follow for a while. If that doesn't arrive, then either there's a problem with existing subscriptions and we'll all have to resubscribe to everything, or there's a problem with following/subscribing to a non-public forum.
  8. I received the test, and have just followed this topic, so we'll see. I'm very selective about which topics I follow, but haven't been receiving notifications on some that I'm sure I'm subscribed to (such as in Memberp). In my settings, I have the first four notification options set to email, including the most applicable: "Notification method to use for replies to followed topics"
  9. Thanks. I received my first notification of a "personal conversation" since the big move. I think that notifications about topics being followed are still broken, however.
  10. We appear to be pretty much on our own here, with Farelf fixing things that the folks in San Bruno should be taking care of and with the benevolent overlords not bothering to drop by here very much or to respond.
  11. The spamvertized URLs in those reports don't resolve to working websites. Perhaps action has been taken? Also, the primary purpose of SC is in dealing with the sources of email spam, not with spamvertized URLs. Looks like a lot of bogus info on the whois for reliefrecoverstrenght.link, which is something you can also use to have action taken. DT
  12. I'm a customer of NameCheap and found them to be both responsive and responsible. I'll need to see some very convincing evidence to think otherwise.
  13. The delete key? Sure, but the crap shouldn't have been allowed through in the first place. It was spammers who used to say "just hit delete" if you don't want our spam, so we shouldn't fall into that same mindset, IMO. And no, life is MUCH too short to spend what little time I have allowing the stuff through and then having to process it--better that it gets vaporized either before it hits my servers or the moment that it does. DT
  14. Control is good, and with adequate scripting, etc., someone who really knows what they're doing can safely utilize a "default" or "catch-all" address, but *only* under those circumstances. In the vast majority of cases, that function should most certainly *not* be turned on for the average domain owner. I'm quite certain that most people stopped allowing everything through many years ago. DT
  15. Please see Rule #3 of "The Rules of spam," to whit: "Spammers are stupid." http://www.pearlgates.net/nanae/rules_of_spam.shtml DT