2006-05-03T02:40:46Ztag:blog.limedaley.com,2018:/isso/thread/post/smtp-authenticationtag:blog.limedaley.com,2018:/isso/168/5582006-05-03T02:40:46Zjondaley<p>You also need to create the /var/spool/postfix/var/run/saslauthd directory, if it doesn't already exist.</p>tag:blog.limedaley.com,2018:/isso/168/5572005-11-21T14:13:47Zjondaley<p>Today I remembered that saslauthd hasn't been able to shutdown properly, so when I did the latest Debian update, it failed to restart.</p> <p>I added these bits of code to make it work properly:</p> <p>/etc/defaults/saslauthd<br> +PIDFILE=&quot;/var/spool/postfix/var/run/saslauthd/saslauthd.pid&quot;</p> <p>/etc/init.d/saslauthd<br> -PIDFILE=&quot;/var/run/${NAME}/saslauthd.pid&quot;<br> +if [ &quot;x${PIDFILE}&quot; = &quot;x&quot; ]; then</p> <ul> <li><pre><code> PIDFILE=&quot;/var/run/${NAME}/saslauthd.pid&quot;</code></pre> +fi</li> </ul> <p>Saslauthd hadn't been using the Debian PIDFILE parameter, and so Debian tried to find /var/run/saslauthd/saslauthd.pid, but it didn't exist, so thought it wasn't running, and then when it tried to start it again, it got this error:<br> invoke-rc.d: initscript saslauthd, action &quot;start&quot; failed.</p>tag:blog.limedaley.com,2018:/isso/168/5562005-11-09T00:34:23Zjondaley<p>I read <a href="http://www.vanemery.com/Protocols/SMTP/smtp.html" rel="nofollow noopener">here</a> that port 465 is the old port for smtps stuff, and 587 is mostly only useful for getting around ISPs who block port 25, and that any reasonable new client or server will do both plain and SSL SMTP on port 25, so perhaps I actually did it right.</p>