Date: Mon, 12 Jun 2006 07:29:26 -0400 From: "jflowers" <jflowers@ezo.net> To: freebsd-isp@freebsd.org Subject: Re: Sendmail/SASL2/saslauthdb problem Message-ID: <20060612111724.M53249@ezo.net> In-Reply-To: <7.0.1.0.0.20060612051259.04bbfd10@szarka.org> References: <7.0.1.0.0.20060611113015.072d4698@szarka.org> <7.0.1.0.0.20060612051259.04bbfd10@szarka.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Nibbed in here without reading the rest of the thread as I just finished
debugging some dovecot SASL. On FreeBSD mmencode can't be used, even with
printf for 'auth plain' because it can't handle the null (\0) characters
required. At least I couldn't figure out how to do it. My solution was to use
perl with MIME::Base64 installed as in:
perl -MMIME::Base64 -e 'print
encode_base64("user\@domain.tld\0user\@domain.tld\0password");'
mmencode -u can be used to test the encoding as there are no nulls:
perl -MMIME::Base64 -e 'print
encode_base64("user\@domain.tld\0user\@domain.tld\0password");'
| mmencode -u
On Mon, 12 Jun 2006 05:13:17 -0400, Rob Szarka wrote
> *ahem*
>
> I would like to point out the following obvious (in retrospect)
> advice about testing smtp auth by hand:
>
> when using mmencode to translate to base64, one should
>
> printf "username" | mmencode
>
> not
>
> echo "username" | mmencode
>
> Of course, it wasn't working from my usual MUA either, originally;
> but after I fixed my problem, I didn't know it was fixed because I
> was testing with a bad username and password.
>
> *sigh*
>
> After a complete deinstall/reinstall/reconfigure didn't work, I
> caught on...
>
> _______________________________________________
> freebsd-isp@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-isp
> To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
--
Jim Flowers <jflowers@ezo.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060612111724.M53249>