I know this sounds like a stupid newbie work around, but I
thought I would throw it out there and see who tells me "now Dave, this can't be
done because...." ;-)
I found the .sh file that is used to start/stop/status the
spamd. I now have a cron job that monitors for the spamd process to disappear.
When it does, I run the .sh file in "restart" mode, just in case I missed
something and its really still running.
If anyone this think this is a really bad idea as a
'band-aid-patch", let me know. I realize it has some drawbacks, but I don't
think they can be helped...
Comments/rotten tomatoes?
- Dave
>>> Olivier Nicole <[EMAIL PROTECTED]> 05/15/02 09:45PM >>> >The basis of the problems seems to be that sendmail won't send the full email >across to spamc for whatever reason, at least on some platforms. Seems like it >would be logical for the whole message to get sent, then to read the whole Wouldn't it be rather spamass-milter that is not sending the full message to spamc? It seems that Milter is a very tricky piece of thing to code for (working with callback, sending the message piece by piece, with the availability to ask for more after each piece sent). I wonder if spamass-milter should not completely replace spamc. Olivier _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk |