![]() I am no javascript coder, so it's a bit long for me to debug that. SpamAssassin for Windows is an effective anti-spam solution utilizing text analysis, Bayesian filtering, and DNS requests to block known spam senders. Is there a problem with the iframe variables or something ? I strongly suspect some sort of javascript problem with preference-frame iframe variables. When I immediately check Javascript error console on Firefox, here is what I get. Obviously, the email address does not get recorded in the database. ![]() The email address in the field disappears and SAuserprefs tells me "Successfully changed spam settings". The SpamAssassin Server log is located at STDOUT, and the following command line will let you inspect it: docker attach -sig-proxyfalse my-container-name where you only see the new log messages. It is a simple procedure that should only take 5 minutes. thats means SAuserprefs does not have any problem with connecting to the database): It's aim is to install Spamassassin and its service for running in connection with the default integration with Hmailserver. Complete Online Manual Compatibility Windows 11 (64 Bit only) Windows 10 (64 Bit only) Windows 8. Includes a resident daemon for mail servers and a user-friendly personal spam filter that works with any POP3 account and any email client. I use the form to add an email address "garybaldi.baldi " to the blacklist (notice that the first entry "garybaldi" was added manually in the database. Use our comprehensive online manual and take advantage of the expert know-how on the renowned spam filter for Windows with integrated Windows system service. SpamAssassin for Win32 is a free and powerful anti-spam filter for Windows. SAuserprefs version is the last one (4th of October 2012). Of course, in the SQL database, nothing gets recorded. On my firefox and Chromium, when I use sauserprefs for inserting a record into the database, I get a javascript error, although the plugin says that my changes were saved. Some good, free web-based tools are available to put a friendly user interface on whitelists (and blacklists) and allow users to edit their own. I searched the forum but it seems I am the only one to get the following issue (well, actually I am not, my whole company gets the same issue). Use FireDaemon, or some other such tool to run SpamD as a windows service and then call SpamC from within the EventHandlers script: Code: Select all SpamAssassin command string cmdSC 'cmd /c C:SAspamc < ''' & oTestfile & ''' > ''' & oInfile & '''' Run SpamC rcSC oWSO. More info on whitelistfrom, whitelistfromrcvd, and blacklistfrom is on the web or can be accessed from your local man pages by typing perldoc Mail::SpamAssassin::Conf.
0 Comments
Leave a Reply. |