From: (no name) (no email)
Date: Fri Jan 02 2004 - 01:13:43 EST
Aha! I didn't understand what "chroot'ed" meant ... Now I gather that,
because "smtpd" DOES run "chroot'ed", it looks for
"/var/spool/postfix/etc/krb5.keytab", which doesn't exist.
SO, my options appear to be, 1) not running "smtpd" "chroot'ed", or 2)
creating "/var/spool/postfix/etc/krb5.keytab". I've tried to discover
how the files in "/var/spool/postfix" are maintained ... What must I do
to ensure "/var/spool/postfix/etc/krb5.keytab" is kept current with
"/etc/krb5.keytab"?
Thanks very much for your help, Andreas; you were spot-on.
Jack
On Jan 1, 2004, at 4:08 AM, Andreas Winkelmann wrote:
> Am Mittwoch, 31. Dezember 2003 18:58 schrieb :
>
>> Dec 31 09:54:06 wum postfix/smtpd[3227]: connect from
>> fis.lat[192.168.179.43]
>> Dec 31 09:54:07 wum postfix/smtpd[3227]: warning: SASL authentication
>> failure: GSSAPI Error: Miscellaneous failure (No such file or
>> directory)
>> Dec 31 09:54:07 wum postfix/smtpd[3227]: warning:
>> fis.lat[192.168.179.43]: SASL GSSAPI authentication failed
>>
>> Anyone know how to determine which file or directory is not such?
>
> Please check, if smtpd runs chroot'ed.
>
> # grep smtpd /etc/postfix/master.cf
>
> --
> Andreas
>
>
|
|
|