I'm just checking on the status of this bug, because I am experiencing the same problem.
However, the symlink does not get destroyed by merely stopping and restarting the service via the init script. After the machine has booted, and I have manually created the symlink, I can restart saslauthd as many times as I wish, and my symlink remains. If my system reboots, however, the symlink disappears, and my users suddenly find themselves unable to relay mail, until I login and manually recreate the symlink. Could this have something to do with the order in which the init scripts are run at startup (as mentioned in bug 300710)? This is a serious bug for anyone trying to deploy a secure postfix mail relay.
signature.asc
Description: OpenPGP digital signature
