Trying to configure Spam Assassin

I have been trying to configure iMS 5.2 with hotfix 1.24 on a Win2000 system, I have the Delegated Admin server also installed.

The system is currently installed and working, I can send mail in and outbound on the system and am using the LDAP server for user id/password management.

My problem generally revolve around the use of a SpamAssassin daemon I have running on a remote system.

The spamd daemon process is currently running on the remote system and I can detect if a connection attempt is made to filter an incoming message.

I don't assume you are familiar with spamd/spamc but let me just say that I can process messages via the client process spamc via the server process spamd with no problem.

My problem deals with the fact that inspite of the fact that I have made changes to the configuration of the iMS 5.2 server to activate spam filtering using SpamAssassin, I can detect no attempts by the iMS 5.2 server to send the email to the spamd server, and am having problems tracking if the module or (.dll in this case) is being called.

ON a higher level I am not sure if the logging facility is configured correctly.

The questions are as follows:

1) I'm not sure about how I am suppose to view the log files, it seems they are viewable as an html text file e.g. http://www.x3ci.com/qtmp/maillog.txt but they are unreadable/garbled in Windows notepad,

a) does the "Messageing server Console" provide a means to view the log file? When I look, it seems that the default path is scrambled for the intended log e.g. http://www.x3ci.com/qtmp/iMS_snap1.bmp

b) is this (see question a) why the Messaging Server Console is unable to display or show stats on the file when I clk on the "content" tab? e.g. http://www.x3ci.com/qtmp/iMS_snap1.bmp ?

c) is there a config file under the iMS 5.2 structure where I can see the full path file name for the admin log and the default log?

2) As I stated previously I am trying to verify if an attempt is being made to contact the spamd daemon process for spam filtering, I have no idication this is happening from the spamd side, in order to tryto track what is happening on the iMS 5.2 server side, I tried to follow the instructions for turning on debugging, to this extent I have added the lines required under the option.dat file ( http://www.x3ci.com/qtmp/option.dat ) to enable SpamAssassin :

Brightmail_Library=D:\Server5\bin\msg\imta\lib\libspamass.dll

Brightmail_config_file=D:\Server5\msg-mail02\imta\config\spama.dat

I have verified that libspamass.dll does reside under the full path I designated.

I have also created the file spama.dat (http://www.x3ci.com/qtmp/spama.dat)

under the full path designated by Brightmail_config_file .

I turned on debugging by the following actions :

Adding the lines :

MM_DEBUG=5

log_message_id=1

to the option.dat file ( http://www.x3ci.com/qtmp/option.dat )

and adding the key words master_debug slave_debug to both the tcp_local and tcp_intranet lines of the imta.cnf file (http://www.x3ci.com/qtmp/imta.dat) although I am not quite sure if this is required.

In spite of these actions I can detect no attempt by the iMS server to call spamd, here is a snippet of the activity log (http://www.x3ci.com/qtmp/maillog.txt) while it indicates network external messages coming inbound to the system, I see no evidence that they are being forwarded to spamd.

Any Idea what might be wrong here?

Please not, suffixes of file names under http://www.x3ci.com/qtmp have been changed to make them viewable via a browser e.g. imta.dat (as listed in the x3ci.com directory) is actually imta.cnf on the server, as it should be. Also imsimta refresh and imsimta cnbuild have been invoked after these file changes with out error.

[3982 byte] By [adialfonso] at [2007-11-25 11:02:11]
# 1

Well, alas, the library is not part of the windows2000 package, and cannot be ported there. I see you found something that appears to be the correct library, but I believe that spamassassin just doesn't work in windows.

If you've made config changes, did you remember to

imsimta cnbuild

imsimta restart dispatcher

after the file edits?

You either have to set it up through the conversion channel, or use a unix box for your iMS installation. . .

That's why I purchased an ultra 5 sparc, for my mail server needs. . . .

your log files are indeed just text files. I use wordpad rather than notpad. Console may allow you to view some logs, but not the MTA ones.

The admin log would be in the admin server's installation path, under admin-serv/log

the default log lives with the other iMS 5.2 logs in

<install_path>/msg-<name of your server>/log

look for the different log types,

default

imap

pop

http

imta

jay_plesset at 2007-7-1 22:10:35 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 2

Q1) So what your saying is that libspamass.dll is a non-functional library and the documentation on hooking iMS 5.2 into SpamAssassin is invalid on a Windows 2000 platform?

Q2) I know this is a dumb question but is this an official response, or could some one confirm this?

Q3) When I read the instructions on how to activate SpamAssassin and cross reference with the arnold mailing list, seems that some activated the usage of the spamd by using BrightMail flag sourcebrightmailoptin on the tcp_local channel (the person resolving this seems to impy they are not on a Windows2000 platform, but might the sourcebrightmailoptin flag be all I am looking forn?

I ask these questions redundantly because SpamAssassin access is an advertised feature of the product on all platforms so I just want to make sure I understand what I am hearing.

adialfonso2 at 2007-7-1 22:10:35 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 3

My understanding was that libspamass.dll was not delivered with the product. If I am incorrect, and you have it, then perhaps it can be made to work.

In order to properly install/configure spamassassin, using the library dll, you will need to carefully follow the instructions, here:

http://docs.sun.com/db/doc/816-6829-10

That means:

1. install spamassassin.

2. start spamd before starting iMS

3. configure the imta.cnf per the documentation in the link above.

4. configure option.dat per the documentation above.

5. run "imsimta cnbuild" to make the configuration "take".

6. make sure you're running iMS in "Direct LDAP mode", not "dirsync mode".

If you wish to post the channel blocks from imta.cnf and your option.dat file, I'd be happy to compare it with my (working) spamassassin installation on Solaris.

jay_plesset at 2007-7-1 22:10:35 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...
# 4
Please also note, this forum is NOT an official support channel. Sun participation is totally voluntary, but I can't claim to be the ultimate authority for iMS.
jay_plesset at 2007-7-1 22:10:35 > top of Java-index,E-Mail, Calendar, & Collaboration,Sun Java System Messaging Server...