On 28/05/14 19:41, Wietse Venema wrote: > You move sockets, but how do you know that the SASL library (invoked > by smtpd) is really connected to the saslauthd process?
I actually created the appropriate symlinks to avoid path breaking. Fact is : if it was related to an non-existant process/file (which Postfix wouldn't connect to), I would get more than just "authentication failure". On 28/05/14 19:49, Viktor Dukhovni wrote: > You're probably better off with dovecot, it is a less steep learning > curve. Cyrus SASL is substantially more configurable, at great > cost in interface complexity. Now that's a far too simple idea to my ears. I've already set up quite a few Postfix+Dovecot installs, and this is not what I'm trying to achieve here. I understand the problem you're mentioning (mixing up server/client-side configurations), now that was silly of me. I may have got confused between several references online, but is there a simple "universal?" way to set up authentication support for outgoing email, without setting up a full incoming email service ? Actually, I only need a few addresses for some web applications to send emails through our server... When I asked the devs if they needed mailboxes, full setup, they said no, so they're gonna stick to it. Thank you both!
