Re: Postfix + SASL problem "no SASL authentication mechanisms"

To: Debian user list <debian-user@lists.debian.org>
Subject: Re: Postfix + SASL problem "no SASL authentication mechanisms"
From: Cliff Flood <cliph@cli.ph>
Date: Fri, 22 Apr 2005 17:49:20 +0100
Message-id: <[🔎] 42692B10.4090104@cli.ph>
In-reply-to: <[🔎] 426921C9.50506@cli.ph>
References: <[🔎] 42691098.6020300@cli.ph> <[🔎] 200504221746.33463.ike@kni.univ.szczecin.pl> <[🔎] 426921C9.50506@cli.ph>

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 nowprotected 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/

Reply to:

Follow-Ups:
- Re: Postfix + SASL problem "no SASL authentication mechanisms"
  - From: Mark Roach <mrroach@okmaybe.com>

References:
- Postfix + SASL problem "no SASL authentication mechanisms"
  - From: Cliff Flood <cliph@cli.ph>
- Re: Postfix + SASL problem "no SASL authentication mechanisms"
  - From: Lech Karol Pawłaszek <ike@kni.univ.szczecin.pl>
- Re: Postfix + SASL problem "no SASL authentication mechanisms"
  - From: Cliff Flood <cliph@cli.ph>

Prev by Date: Re: upgrade from 2.4 to 2.6: unknown symbols
Next by Date: Re: using cron
Previous by thread: Re: Postfix + SASL problem "no SASL authentication mechanisms"
Next by thread: Re: Postfix + SASL problem "no SASL authentication mechanisms"
Index(es):
- Date
- Thread