Bug 78102 - /usr/ports/mail/qmail-scanner doesn't detect spamassassin correctly in all cases
Summary: /usr/ports/mail/qmail-scanner doesn't detect spamassassin correctly in all cases
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-26 01:30 UTC by Will Saxon
Modified: 2005-06-01 20:24 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Will Saxon 2005-02-26 01:30:17 UTC
      The existing patch to the qmail-scanner configure script assumes "--socketpath=/path/to/socket" is the only valid way to specify the unix socket for spamd. "--socketpath /path/to/socket" also works.

Fix: 

change:

+               SPAMD_SOCKET=`ps auxwww 2>/dev/null|egrep 'spamd.*socket'|grep -v grep|sed -e 's/^.*socketpath=//'|awk '{print $1}'`

to

+               SPAMD_SOCKET=`ps auxwww 2>/dev/null|egrep 'spamd.*socket'|grep -v grep|sed -e 's/^.*socketpath[\ |=]//'|awk '{print $1}'`

in files/patch-configure
How-To-Repeat:       start spamd with '--socketpath /path/to/socket' and then try to install qmail-scanner. It will complain about spamassassin not being set up right and it ignores spamassassin.
Comment 1 Volker Stolz freebsd_committer freebsd_triage 2005-03-08 12:57:51 UTC
Dear maintainer, please look into this issue!

Volker
Comment 2 Volker Stolz freebsd_committer freebsd_triage 2005-03-08 12:58:17 UTC
State Changed
From-To: open->feedback

Forwarded PR to maintainer
Comment 3 Florent Thoumie freebsd_committer freebsd_triage 2005-06-01 20:24:03 UTC
State Changed
From-To: feedback->closed

Committed, thanks!