Brian,

It's not the first time I've though of leaving. All CMS's have their strengths and weakneses. However, I've always felt the DNN interface was easiest for our clients to learn when changing their own websites. However, I can't keep doing this. Especially when there's no end in site. I got an email from the support manager at DnnSoftware saying he can't allow his support staff to continue helping me with the issue until I pay for support time. That, most of all, makes me want to leave. 

Paul, by my count at least half a dozen of our staff have been trying to help you, consuming something close to 30hrs in (free) support time. I myself have spent a number of hours examining your IIS logs and sending email responses - of my emails my last two (sent Tue 15/07/2014 22:56 &

Wed 16/07/2014 20:29) have yet to receive responses. I am confused as to your expectations of free support, and then when I offer it (as security team lead) you seem to not take advantage of it.

No one enjoys the situation that we are in at the minute, and we are working hard on resolutions towards it. Whilst a number of people have been affected (i.e. sites that offer public or verified registration), most have found the workarounds at http://www.dnnsoftware.com/community-... to be effective and allow them to continue working whilst we finalise a solution to this with the 7.3.2 release.

Paul,

I don't wish to criticize in public, but I'm still waiting on responses to both my mails. My first mail also did not suggest that module, but rather asked for what filtering you're using (e.g. ISAPI, urlrewrite module or IIS request filtering) - pleas re-read it and respond accordingly. In my second mail I confirmed that the logs you gave me do not show automated registration but rather returning spam users attempting to view their profile page - as I indicated in that mail a simple filter to map those requests to a 404 would block ~95% of that traffic. That said, the logs show that this site receives less than 10,000 page views a day which in real terms in not large so I am surprised that its affecting performance of that site much at all. Note: the logs are dropping in size rapidly suggesting that the spam requests are dropping naturally as they fail to log in.

If you could respond to one of my mails I will continue to try to help, but I would prefer if you would not post inaccurate information to try to drum up public controversy as that's coming dangerously close to trolling (e.g. you've stated on a mail to our support lead that you spend $25,000 a year at the dnnstore but now you've said you've made 200 purchases - you also say you've been doing DNN for 14 years (we've been going for 11) these figures do not correlate well. )

Note: DNN is free and open-source - there should be no expectation of free support. The fact that you have hundreds of (paying) clients, does not make you different from any other user and expecting free support is unrealistic as it's not something we can offer to the whole community. As security team lead I've chosen to help you as I find it odd that you've been disproportionately affected (99% of others affected have simply applied one of the workarounds and the issue went away) and I want to analyse the reasons why to see if there are additional defence-in-depth measures we should add to 7.3.2. However my time is limited (I'm actually makes the fixes as we speak), so please keep all further correspondence with me to email responses.

thanks,

Cathal