Spamihilator and its plug-ins under Windows Vista - Anbuva's FAQ, revised -Pre-conditions
These FAQ (frequently asked questions) refer to the following basic configuration:
- Windows Vista (any 32-bit version)
- Spamihilator (current version, at least 0.9.9.26 or higher)
- User account control access available as administrator and as a user
- Standard installation paths being set on drive C:
- Mail accounts being served under a Windows user with restricted rights1. Which Spamihilator plug-ins have been optimized for Vista?
The following list shows the plug-ins downright optimized for Vista:
- Spamihilator's elementary filters, namely Learning Filter, Spam Word Filter, Newsletter Filter, DCC Filter, Link Filter, Image Filter and Attachment Filter
- Spamihilator's Pop3Notifier Plug-in
- Bob Loeffler's Filters, and that are Empty Mail Filter, Html Filter, Plain Text Filter, No Comment Filter, Scripts Filter and the helpful Statistics Plug-in, Export Senders Plug-in, and Unclassified Filter Plug-in
- Misnamed Filter (current beta), Outgoing Friends (current beta), IMP-Filter (TextTransformer)
- Live Stats Plug-in
These are Spamihilator plug-ins working properly with Windows Vista, even though not yet optimized:
- Charset Filter (beta), Strange Country Filter, Air Filter
- Alphabet Soup Filter, S_P_A_C_E Filter, URL-Filter (current beta)
- Spam-Report Plug-in (beta)
- Language Packs (working correctly)
- Boarisch Language Pack (working correctly)2. After the computer boot, the starting procedure of Spamihilator lasts very long or hangs in a waiting loop.
This is caused by the Windows auto start function and the prefetch function and will normalize by itself after a while. 3. How can I recognize the incompatibility of Spamihilator plug-ins? After the installation of a plug-in, I can't see the installed files.
Windows Vista provides a virtual directory, which pretends writing rights for applications that aren't actually compatible to Vista to the folder "c:\programs". You will find it in the following folder (if there is no further folder, presumably there is no incompatibility):
"C:\Users\USER_NAME\AppData\Local\VirtualStore\Program Files\Spamihilator". 4. During the installation procedure of Spamihilator or of a plug-in, Vista asks for the administrator password. Is this dangerous?
Administrator rights are needed to allow the Spamihilator installation to write into the directory "C:\Programs", which is not allowed to a restricted user. 5. I can't install Spamihilator or a plug-in! After double click on the executable setup file, nothing happens.
The installation procedure needs to be started with administrator rights under the performing restricted user. With Vista, this is easily to carry out, just by right clicking on the setup file and choosing "run as administrator".
The same is needed by some other programs. Normally, Vista should recognize needed administrator rights and accept it accordingly. 6. The virtual path is not existing, respectively I can only find path names in my own language. Do I have to reckon with problems whilst the installation?
No, because Vista is using standardized paths, localized in the system language. The correct paths can be recognized by using the dos box or a file manager (e.g. Windows Explorer) to watch the installation paths.
Example: an installation in "C:\Programme" (in German) is in fact copied in "C:\Program Files". 7. An error message appears, while receiving mails, saying that the server "localhost" or "127.0.0.1" could not be found. Thus, the mail client doesn't work together with Spamihilator.
On the Vista system, the host file can be found under
It contains the two lines
To comment out (with the "#" sign) or to delete the second line lets function the program again. The second line belongs to the Internet Protocol version 6 (IPv6). 8. After the installation of Spamihilator or of a plug-in, Vista shows a message, saying that the program possibly is not installed correct.
This may occur during the installation process or after the installation. This can be ignored without disadvantage, the installation will complete correctly anyway and Spamihilator will work without any problems. 9. Spamihilator's setup assistant doesn't recognize my mail client, respectively Windows Mail in Vista.
When the mail client configuration doesn't work automatically, it can be easily done manually. See also in the Spamihilator Online Help
. Configure your mail client:
- Incoming server = POP3 or IMAP
- Incoming server address = localhost or 127.0.0.1
- Incoming port = 110
- Local server port POP3 = 11010. Do I have to assume problems with the Vista firewall or any other firewall?
Normally not, because Spamihilator will be recognized automatically or by prompting the user and will work without any trouble with every firewall. Otherwise, survey the firewall rules and delete the concerned rule, for to allow the firewall to create it newly. 11. How does Spamihilator function together with screen savers?
Under Vista's screen savers, the pop-up window of Spamihilator shows up, letting the screen saver continue. Problems may occur with some special screen savers, particularly when they use a special graphical resolution. 12. Mails in the in-box of my mail client don't appear in the training area of Spamihilator.
This happens, when running Spamihilator as administrator, especially after installation of Spamihilator plug-ins. Mails are assigned to the administrator user account and arrive to the administrator's training area, but anyway to the restricted user's mail client.
Corrective: Close Spamihilator and restart just as restricted user again. 13. Do I have to be aware of problems in conjunction with the integrated spam filters in Windows Mail, Outlook or other mail clients?
In general not, because Spamihilator is interposed as a proxy between the mail client and the mail server, and the mail client will only apply its own filter after Spamihilator having regularly delivered the mails to the mail client. When still missing a mail in the in-box, it may have been moved by the mail client into its junk folder. To avoid such problems, the mail client's built-in junk filter should better be turned off or mitigated. 14. Mails recognized as non-spam by Spamihilator don't appear in the in-box of the mail client.
Many mail clients are providing built-in junk filters, which may move mails to their own junk-mail folders unawares. These junk folders can be overlooked easily, considering the plenty of folders. 15. Mails from senders recorded in the friends list do not appear in the training area. Does Spamihilator learn from mails from friends at all?
In this case, it needs to be checked if the function "automatically learn from messages from my friends" is activated, and if the sender address is recorded properly in the friends list.
Recommended settings: In case there are sender addresses recorded in the friends list, the above named function should be activated in order to enable learning from their mails. Without this function activated, mails from friends only get delivered without learning from. 16. Spamihilator doesn't sieve any spam mail, although they are shown in the training area. No spam mail appears in the Spamihilator recycle bin.
Make sure to have checked the expanded display of the mail in the Spamihilator training area. The information about the filter reason given there allows you to recognize, whether the filter sequence has to be customized, or Spamihilator needs a little more time for learning after a recent installation. Of course, Spamihilator wouldn't filter actually, when no filter is activated at all. 17. I can't select or deselect the check mark for the activation of the automatic Spamihilator start with Windows.
This setting can be found under the general settings, it's called "launch Spamihilator at Windows startup".
Disabling the registry item within "HKLM\Software\Microsoft\Windows\CurrentVersion\Run" will solve this problem. Unless this item is deactivated, Spamihilator will start with every Windows user automatically. Else, this setting can be deactivated with MSConfig started as administrator. 18. How can I save all my settings and the training data for a future new installation?
For that purpose, you can save completely the following folder and all its sub-folders and files within
"C:\Program Files\Spamihilator" and
After the new installation of Windows and Spamihilator, you can insert them at their original location. Perhaps you have to overwrite the newer folders. Care about the writing rights, certainly. 19. Is the use of Spamihilator really free of charge, or does the term of use expire after a while? Is it free for use in a commercial ambit, too?
Yes, Spamihilator is freeware for private and commercial purposes. There is no expiration date or demo period. 20. My anti-virus program complains having found a virus whilst downloading or installing Spamihilator!
Spamihilator is not containing any virus code or other malware or spyware, being tested with different security instances and confirmed by beta testers and an extended community and by professional testers of computer magazines. This is likely to be a false positive alarm of the anti-virus software. Be careful to have downloaded the Spamihilator setup executable file from a trustworthy resource, for to avoid manipulated downloads. Beyond that, make sure not to have another malware on your computer, infecting other programs, e.g. Spamihilator. 21. Is it possible to use Spamihilator with a mobile device, e.g. on a USB stick?
Unfortunately, this isn't possible until now. 22. Does it cause trouble using Spamihilator together with another spam filter program?
Some other spam filters do interact inappropriately with Spamihilator and thereby cause disturbances in receiving mail. In most cases, it wouldn't be reasonable to use more than one spam filter, anyway. 23. Although started properly and visible within the Windows Task Manager, the Spamihilator tray symbol doesn't show in the tray area.
This is a known bug of Windows XP. Presumably other tray symbols are lost on a such affected system, too. 24. I have updated from a Spamihilator version lower than 0.9.9.26, and now I encounter odd behavior of mail reception.
The newer generation of Spamihilator versions have obtained many improvements and new features, too. Spamihilator, and specially its installation, had to be customized to the requirements of Microsoft Windows Vista, which concerns mainly the User Account Control.
To avoid potentially annoying trouble, it is necessary to adhere to the following instructions carefully, best having carried out a complete system backup:
a) Perform a complete uninstall of the old Spamihilator version
b) Manually delete every directory associated with Spamihilator, even if hidden, e.g.:
- C:\User\USER_NAME\AppData\Local\VirtualStore\Program Files\Spamihilator
- C:\Users\USER_NAME\AppData\Local\VirtualStore\Program Files\Spamihilator
In Windows XP:
- C:\Documents and Settings\USER_NAME\AppData\Spamihilator
c) Reinstall Spamihilator with the plug-ins approved for use with Vista25. Will I have to encounter problems with IMAP under Vista?
Using IMAP with Vista doesn't arouse any problems by itself. We have tested IMAP with a free account, made available and supported kindly by "diemailbox.de", using Outlook 2007 under Windows Vista.
- user name = John Public
- mail address = john.public@
- account type = IMAP
- incoming server = 127.0.0.1 or localhost
- sending server = smtp.diemailbox.de
- user name = imap.diemailbox.de&
- Configure sending settings different from receiving settings, not inclosing the typical entries needed for the Spamihilator proxy
- Do not check "login with secure password authentification"
- Don't activate the SSL/TLS in the mail client's accounts, but in the Spamihilator settings, if intended
- Set the server timeout to the highest possible value
- Formerly, the IMAP module worked somewhat a little notchy, but the current Spamihilator works smoothly
- A pitfall with IMAP and Spamihilator is the handling of false positive filtered mails, because keeping them in the recycle bin subducts them from the IMAP server
- The brilliant cross protocolling method bypasses the IMAP protocol and enables you to receive IMAP mails like POP3 mails
- For this purpose enter the following account information in the mail client's input form:
- - incoming server = POP3
- - incoming server = localhost or 127.0.0.1
- - account: imap_server&
143 (Created in June, 2007, last updated in December, 2008, and translated into English on march, 2009. Sorry to all English readers for the rather poor English lingo. Upwards to the opening posting.)