Am Mo, den 07.06.2004 schrieb Roger Grosswiler um 13:02: > Why i use pam instead of shadow? because with shadow i did not get it running strangerwise, but it worked fine from > the beginning with pam, which does not do any difference except using one more interface (in my understanding, please > don't let me die unwise...) As you say it, I remember we already had talked about that difficulty for you a while ago. Although I still don't understand the reason. Anyway, you are right that at least in basic configuration there is no real difference between using pam or shadow as mechs with saslauthd - speaking about the default /etc/pam.d/smtp file coming with Fedora. And if you intend to not authenticate against system users, PAM is one way to configure your system, including Cyrus-IMAPd, as a sealed server. One way to do so is described here (for Postfix, can be done with other MTA too): http://linux-universe.com/HOWTO/Postfix-Cyrus-Web-cyradm-HOWTO/pam-config.html by using pam_mysql and keeping the user data in an SQL database. While that could be done too with MECH=auxprop and not using PAM. > of course you are right, just wanted to make sure, it isn't cyrus itself, that cannot connect...so i go forward step > by step... A fair way to find the trouble maker. Just wanted to remark that this setting change in /etc/sysconfig/saslauthd is not really necessary. > Roger Alexander -- Alexander Dalloz | Enger, Germany | GPG key 1024D/ED695653 1999-07-13 Fedora GNU/Linux Core 2 (Tettnang) on Athlon CPU kernel 2.6.5-1.358 Serendipity 14:06:45 up 5 days, 14:24, load average: 0.58, 0.27, 0.22
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
