7 msgPostfix 2.2.5 on latest Solaris 9 x86
5 msgPostfix Relay, and Pop-before-smtp

Newb Question
\ Jeff (23 Sep 2007)
. \ Jeff (23 Sep 2007)
. \ Jeff (23 Sep 2007)
. . \ mouss (23 Sep 2007)
. . . \ Victor Duchovni (23 Sep 2007)
. . . . \ mouss (23 Sep 2007)
. \ mouss (23 Sep 2007)
. . \ Jeff (23 Sep 2007)
. . . \ mouss (23 Sep 2007)
. . . . \ Jeff (23 Sep 2007)
. . . . . \ mouss (24 Sep 2007)
. \ David B. Ferguson (23 Sep 2007)

13 msgBest defense against this?
1 msgundelivered mail problem - SOLVED
4 msgLegal local-part
3 msgvirtual_alias_domains with mysql: 'User unknown...
6 msgSubmission port (587): howto to use differente ...
5 msgWhen does smtpd_reject_unlisted_recipient kick in?
4 msgPostfix 'falling back' on sasldb? I don't want ...
3 msgNested access maps (I think ;))
3 msgSuppression of encoding bad header function in ...
4 msgRE: Catchall ??
3 msgproblem with .forward files + forwarding loops
5 msgPostfix Strange Behaviours
7 msgContent filter question, based upon auth'ed or not
28 msgMail stuck in active queue for loooong time
11 msgHow to stop a user from changing the 'From:' he...
10 msg[Semi-OT] blocked port 465, anywhere?
7 msgchroot problems on Nexenta (OpenSolaris)
Subject:Re: Newb Question
Group:Postfix-users
From:mouss
Date:24 Sep 2007


 
Jeff wrote:
>
>
> On 9/23/07 5:25 PM, "mouss" <mlist.only> wrote:
>
>> Jeff wrote:
>
>> There is no PLAIN and LOGIN here. disable cram-md5 and digest-md5,
>> enable the broken_sasl_... and restart postfix. then reconnect via
>> telnet and see if the response to EHLO contains two AUTH lines (one
>> being the "broken" one. both should contain PLAIN and LOGIN).
>>
>
> I removed all but the sasl2 conf file (the one that Postfix is using),
> removed cram-md5 and digest-md5, added PLAIN and LOGIN and logging to the
> smtpd.conf file. I also added the broken_sasl line to main.cf. I restarted
> postfix and saslauthd. Telneting, I now get:
>
> 250-AUTH PLAIN LOGIN
> 250-AUTH=PLAIN LOGIN
>
> It doesn't work, but at least this is progress. The logs say that no result
> was returned, but I checked the sql statement (again) and it works. I am
> very clear now that I don't understand what's going on. What do you think
> might be broken?
>

what do you mean by "doesn't work". please be more explicit. also show
relevant logs.

is the password in myslq in clear text? (unpatched) cyrus-sasl doesn't
support encrypted mysql paswords.

check your mysql logs and see if cyrus-sasl queries mysql and what query
it uses. run the same query. show the query and output.



© 2004-2008 readlist.com