Hello everyone,
I have installed/configured Spamassassin 3.10/Squirrelmail 1.45/ClamAV .87.1 on a FreeBSD 4.11 box (actually went very well). Spamassassin is catching test messages, and they are placed into the appropriate users "spam" box in squirrelmail. However, after running/logging in debug mode I have two errors that for the life of me, I cannot find a solution for.
The first problem in regards to the following log messages that appear soon after starting spamd:
++++++++
Jan 9 22:13:54 server1 spamd[47844]: prefork: sysread(8) not ready, wait max 300 secs
Jan 9 22:13:54 server1 spamd[47843]: prefork: sysread(7) not ready, wait max 300 secs
Jan 9 22:16:25 server1 spamd[47844]: prefork: periodic ping from spamd parent
Jan 9 22:16:25 server1 spamd[47843]: prefork: periodic ping from spamd parent
Jan 9 22:16:25 server1 spamd[47844]: prefork: sysread(8) not ready, wait max 300 secs
Jan 9 22:16:25 server1 spamd[47843]: prefork: sysread(7) not ready, wait max 300 secs
Jan 9 22:18:57 server1 spamd[47844]: prefork: periodic ping from spamd parent
Jan 9 22:18:57 server1 spamd[47843]: prefork: periodic ping from spamd parent
Jan 9 22:18:57 server1 spamd[47844]: prefork: sysread(8) not ready, wait max 300 secs
Jan 9 22:18:57 server1 spamd[47843]: prefork: sysread(7) not ready, wait max 300 secs
Jan 9 22:21:28 server1 spamd[47844]: prefork: periodic ping from spamd parent
Jan 9 22:21:28 server1 spamd[47843]: prefork: periodic ping from spamd parent
Jan 9 22:21:28 server1 spamd[47844]: prefork: sysread(8) not ready, wait max 300 secs
Jan 9 22:21:28 server1 spamd[47843]: prefork: sysread(7) not ready, wait max 300 secs
++++++++
I have searched "high-and-low" and have only found references to the above through archives of the spamassassin dev group. Nothing of "substance" however. Spamd doesn't die, but the 2 child processes come to a hault. Has anyone viewed their spamassassin output in debug mode to see if they encounter the same? Any ideas?
The second is something that I have seen in the forums here, but have not been able to find a solution for. Several people here have referenced the error in numerous posts, however the config options they have presented (for both directadmin templates & the site-wide spamassassin conf files (/var/mail/spamassin/local.cf) do not solve the problem.
++++++++
Jan 6 16:30:58 server1 spamd[439]: config: failed to parse line, skipping: rewrite_subject 1
Jan 6 16:30:58 server1 spamd[439]: config: failed to parse line, skipping: subject_tag *****SPAM*****
++++++++
I consider this a "cosmetic" bug, in that the message subjects are being rewritten for spam that is received - spamd is just logging incorrect info. Any ideas with this one? The following is a sample of my user_prefs in
/usr/local/directadmin/data/templates/custom
*******
report_safe |report_safe|
|blacklist_from|
|whitelist_from|
required_score |required_hits|
rewrite_header subject |subject_tag|
********
Any assistance/suggestions/or redirection to possible solutions is greatly appreciated!!! Thanks again!
Michael
I have installed/configured Spamassassin 3.10/Squirrelmail 1.45/ClamAV .87.1 on a FreeBSD 4.11 box (actually went very well). Spamassassin is catching test messages, and they are placed into the appropriate users "spam" box in squirrelmail. However, after running/logging in debug mode I have two errors that for the life of me, I cannot find a solution for.
The first problem in regards to the following log messages that appear soon after starting spamd:
++++++++
Jan 9 22:13:54 server1 spamd[47844]: prefork: sysread(8) not ready, wait max 300 secs
Jan 9 22:13:54 server1 spamd[47843]: prefork: sysread(7) not ready, wait max 300 secs
Jan 9 22:16:25 server1 spamd[47844]: prefork: periodic ping from spamd parent
Jan 9 22:16:25 server1 spamd[47843]: prefork: periodic ping from spamd parent
Jan 9 22:16:25 server1 spamd[47844]: prefork: sysread(8) not ready, wait max 300 secs
Jan 9 22:16:25 server1 spamd[47843]: prefork: sysread(7) not ready, wait max 300 secs
Jan 9 22:18:57 server1 spamd[47844]: prefork: periodic ping from spamd parent
Jan 9 22:18:57 server1 spamd[47843]: prefork: periodic ping from spamd parent
Jan 9 22:18:57 server1 spamd[47844]: prefork: sysread(8) not ready, wait max 300 secs
Jan 9 22:18:57 server1 spamd[47843]: prefork: sysread(7) not ready, wait max 300 secs
Jan 9 22:21:28 server1 spamd[47844]: prefork: periodic ping from spamd parent
Jan 9 22:21:28 server1 spamd[47843]: prefork: periodic ping from spamd parent
Jan 9 22:21:28 server1 spamd[47844]: prefork: sysread(8) not ready, wait max 300 secs
Jan 9 22:21:28 server1 spamd[47843]: prefork: sysread(7) not ready, wait max 300 secs
++++++++
I have searched "high-and-low" and have only found references to the above through archives of the spamassassin dev group. Nothing of "substance" however. Spamd doesn't die, but the 2 child processes come to a hault. Has anyone viewed their spamassassin output in debug mode to see if they encounter the same? Any ideas?
The second is something that I have seen in the forums here, but have not been able to find a solution for. Several people here have referenced the error in numerous posts, however the config options they have presented (for both directadmin templates & the site-wide spamassassin conf files (/var/mail/spamassin/local.cf) do not solve the problem.
++++++++
Jan 6 16:30:58 server1 spamd[439]: config: failed to parse line, skipping: rewrite_subject 1
Jan 6 16:30:58 server1 spamd[439]: config: failed to parse line, skipping: subject_tag *****SPAM*****
++++++++
I consider this a "cosmetic" bug, in that the message subjects are being rewritten for spam that is received - spamd is just logging incorrect info. Any ideas with this one? The following is a sample of my user_prefs in
/usr/local/directadmin/data/templates/custom
*******
report_safe |report_safe|
|blacklist_from|
|whitelist_from|
required_score |required_hits|
rewrite_header subject |subject_tag|
********
Any assistance/suggestions/or redirection to possible solutions is greatly appreciated!!! Thanks again!
Michael