>>120
Provide a line number. It just doesn't happen.

I just traced the execution by hand, and unless I'm incredibly dense, it does no wget or locally implemented equivalent anywhere.
Full execution path is as follows:

1. wakaba.pl:486: post_stuff passes spam_files=>[SPAM_FILES] to spam_engine
2. wakautils.pl:1046 spam_engine initializes local @spam_files array
3. wakautils.pl:1054 spam_engine passes @spam_files to compile_spam_checker
4. wakautils.pl:1034 compile_spam_checker maps read_array on its local arg list
5. wakautils.pl:962 read_array accepts one scalar, which can either be a filehandle or a filename; if it's a filename, it opens the file locally with open FILE,$file. Either way, it returns all the lines in the given file as an array.
6. wakautils.pl:1028 back to compile_spam_checker to munge the results from read_array into a form suitable for inserting into a regex
7. wakautils.pl:1023 ... which it then does a bit more munging on, saving the results in @re
8. wakautils.pl:1036 still in compile_spam_checker, take @re and build a block of code out of it
9. wakautils.pl:1054 back to spam_engine; results from compile_spam_checker are saved as $spam_checker and all the form fields are scrunched together into $fulltext
10. wakautils.pl:1060 spam_engine still. actually run the spam checker with the given text, and call spam_screen if it gets triggered
11. wakautils.pl:1063 spam_screen just prints out a page saying "anti-spam filters triggered". (On an unrelated note, this page doesn't use the templates at all.)
12. wakaba.pl:493 if the spam checker didn't find anything, control returns here.