Bug 169390
| Summary: | Dovecot requires saslauthd to work but does not declare that | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Paolo Campegiani <p.campegiani> |
| Component: | dovecot | Assignee: | John Dennis <jdennis> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | Keywords: | FutureFeature |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2005-09-27 22:56:23 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Your statement that dovecot requires salauthd to work is not correct. Dovecot may require saslauthd if it is configured to use sasl. Also, saslauthd can be utilized by any number of other sasl clients besides just dovecot. Therefore it would not be correct for dovecot to manage saslauthd, either by starting it or configuring it. However, I do have sympathy for your frustration with understanding the whole gamut of authtentication issues which arise when setting up various servers that require authentication. The information is out there, but its sometimes hard to find and put together into a cohesive whole with a simple step by step receipe. We should provide better documentation in this area. But please note that authentication applies to many services besides dovecot, servers may share authentication or may keep private authentication information, and there are wide variety of authentication databases, mechanisms, and ways to configure individual servers to use them. Alas, this documentation would probably be an entire book, which is why it probably hasn't been done yet. You can find dovecot documentation on authentication here: /usr/share/doc/dovecot-*/auth.txt http://wiki.dovecot.org/moin.cgi/Authentication I'm going to close this bug report because its not really a dovecot issue, but please feel free to either create a new bug report specific to documentation. Maybe one day one of us will write the book on authentication ;-) |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.0.6-1.2.fc3 Firefox/1.0.6 Description of problem: This is not a bug, more a lack in documentation or diagnostic messages. I've encountered this problem when I was required to fix a IMAP server, running dovecot, which timeouts every IMAP-POP3 login. I realized the problem was saslauthd wasn't running on the machine, but I didn't find any clue in /var/log/messages or /var/log/maillog, I was just lucky to find the problem :) I think you should find a way to enable saslauthd when dovecot starts (maybe changing the /etc/init.d scripts), or at least print some help information in a log file. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. Stop saslauthd 2. Start dovecot 3. Try to download your mail Actual Results: Login expires after a timeout, with no messages in a log file. Expected Results: At least an error message ("saslauthd not working, unable to authenticate") should be found. Additional info: