Bradley Walker wrote: > I didn't ignore your first message, in fact I read it, have it archived in a > folder here to continue to try and discern helpful information from. Being > I'm working 14-17 hours a day as a business owner, replies sometimes can't > always come in due time.
Sorry if I seemed rude, but the only thing that can be seen is you constantly asking about this problem, without giving feedback. > appropriately. However the system itself is not under a stressful load at > this point. Load averages throughout the day sometimes can even be > 0.0/0.0/0.0 while email is continually being processed. It's still strange that 5 minutes is not enough for SA to process a single message. This is usually a sign of an overloaded system or very heave rulesets. What's your hardware and mail volume? btw, if you don't need user-specific rulesets and bayes-db, you should switch to content scanning at ACL time. It's less complex, more stable and lowers system load. And if you trust your users a little bit (after all, you have a contract), you can exclude authenticated senders from spam scanning. > Several people on the SpamAssassin list have commented that the spamc child > process has been terminated created the error that I orginially posted. That may be true, but 5 minutes should be really enough for SA to scan a message. -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
