Vincent Lefevre wrote: > The problem comes from the fact that famd chooses a random port at > startup.
Just to be clear are you saying that famd picked port 783 randomly at startup? > I don't know what is the policy for port selection, but either > spamd should choose a different port until it succeeds, or (if > ports are supposed to be fixed) this should be seen as a critical > bug of famd, because its choice potentially breaks other packages > (like spamassassin). Look in /etc/services and you will find that port 783 is allocated in Debian to spamd. That is the port that spamc will use to contact the spamd. It has been coordinated. Bob -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
