Timo Sirainen wrote on 20.07.2010:
> On 19.7.2010, at 22.59, Daniel Luttermann wrote:
>> The queries uses only "userid" instead of "username" so I think if one
>> sql field were missing it should report that "userid" could not be
>> found because the query is "FROM users WHERE userid = '%u'".
>>
On 19.7.2010, at 22.59, Daniel Luttermann wrote:
> The queries uses only "userid" instead of "username" so I think if one
> sql field were missing it should report that "userid" could not be
> found because the query is "FROM users WHERE userid = '%u'".
>
> I've not select "username" in any sql s
Anton Dollmaier wrote on 19.07.2010:
> Hi,
>> I dont' know where the field "username" should come from because I
>> don't use this field (or query).
> perhabs this is the problem?
The queries uses only "userid" instead of "username" so I think if one
sql field were missing it should report that
Hi,
I dont' know where the field "username" should come from because I
don't use this field (or query).
perhabs this is the problem? ;-)
The relevant files are:
Output of "dovecot -n" would be better, together with the additional files.
dovecot-sql.conf.ext
passw
Version: Dovecot 2.0 rc2
I'm testing Dovecot with MySQL quotas but I get always this error for
incoming mails:
tux dovecot: lmtp(4928): Error: user testu...@dlutt.de: Auth USER lookup failed
tux dovecot: auth: Error: mysql: Query failed, retrying: Unknown column
'username' in 'where clause'
I d
