Displaying 20 results from an estimated 3000 matches similar to: "Probs authenticating to Dovecot"
2017 Feb 01
2
Dovecot auth-worker error after cram-md5 auth
I haven't doveadm logs in /var/log/. Are they default in another place or
maybe should I turn on something?
My config (default passdb block and auth_mechanisms, nothing more changed):
root at vps342401:/etc/dovecot# doveconf -n
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS
auth_mechanisms = plain login
listen = *,[::]
log_timestamp =
2017 Feb 01
2
Dovecot auth-worker error after cram-md5 auth
I always restart dovecot after change config. ;) Sure, I commented out
added two lines by me, restarted dovecot and here it is:
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS
auth_mechanisms = plain login cram-md5
listen = *,[::]
log_timestamp = "%Y-%m-%d %H:%M:%S "
mail_max_userip_connections = 100
mail_plugins = " quota"
2017 Feb 01
2
Dovecot auth-worker error after cram-md5 auth
This is debug log files in syslog:
Feb 1 07:10:25 vps342401 dovecot: auth: Debug: client passdb out:
CONT#0112#011PDAxODg3ODIzMTUwMzgxNzMuMTQ4NTkyOTQyNUB2cHMzNDI0MDEub3ZoLm5ldD4=
Feb 1 07:10:26 vps342401 dovecot: auth: Debug: client in: CONT<hidden>
Feb 1 07:10:26 vps342401 dovecot: auth-worker(27069): Debug: sql(
do_not_reply at example.com,12.173.211.32): query: SELECT email as user,
2017 Feb 01
2
Dovecot auth-worker error after cram-md5 auth
Is there any strange thing in these config lines?
2017-02-01 9:40 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
> doveadm log errors can be helpful too
>
>
> On 01.02.2017 10:25, Poliman - Serwis wrote:
> > I can check each logs, I have root privileges.
> >
> > 2017-02-01 9:04 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
> >
> >> Can
2017 Feb 01
2
Dovecot auth-worker error after cram-md5 auth
It still use:
passdb {
driver = passwd-file
args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
}
When I delete above and delete "cram-md5" in auth_mechanisms it still not
working.
2017-02-01 8:45 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
> You are probably wanting to do
> passdb {
> driver = passwd-file
> args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
2017 Feb 01
3
Dovecot auth-worker error after cram-md5 auth
Default it was: "auth_mechanisms = plain login" and I added cram-md5.
After restart all work perfectly. But after I added:
driver = passwd-file
args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
I can't set default lines because I got error. Please tell me which lines
should be changed to resolve this issue. Should I remove "login" from
auth_mechanism
2017 Feb 01
3
Dovecot auth-worker error after cram-md5 auth
I can check each logs, I have root privileges.
2017-02-01 9:04 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
> Can you check your logs?
>
> Aki
>
>
> On 01.02.2017 10:02, Poliman - Serwis wrote:
> > When I used backup copy of the dovecot.conf file I have this same error.
> So
> > I think that maybe something was written to database? I really would
>
2017 Feb 01
3
Dovecot auth-worker error after cram-md5 auth
When I used backup copy of the dovecot.conf file I have this same error. So
I think that maybe something was written to database? I really would point
out that I only added
passdb {
driver = passwd-file
args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
}
and comment out from above block default lines
#args = /etc/dovecot/dovecot-sql.conf
#driver = sql
And in auth_mechanisms add line
2017 Jan 31
3
Dovecot auth-worker error after cram-md5 auth
I set up cram-md5 using this tutorial
https://wiki2.dovecot.org/HowTo/CRAM-MD5 in /etc/dovecot/dovecot.conf in
passdb code block:
listen = *,[::]
protocols = imap pop3
#auth_mechanisms = plain login cram-md5
auth_mechanisms = cram-md5 plain login
#dodana nizej linia
ssl = required
disable_plaintext_auth = yes
log_timestamp = "%Y-%m-%d %H:%M:%S "
mail_privileged_group = vmail
2017 Feb 03
0
postfix/smtpd[725]: fatal: no SASL authentication mechanisms
I haven't doveadm logs in /var/log/. Are they default in another place or
maybe should I turn on something?
My config (default passdb block and auth_mechanisms, nothing more changed):
root at vps342401:/etc/dovecot# doveconf -n
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS
auth_mechanisms = plain login
listen = *,[::]
log_timestamp = "%Y-%m-%d
2017 Feb 01
0
Dovecot auth-worker error after cram-md5 auth
Because cram-md5 needs the user's password for calculating responses, it
cannot work with hashed passwords (one-way encrypted). The only
supported password schemes are PLAIN and CRAM-MD5.
Aki
On 01.02.2017 09:33, Poliman - Serwis wrote:
> I always restart dovecot after change config. ;) Sure, I commented out
> added two lines by me, restarted dovecot and here it is:
>
> # 2.2.9:
2017 Feb 01
0
Dovecot auth-worker error after cram-md5 auth
On 01.02.2017 08:18, Poliman - Serwis wrote:
> This is debug log files in syslog:
> Feb 1 07:10:25 vps342401 dovecot: auth: Debug: client passdb out:
> CONT#0112#011PDAxODg3ODIzMTUwMzgxNzMuMTQ4NTkyOTQyNUB2cHMzNDI0MDEub3ZoLm5ldD4=
> Feb 1 07:10:26 vps342401 dovecot: auth: Debug: client in: CONT<hidden>
> Feb 1 07:10:26 vps342401 dovecot: auth-worker(27069): Debug: sql(
>
2017 Feb 01
0
Dovecot auth-worker error after cram-md5 auth
You are probably wanting to do
passdb {
driver = passwd-file
args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
}
passdb {
driver = sql
args = /etc/dovecot/dovecot-sql.conf
}
Why you want to use cram-md5 is beyond me, because using SSL is much
more safer.
Aki
On 01.02.2017 09:41, Poliman - Serwis wrote:
> Default it was: "auth_mechanisms = plain login" and I added cram-md5.
2017 Feb 01
0
Dovecot auth-worker error after cram-md5 auth
Are you still trying to authenticate using cram-md5?
Aki
On 01.02.2017 09:51, Poliman - Serwis wrote:
> It still use:
> passdb {
> driver = passwd-file
> args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
> }
>
> When I delete above and delete "cram-md5" in auth_mechanisms it still not
> working.
>
> 2017-02-01 8:45 GMT+01:00 Aki Tuomi <aki.tuomi at
2017 Feb 01
0
Dovecot auth-worker error after cram-md5 auth
Can you check your logs?
Aki
On 01.02.2017 10:02, Poliman - Serwis wrote:
> When I used backup copy of the dovecot.conf file I have this same error. So
> I think that maybe something was written to database? I really would point
> out that I only added
> passdb {
> driver = passwd-file
> args = scheme=cram-md5 /etc/dovecot/cram-md5.pwd
> }
>
> and comment out from
2017 Feb 01
0
Dovecot auth-worker error after cram-md5 auth
doveadm log errors can be helpful too
On 01.02.2017 10:25, Poliman - Serwis wrote:
> I can check each logs, I have root privileges.
>
> 2017-02-01 9:04 GMT+01:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
>
>> Can you check your logs?
>>
>> Aki
>>
>>
>> On 01.02.2017 10:02, Poliman - Serwis wrote:
>>> When I used backup copy of the
2017 Feb 02
0
Dovecot auth-worker error after cram-md5 auth
I haven't doveadm logs in /var/log/. Are they default in another place or
maybe should I turn on something?
My config (default passdb block and auth_mechanisms, nothing more changed):
root at vps342401:/etc/dovecot# doveconf -n
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS
auth_mechanisms = plain login
listen = *,[::]
log_timestamp = "%Y-%m-%d
2015 Mar 22
2
Error after setting up fts /solr for Open-Xchange
Hi List,
i have tried to get fts / solr running with virtual all folder with
Open-Xchange.
I followed a pretty well written howto from Open-Xchanges Intranet, and
i first thought everything was running smooth, as the first one or two
searches were successful. However now whenever i try to search again
for something in the virtual "all folders" Open-Xchange tells me:
*Error*
2019 Mar 28
2
dovecot mailing list stopped delivering mail
Strangest thing. Since some time Marts 25. I'm no longer receiving mails
from the dovecot mailing list server. Mails from other sources are
behaving fine.
Instead I'm just seing
Mar 26 08:27:54 dna01 postfix/smtpd[107746]: Anonymous TLS connection
established from talvi.dovecot.org[94.237.25.159]: TLSv1.2 with cipher
ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)
Mar 26 08:27:54 dna01
2015 Mar 28
2
Error after setting up fts /solr for Open-Xchange
Am 28.03.2015 um 10:42 schrieb zucca at systemschmiede.com:
> Hi everyone,
>
> may i jolt this again please...still found no solution at all to this
> really.
> Thank you very much, i appreciate your help!
> Cheers
> Sascha
a good idea might be upgrade to recent, before do more debug
Timo Sirainen <tss at iki.fi> [Thu, 12 Mar 2015 17:41:05 +0200] rev 18340
Released