|Q:||It seems the action "Add sender address to the Black-/Whitelist" does not work. There are no addresses shown in the Spam filter settings. But why is there not an error message?|
|A:||Addresses added by a SmartPOP2Exchange action are added to an auto-whitelist/blacklist, so these addresses are not listed in the Spam filter options. You can find the files for the auto-whitelist/blacklist under "%COMMONFILES%\JAM Software\SpamAssassin\etc\SpamAssassin\" (JAMAutoWL.cf or JAMAutoBL.cf)|
|Q:||Can I adjust SpamAssassin settings myself?|
|A:||Of course you can. Please see the Spam Filter chapter.|
|Q:||Do I need to open any ports for the integrated SpamAssassin?|
|A:||Yes, since V7 of SmartPOP2Exchange the integrated SpamAssassin does not only use RBL which requires ICMP for requesting, you also need to open TCP Port 7 and TCP Port 2703 to make SpamAssassin able to use Razor2.|
Otherwise spam scans may take longer than one minute or you need to disable Razor2:
- Create a cf file like "XMySettings.cf" (text files) and put "RAZOR2_CHECK 0" in it.
- Put this file in "C:\Program Files\Common Files\JAM Software\SpamAssassin\etc\spamassassin\"
|Q:||I get an error message of an access violation in spamd.exe and then SpamAssassin sometimes is not available any longer. How do I get rid of this?|
|A:||This error message only occurs when a "real" JIT debugger like "vsjitdebugger.exe" from Visual Studio is installed.|
It is never recommended to have such a JIT debugger running on a productive system!
The JIT debugger will attach to any process causing an unhandled exception and ask for debugging. So spamd.exe will be paused/blocked.
The error itself occurs deep inside of SpamAssassin and can't be avoided because of the port of SpamAssassin from Linux/Unix to windows.
The error does not influence SpamAssassin scans at all. So please de-register any JIT debugger from your system or exclude spamd.exe if possible.
For de-registering you need to clear the following registry entry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug] "Debugger"=""
on x64bit systems additionally:
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug] "Debugger"=""
|Q:||Where can I change the threshold value of the spam-filter?|
|A:||To change the threshold you have to open the "spam" rule in your Account form. Choose "Message declared as spam..." from "5. Rule description" and enter the new value for the threshold.|
|Q:||How do I get updates for the integrated SpamAssassin?|
|A:||SpamAssassin does update its rules files once a week automatically.|
|Q:||How do I get updates for the integrated ClamAV?|
|A:||The "engines" of ClamAV and SpamAssassin are updated with SmartPOP2Exchange updates.|
The integrated ClamAV automatically updates its virus signatures several times a day from official sources independent from our product updates.
|Q:||Which virus scan software is supported by SmartPOP2Exchange?|
|A:||Because SmartPOP2Exchange uses the "on access" function of virus scanners, any antivirus software offering this feature can be used. You just have to figure out which settings of your virus software apply. For further information, please have a look at the chapter antivirus overview.|
|Q:||Can I update the integrated ClamAV myself?|
|A:||You may update the dlls and exe files (C:\Programs\Common Files\JAM Software\ClamAV) of ClamAV yourself by getting them from the ClamWin (http://www.clamwin.com) project, but we do not give any support for this. It may cause viruses to not be detected or any mail/file to be detected as a virus. We once had this situation when ClamWin changed some interfaces which did not result in an error, just in strange behavior.|
The virus signature files used by ClamAV are placed in:
C:\Documents and Settings\All Users\Application Data\JAM Software\ClamAV
and are updated automatically; at least every 3 hours.
|Q:||Why did I get virus infected mail although I have activated the virus checking function of SmartPOP2Exchange?|
|A:||Please be sure that your AV software is configured correctly. (see Antivirus overview)|