> I was surprised that directly contacting people worked at all, but since
> it has I thought I'd allow it and hope it wouldn't piss off too many
> people.. There won't be more than that one mail, which you're free to just
> ignore.
>
> If we get enough funding we can hire more people to work on D
>> > username NUL username NUL password
>>
>> It's username then password.
>
> What about the NUL characters in the middle? Those are important.
U... I wrote a quick perl script to decrypt the string and
print it out... I'll have to look at how to tell if there are
NUL chars in there.
>>
> So it's either
>
> NUL username NUL password
>
> or
>
> username NUL username NUL password
It's username then password.
> Wonder if it has to do with a single process doing multiple lookups.
> That's the main difference compared to SSH and pretty much everything
> else.
I upgraded the server
> Did you check with auth_debug_passwords=yes what the password is? v1.2
> doesn't seem to log it clearly, but by base64 decoding resp= value you
> could see it.
Hi Timo,
Well, I cranked the debug back up all the way and captured the
password. After whipping up a quick perl script to decode
>> And sure enough, there it is:
>>
>>
>> Aug 3 12:15:23 fusion dovecot: auth(default): client in: AUTH 1
>> PLAIN service=imapsecured lip=127.0.0.1 rip=127.0.0.1
>> lport=143
>> rport=19068 resp=
>> Aug 3 12:15:23 fusion dovecot: auth(default): bsdauth(benny,127.0.0.1):
>> loo
>>The only error I get in the mail log is:
>>
>> Aug 3 11:00:09 fusion dovecot: imap-login: Aborted login (auth failed,
>> 1
>> attempts): user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1,
>> secured
>
> Get it to log more with auth_verbose=yes, and perhaps even
> auth_debug_passwords=yes.
Hey folks,
I recently upgraded my mail server from an older OpenBSD -CURRENT
snapshot to the latest (Aug 1). As part of this upgrade, I updated
all of my packages to their latest versions.
Since this upgrade, dovecot has begun failing to authenticate
intermittently. I use it primarily fo
