I just sent every crash report the program generated. You call crashing while submitting a "minor" issue?
Depends on the cause, if it's only happening to a single user, caused by loading corrupt files, trying to comment to specific URL's like
this one that bring 10+ yo browsers to their knees, your security denying writes to the SB ini file and so on then yeah it's a minor issue.
There is a small bug in the IP Test in the Proxy Module.
A specific proxy that sends an X-forwarded for header, passes the test. Obviously though, it leaks the ip.

I checked it with online tools and saw the header.
If you want, I can sent you the ip of the proxy I tested by PM.
Thanks!
X-Forwarded used to be blocked, people complained they couldn't get enough free proxies because obviously keeping only Elite would mean there's close to none left.
As someone mentioned before, X-Forward does not get passed to blog dashboards, the only thing that shows is the proxy IP not yours. So sure the proxy checker can be changed, but no doubt that would kill the free proxies.
>Pretty sure the select to compare does it at the URL level. But what you could do is harvest URL's, then merge in your success list and pick remove duplicate domains. I think that would give you what you are after.
But that would mean the same domain could get another entry. Which would look obvious to the webmaster. And when first delete duplicate urls from the newly scraped list you cant be sure that the url that is kept is the same that is in the successlist. So it could be that there is another blogentry in the successlist which would mean the webmaster sees again the very same comment.
Maybe a small problem but I think staying under the radar is better.
If you want to block domains at the root level, then trim your list to root and save the file out as Blacklist.txt in your blacklist folder.
As a final test I then used the manual option to post a comment - this worked and the new comment could be seen and also on page reload, but the automated comments were nowhere.
The Accurate Mode and Manual Mode are identical, they have the same form detection, same form filling, same proxy handling everything. The only difference is Manual Mode you click the button instead of ScrapeBox, and if ScrapeBox wasn't clicking the button properly it wouldn't say success or fail it would sit on the page until it timed out.
So not sure what's up with that, maybe your domains were blocked. BlogEngine has changed a lot.
Note the bold:
BlogEngine.NET 1.6 is Released - February 1, 2010 01:56
For those who receive a steady dose of comment spam (and who doesn't!), a new powerful Comment Management and Comment Spam Filtering infrastruture has been added in version 1.6. Comments across all posts can be viewed, edited, deleted or approved in one convenient area. Comments can still be manually moderated, but now moderation can be automated by running comments thru remote or local comment spam validation services.
Yes it's now has moderation, Askimet, Stopforumspam and other things. If people are having problems with it crashing, not commenting and can't get links with it via the old comment method, the new comment method and the manual mode then it may just be time to remove it because that's 3 options and there's not a fourth.