Re: Postfix + SASL problem "no SASL authentication mechanisms"
From: Cliff Flood (cliph_at_cli.ph)
Date: 04/22/05
- Previous message: Monique Y. Mudama: "Re: upgrade from 2.4 to 2.6: unknown symbols"
- In reply to: Cliff Flood: "Re: Postfix + SASL problem "no SASL authentication mechanisms""
- Next in thread: Mark Roach: "Re: Postfix + SASL problem "no SASL authentication mechanisms""
- Reply: Mark Roach: "Re: Postfix + SASL problem "no SASL authentication mechanisms""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 22 Apr 2005 17:49:20 +0100 To: Debian user list <debian-user@lists.debian.org>
Cliff Flood wrote, on 04/22/05 17:09:
> Where am I going wrong?
Ok, I figured it out mostly, postfix was unable to read the
/var/run/saslauthd dir so I added 'postfix' to the 'sasl' group and
'plain' login works now!
For some reason the *-md5 logins dont work but as the traffic is now
protected using TLS I'm not too worried about it.
Would anyone know why digest-md5 and cram-md5 as login mechanisms fail?
-- Cliph/ff http://chicks-dig-unix.net/ -- To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
- Previous message: Monique Y. Mudama: "Re: upgrade from 2.4 to 2.6: unknown symbols"
- In reply to: Cliff Flood: "Re: Postfix + SASL problem "no SASL authentication mechanisms""
- Next in thread: Mark Roach: "Re: Postfix + SASL problem "no SASL authentication mechanisms""
- Reply: Mark Roach: "Re: Postfix + SASL problem "no SASL authentication mechanisms""
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|