[Bug 4723] New: spamd doesn't see dccifd daemon if started first

[bu...@bugzilla.spamassassin.org]

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4723

           Summary: spamd doesn't see dccifd daemon if started first
           Product: Spamassassin
           Version: 3.0.4
          Platform: All
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P5
         Component: spamc/spamd
        AssignedTo: dev@spamassassin.apache.org
        ReportedBy: bugzilla@johnlevine.com


There's two DCC interfaces, the fast dccifd daemon and the slow
dccproc.  But if you use spamd and start it before dccifd, then spamd
won't see the socket that dccifd provides and will fall back to dccproc.

Would it be hard to special case the dcc check to
recheck for dccifd inside spamd, or add an option to try harder to find
it?  It's basically just open("/tmp/dccsocket"), which should be pretty
fast.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

[Bug 4723] spamd doesn't see dccifd daemon if started first

[bu...@bugzilla.spamassassin.org]

http://issues.apache.org/SpamAssassin/show_bug.cgi?id=4723


sidney@sidney.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




------- Additional Comments From sidney@sidney.com  2006-04-16 00:17 -------
John, I came across your old bug report while looking at DCC issues and the DCC
mailing list archives. I think that I've tested this properly in SpamAssassin
3.1.1 and found that spamd rechecks for dccifd with every message.

I'm closing this as FIXED, but could you please verify that it really is and
re-open it if I'm wrong about that?




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.