Hi, Hey it sounds like others are familiar with SPAMassassin. That's good news.
Thanks for the suggestion but I am aware of SPAMD and have given up on it as it uses fork(). If I understand what it's doing parent process has loaded in the SPAMassassin "object" and hence invoked the Perl parse to parse the code into memory and then it fork()s of a child process to actually run the SPAMassassin code to read through the mail message. The assumption is that the forked child process creation doesn't incur much overhead, as in Unix, and the child process picks up the copy of the already compiled perl scripts from the parent. But that's moot as fork() is still unimplemented on VMS Perl. It is not there in VMS DECC nor is it implemented in VMS Perl. Please correct me if I'm wrong. I'm usuing 5.6.1 of VMS Perl. Maybe a later version supports it. So without fork() getting SPAMD to work on VMS perl would seem to be a poor use of my time. (I have some other complaints about SPAMD but since the absence of fork() renders them moot I won't go into them.) Regarding SPAMC, having that work for VMS would allow one to run the actual SPAMD daemon on another node which would be an arrow in our quiver - but I wouldn't want it to be the only arrow. Perhaps another option might be a Perl compiler to allow users to pre-compile Perl code. I have seen hints at this around some sort of perl "dump" command description in one of the O'Reilly books but can't remembed where for sure. Karol ============================== Karol E. Zielonko Jr. OpenVMS Engineering Hewlett-Packard Company If you have me in your address book please configure the entry to indicate that I prefer to receive plain text.
