Users are able to reach the SpamCop site and parse/report small emails, but when trying to submit a large spam through the website form they get a time-out error after clicking the "parse" button. This is a problem experienced by users with firewalls. It may be a personal hardware/software firewall you have employed or, there may be a firewall on your ISP's network "protecting" you that you are not necessarily aware of.

SpamCop is an ever changing entity in a moving sea of data. Not only does it use internal databases to keep track of contact emails, closed accounts, historical data, etc., but it also relies on network databases to be up, operational, and accurate. To add to this confusion, changes are frequent to the algorithm, so you may experience a bug one day and find it fixed the next. Unfortunately, the reverse is also true - everything can be fine one day and new bugs appear the next.

There are three main parts to SpamCop; the Reporting Service, Mail Service, and Blocking List. All three operate independently of each other, but they also rely on each other to operate effectively. The reporting service allows you to file complaints with appropriate administrators about spam. These reports generate statistics that are fed to the Blocking Service, automatically keeping it up to date.

SpamCop has begun requiring that spam containing HTML is submitted with the HTML codes intact (funny codes in the body of the message). This prevents erroneous complaints and allows SpamCop to find sites referenced within the HTML. Just because you don't see pretty pictures and colorful text does not mean the email you are viewing does not use HTML coding. The HTML tags contain the email and web site addresses, which may not be contained in the plain text.

This means that SpamCop found an email address to complain to, but it was invalid. If you find a more-correct place to report spam issues for the email in question, you may report these updates to deputies@admin.spamcop.net. Please do not send email unless you can provide a working abuse address where none was found before. You must confirm that the new address is correct and responsive to spam reports before you ask SpamCop to use it.

SpamCop will not send reports for any spam it detects is more than 48 hours old, as indicated by the first accepted Received: line. SpamCop uses the date of the topmost useful Received: line. This is usually information direct from your own email server, not the spammer's email system. The date used is actually appended by your own ISP and indicates the amount of time the email has been sitting in your inbox waiting for you to retrieve it.

This error is caused by a setting in your FTP client, that limits the amount of time your FTP client will wait for a server to respond. In order to fix this problem, increase the "server timeout" setting; a setting of 180 seconds should be enough time to connect to the archive.org servers. If you use SmartFTP, the "server timeout" setting can be found in Tools > Settings > Connections.

The header of the spam didn't have enough information to figure out what IP the spam came from. This happens sometimes on very old or strangely configured email systems. For instance, if you are using a Novell or old Microsoft server, you may have this problem. The problem also occurs with hotmail, but only intermitantly. If this is the problem, you will probably see it with ALL email (unless you use hotmail, then only sometimes).

SpamCop no longer (as of Feb 25th, 2003) trusts relays which have not been submitted for relay testing by SpamCop.

When you watch a story we don't provide a direct link to the movie files on our server. We instead provide a "Click To Play" link that is unique to you, but is only available for a short period of time (roughly 60 seconds). If you do not actually click the "Click To Play" graphic to start watching your chosen story before the link expires you will get the "Click To Play" Timeout error.

The price is $1.00 per megabyte of email processed. This charge is asessed when a) when you paste email into SpamCop's reporting form and hit "parse" or b), when you click on the link to go to the parsing page for spam submitted through the SpamCop's email submission system. When you subscribe, we bill you for however many bytes you choose to use, and we warn you on the homepage when you run out of "fuel.

SpamCop is the premier web-based service for reporting and blocking spam, founded in 1998 by Julian Haight. SpamCop processes over one million spam complaints a day and is supported by hundreds of thousands of users, a knowledgeable volunteer community, and a professional staff. SpamCop streamlines the process of determining the origin of spam emails and reporting them to the relevant Internet service providers. SpamCop offers both free and premium reporting services.

Advertising is now available on the SpamCop.net website. Your 468x60 banner will run in a regular rotation on free users' pages. Paying members do not see banners, nor are banners shown on some peripheral pages (such as the FAQ). Banners are shown to users on the home-page and during spam processing as well as on other pages, such as the help center and statistics pages. They are also shown to anyone responding to SpamCop reports through the web site.

by default the IP is 192.168.1.168 Mask is 255.255.255.0 You have to add an IP address to your workstation that is within the same subnet.

will set a ten minute timeout for all protocols. If you want to set a specific protocol, such as FTP, put that in place of the default. system/schemes/ftp/timeout: 0:10

If you have applied and received a 'Duplicate Transaction' error you have hit the 'Submit' button more than once. Your account may have already been created, check your email for a confirmation letter from us with your Adult Check ID in it. If you did not receive a confirmation letter from us then your account was not created and you may apply again.

This error is caused by a setting in your FTP client, that limits the amount of time your FTP client will wait for a server to respond. In order to fix this problem, increase the "server timeout" setting; a setting of 180 seconds should be enough time to connect to the archive.org servers. If you use SmartFTP, the "server timeout" setting can be found in Tools > Settings > Connections.

To debug lock timeout errors, set derby.locks.monitor=true and derby.locks.deadlockTrace=true in derby.properties. This will print the lock table information to the derby.log when the timeout happens. If you also set derby.language.logStatementText=true, then all the statements executed on the system will be written out to the derby.log. Statement information also includes the transaction id on which the statement is being executed.

If your XML is extremely large it may take flash a long time to process your XML. If this takes longer than 15 seconds, the flash player will throw an error. You cannot change this error, or its timeout. Your options will be to reduce the size of your XML file or load and parse it in several chunks. It has been found that attributes are a lot quicker to access and parse than child nodes.

Microsoft has confirmed that there is a software flaw in Internet Explorer with Content Advisor enabled. This will be resolved with a future patch from Microsoft; however, there are two immediate options for solving this issue: Go to Tools in your Internet Explorer browser and click on Internet Options. The Options window will open. If you do not wish to disable the Content Advisor, another option is to use another, more secure browser called Mozilla Firefox.