From: Ian M. E. <ian...@di...> - 2011-01-21 01:19:44
|
Used to have spam_buttons working just fine. After a major server crash required an os reload, I haven't been able to get my setup to work. Using the latest spam_buttons and spamassassin. Current command line is: $is_spam_shell_command = 'sudo -u spamd /usr/bin/spamc -L spam'; I'm getting an error 74. Trying out the other commands didn't seem to work either. What steps should I take to give more pertinent information to solve this issue? Thanks! |
From: Tomas K. <to...@us...> - 2011-01-21 06:10:26
|
Ian Evans-2 wrote: > > Used to have spam_buttons working just fine. After a major server crash > required an os reload, I haven't been able to get my setup to work. > > Using the latest spam_buttons and spamassassin. Current command line is: > > $is_spam_shell_command = 'sudo -u spamd /usr/bin/spamc -L spam'; > > I'm getting an error 74. Trying out the other commands didn't seem to work > either. > > What steps should I take to give more pertinent information to solve this > issue? > Have you checked /etc/sudoers? Are you sure that program execution is not restricted in new setup? Check PHP safe mode and disabled functions. -- View this message in context: http://old.nabble.com/Error-74-on-spam_buttons-with-spamc-command-tp30725019p30726062.html Sent from the squirrelmail-plugins mailing list archive at Nabble.com. |
From: Ian M. E. <ian...@di...> - 2011-01-21 07:44:29
|
On Fri, January 21, 2011 1:10 am, Tomas Kuliavas wrote: >> Used to have spam_buttons working just fine. After a major server crash >> required an os reload, I haven't been able to get my setup to work. >> >> Using the latest spam_buttons and spamassassin. Current command line is: >> >> $is_spam_shell_command = 'sudo -u spamd /usr/bin/spamc -L spam'; >> >> I'm getting an error 74. Trying out the other commands didn't seem to >> work >> either. >> >> What steps should I take to give more pertinent information to solve >> this >> issue? >> > Have you checked /etc/sudoers? apache ALL=(spamd) NOPASSWD: /usr/bin/sa-learn, /usr/bin/spamassassin, /usr/bin/spamc > Are you sure that program execution is not restricted in new setup? Check > PHP safe mode and disabled functions. safe mode is off. |
From: Tomas K. <to...@us...> - 2011-01-22 21:06:49
|
Ian Evans-2 wrote: > > On Fri, January 21, 2011 1:10 am, Tomas Kuliavas wrote: >>> Used to have spam_buttons working just fine. After a major server crash >>> required an os reload, I haven't been able to get my setup to work. >>> >>> Using the latest spam_buttons and spamassassin. Current command line is: >>> >>> $is_spam_shell_command = 'sudo -u spamd /usr/bin/spamc -L spam'; >>> >>> I'm getting an error 74. Trying out the other commands didn't seem to >>> work >>> either. >>> >>> What steps should I take to give more pertinent information to solve >>> this >>> issue? >>> >> Have you checked /etc/sudoers? > > apache ALL=(spamd) NOPASSWD: /usr/bin/sa-learn, /usr/bin/spamassassin, > /usr/bin/spamc > >> Are you sure that program execution is not restricted in new setup? Check >> PHP safe mode and disabled functions. > > safe mode is off. > Can you set sb_debug to 1 in spam_buttons plugin configuration and show executed command? Error 74 comes from spamc. It is EX_IOERR 74 input/output error. Either file was unreadable or executed command is broken. -- View this message in context: http://old.nabble.com/Error-74-on-spam_buttons-with-spamc-command-tp30725019p30738739.html Sent from the squirrelmail-plugins mailing list archive at Nabble.com. |
From: Ian M. E. <ian...@di...> - 2011-01-22 21:35:12
|
On Sat, January 22, 2011 4:06 pm, Tomas Kuliavas wrote: > Ian Evans-2 wrote: >> >> On Fri, January 21, 2011 1:10 am, Tomas Kuliavas wrote: >>>> Used to have spam_buttons working just fine. After a major server >>>> crash >>>> required an os reload, I haven't been able to get my setup to work. >>>> >>>> Using the latest spam_buttons and spamassassin. Current command line >>>> is: >>>> >>>> $is_spam_shell_command = 'sudo -u spamd /usr/bin/spamc -L spam'; >>>> >>>> I'm getting an error 74. Trying out the other commands didn't seem to >>>> work >>>> either. >>>> >>>> What steps should I take to give more pertinent information to solve >>>> this >>>> issue? >>>> >>> Have you checked /etc/sudoers? >> >> apache ALL=(spamd) NOPASSWD: /usr/bin/sa-learn, /usr/bin/spamassassin, >> /usr/bin/spamc >> >>> Are you sure that program execution is not restricted in new setup? >>> Check >>> PHP safe mode and disabled functions. >> >> safe mode is off. >> > Can you set sb_debug to 1 in spam_buttons plugin configuration and show > executed command? COMMAND USED TO REPORT: sudo -u spamd /usr/bin/spamc -L spam < ../data//sb_tmp_764171_1295731904 Just noted the double '//' after data. Could that be the problem and if so where would I fix that path? |
From: Tomas K. <to...@us...> - 2011-01-22 22:12:11
|
2011.01.22 23:35 Ian M. Evans rašė: > On Sat, January 22, 2011 4:06 pm, Tomas Kuliavas wrote: >> Ian Evans-2 wrote: >>> >>> On Fri, January 21, 2011 1:10 am, Tomas Kuliavas wrote: >>>>> Used to have spam_buttons working just fine. After a major server >>>>> crash >>>>> required an os reload, I haven't been able to get my setup to work. >>>>> >>>>> Using the latest spam_buttons and spamassassin. Current command line >>>>> is: >>>>> >>>>> $is_spam_shell_command = 'sudo -u spamd /usr/bin/spamc -L spam'; >>>>> >>>>> I'm getting an error 74. Trying out the other commands didn't seem to >>>>> work >>>>> either. >>>>> >>>>> What steps should I take to give more pertinent information to solve >>>>> this >>>>> issue? >>>>> >>>> Have you checked /etc/sudoers? >>> >>> apache ALL=(spamd) NOPASSWD: /usr/bin/sa-learn, /usr/bin/spamassassin, >>> /usr/bin/spamc >>> >>>> Are you sure that program execution is not restricted in new setup? >>>> Check >>>> PHP safe mode and disabled functions. >>> >>> safe mode is off. >>> >> Can you set sb_debug to 1 in spam_buttons plugin configuration and show >> executed command? > > COMMAND USED TO REPORT: > sudo -u spamd /usr/bin/spamc -L spam < ../data//sb_tmp_764171_1295731904 > > Just noted the double '//' after data. Could that be the problem and if so > where would I fix that path? plugins/spam_buttons/functions.php line 504 $tempFile = $attachment_dir . '/sb_tmp_' . $messageID . '_' . $timestamp; $attachment_dir and $data_dir have trailing / in standard SquirrelMail configuration. -- Tomas |
From: Ian M. E. <ian...@di...> - 2011-01-22 23:54:56
|
On Sat, January 22, 2011 5:08 pm, Tomas Kuliavas wrote: [snip] > plugins/spam_buttons/functions.php line 504 > > $tempFile = $attachment_dir . '/sb_tmp_' . $messageID . '_' . $timestamp; > > $attachment_dir and $data_dir have trailing / in standard SquirrelMail > configuration. Hmm...my plugins/spam_buttons/functions.php only has 188 lines. Version is 2.3.1 |
From: Tomas K. <to...@us...> - 2011-01-23 06:14:40
|
Ian Evans-2 wrote: > > On Sat, January 22, 2011 5:08 pm, Tomas Kuliavas wrote: > [snip] >> plugins/spam_buttons/functions.php line 504 >> >> $tempFile = $attachment_dir . '/sb_tmp_' . $messageID . '_' . $timestamp; >> >> $attachment_dir and $data_dir have trailing / in standard SquirrelMail >> configuration. > > Hmm...my plugins/spam_buttons/functions.php only has 188 lines. Version is > 2.3.1 > plugins/spam_buttons/report.php line 1682 -- View this message in context: http://old.nabble.com/Error-74-on-spam_buttons-with-spamc-command-tp30725019p30740316.html Sent from the squirrelmail-plugins mailing list archive at Nabble.com. |
From: Ian M. E. <ian...@di...> - 2011-01-23 06:26:24
|
On Sun, January 23, 2011 1:14 am, Tomas Kuliavas wrote: > > > Ian Evans-2 wrote: >> >> On Sat, January 22, 2011 5:08 pm, Tomas Kuliavas wrote: >> [snip] >>> plugins/spam_buttons/functions.php line 504 >>> >>> $tempFile = $attachment_dir . '/sb_tmp_' . $messageID . '_' . >>> $timestamp; >>> >>> $attachment_dir and $data_dir have trailing / in standard SquirrelMail >>> configuration. >> >> Hmm...my plugins/spam_buttons/functions.php only has 188 lines. Version >> is >> 2.3.1 >> > plugins/spam_buttons/report.php line 1682 Got it. Thanks! |
From: Paul L. <pa...@sq...> - 2011-01-25 01:36:34
|
2011/1/22 Ian M. Evans <ian...@di...>: > On Sun, January 23, 2011 1:14 am, Tomas Kuliavas wrote: >> >> >> Ian Evans-2 wrote: >>> >>> On Sat, January 22, 2011 5:08 pm, Tomas Kuliavas wrote: >>> [snip] >>>> plugins/spam_buttons/functions.php line 504 >>>> >>>> $tempFile = $attachment_dir . '/sb_tmp_' . $messageID . '_' . >>>> $timestamp; >>>> >>>> $attachment_dir and $data_dir have trailing / in standard SquirrelMail >>>> configuration. >>> >>> Hmm...my plugins/spam_buttons/functions.php only has 188 lines. Version >>> is >>> 2.3.1 >>> >> plugins/spam_buttons/report.php line 1682 > > Got it. Thanks! Please clarify -- did the removal of the extra slash solve the error you were seeing? -- Paul Lesniewski SquirrelMail Team Please support Open Source Software by donating to SquirrelMail! http://squirrelmail.org/donate_paul_lesniewski.php |
From: Ian M. E. <ian...@di...> - 2011-01-25 01:45:29
|
On Mon, January 24, 2011 8:36 pm, Paul Lesniewski wrote: > 2011/1/22 Ian M. Evans <ian...@di...>: >> On Sun, January 23, 2011 1:14 am, Tomas Kuliavas wrote: >>> Ian Evans-2 wrote: >>>> On Sat, January 22, 2011 5:08 pm, Tomas Kuliavas wrote: >>>> [snip] >>>>> plugins/spam_buttons/functions.php line 504 >>>>> $tempFile = $attachment_dir . '/sb_tmp_' . $messageID . '_' . >>>>> $timestamp; >>>>> $attachment_dir and $data_dir have trailing / in standard >>>>> SquirrelMail >>>>> configuration. >>>> Hmm...my plugins/spam_buttons/functions.php only has 188 lines. >>>> Version >>>> is >>>> 2.3.1 >>> plugins/spam_buttons/report.php line 1682 >> Got it. Thanks! > Please clarify -- did the removal of the extra slash solve the error > you were seeing? Yes, it did. Everything is working fine now. |