I have to admit that I know next to nothing on fixing problems on my computer. The problem I have is when trying to post a comment on a certain blog site, I get the message “The website cannot display HTTP 450 most likely the cause. It goes on to this wesite is under maintance, the website has a program error.
What you can do is; refresh the page, still doing it.
Go back to previous page. Nothing.

I can read the blog & there are new comments happining but I can’t without the above message happening. This has gone on for 2 days. I have posted many times before on this site with no problem. No my comments are not offensive & I have not been kicked off. Could this be a virus on that blog? Please advice if you have any info to help fix the problem. Easy steps tp do?

Thanks

I have to admit that I know next to nothing on fixing problems on my computer. The problem I have is when trying to post a comment on a certain blog site, I get the message “The website cannot display HTTP 450 most likely the cause. It goes on to this wesite is under maintance, the website has a program error.
What you can do is; refresh the page, still doing it.
Go back to previous page. Nothing.

I can read the blog & there are new comments happining but I can’t without the above message happening. This has gone on for 2 days. I have posted many times before on this site with no problem. No my comments are not offensive & I have not been kicked off. Could this be a virus on that blog? Please advice if you have any info to help fix the problem. Easy steps tp do?

Thanks

On the other hand, I prefer to keep using 450 especially as it pertains to spammers. For zombie machines, this won’t do much other than tie up some more connections in my tarpit. For improperly confirgured mail servers or servers owned by spammers, this means their queues will fill up. The more they have in their queue, the less spam they will be able to send and the bigger mail servers they will need to buy.

This also means that if people are trying to send mail to my company from a mis-configured mail server and the mail is legit, then both they and I have more time to work out their misconfiguration (usually FcrDNS) and then the world is better off because less people have to leave their mail servers wide open to receive mail from them. I for one use some very tough and taboo regex filters to blacklist DSL and Cable modems, so I like to have some room for error. In fact, I could probably shut off spamassassin and stop checking with the RBL’s and I would still stop about 95% of the spam… so it is nice to keep them retrying just in case one of them happens to just be an ignorant DNS admin.

I do get some joe-jabs from time to time, simply because I have been poisoning spammer databases for about 8 years now and some of the get kindof pissed off about it. That is another tarpit that they don’t realize they are getting into. If my mail server starts receiving automated bounces from poorly configured mail server, it then sends a single email to each domains abuse and postmaster explaining them that they are replying to forged emails and that they can simply avoid that (at least as it pertains to my domains and any real domains) by checking SPF records. The spammers jabs are actually so counter-productive that I have actually helped several hundred small companies and organizations to start publishing SPF because of them. They simply can’t win. :-)

On the other hand, I prefer to keep using 450 especially as it pertains to spammers. For zombie machines, this won’t do much other than tie up some more connections in my tarpit. For improperly confirgured mail servers or servers owned by spammers, this means their queues will fill up. The more they have in their queue, the less spam they will be able to send and the bigger mail servers they will need to buy.

This also means that if people are trying to send mail to my company from a mis-configured mail server and the mail is legit, then both they and I have more time to work out their misconfiguration (usually FcrDNS) and then the world is better off because less people have to leave their mail servers wide open to receive mail from them. I for one use some very tough and taboo regex filters to blacklist DSL and Cable modems, so I like to have some room for error. In fact, I could probably shut off spamassassin and stop checking with the RBL’s and I would still stop about 95% of the spam… so it is nice to keep them retrying just in case one of them happens to just be an ignorant DNS admin.

I do get some joe-jabs from time to time, simply because I have been poisoning spammer databases for about 8 years now and some of the get kindof pissed off about it. That is another tarpit that they don’t realize they are getting into. If my mail server starts receiving automated bounces from poorly configured mail server, it then sends a single email to each domains abuse and postmaster explaining them that they are replying to forged emails and that they can simply avoid that (at least as it pertains to my domains and any real domains) by checking SPF records. The spammers jabs are actually so counter-productive that I have actually helped several hundred small companies and organizations to start publishing SPF because of them. They simply can’t win. :-)