Displaying 20 results from an estimated 3000 matches similar to: "postfix/smtpd[725]: fatal: no SASL authentication mechanisms"
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 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
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 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
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
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
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
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
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
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
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
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 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
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 May 05
0
confused with ssl settings and some error - need help
Internal PCI Scan on Tenable.io website. Of course after register account.
2017-04-30 9:11 GMT+02:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
> What kind of test are you running?
>
> Aki
>
> > On April 27, 2017 at 12:00 PM Poliman - Serwis <serwis at poliman.pl>
> wrote:
> >
> >
> > I turned of ssl_cipher_list in dovecot.conf file (so it's
2017 Apr 27
0
confused with ssl settings and some error - need help
I turned of ssl_cipher_list in dovecot.conf file (so it's default) but test
still gives errors:
Apr 27 08:55:06 serwer-1 dovecot: pop3-login: Error: SSL: Stacked error:
error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol
Apr 27 08:55:06 serwer-1 dovecot: pop3-login: Error: SSL: Stacked error:
error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol
Apr 27 08:55:07
2017 Apr 27
0
confused with ssl settings and some error - need help
> On April 27, 2017 at 10:55 AM Poliman - Serwis <serwis at poliman.pl> wrote:
>
>
> Thank You for answers. But:
> 1. How should be properly configured ssl_cipher_list?
ssl_cipher_list = ALL:!kRSA:!SRP:!kDHd:!DSS:!aNULL:!eNULL:!EXPORT:!DES:!3DES:!MD5:!PSK:!RC4:!ADH:!LOW at STRENGTH
To disable non-EC DH, use:
ssl_cipher_list =
2017 Apr 27
0
confused with ssl settings and some error - need help
> On April 27, 2017 at 8:12 AM Poliman - Serwis <serwis at poliman.pl> wrote:
>
>
> Hi,
> To default dovecot.conf file I added (based on found documentation):
> ssl = required
> disable_plaintext_auth = yes #change default 'no' to 'yes'
> ssl_prefer_server_ciphers = yes
> ssl_options = no_compression
> ssl_dh_parameters_length = 2048
>
2017 Apr 30
2
confused with ssl settings and some error - need help
What kind of test are you running?
Aki
> On April 27, 2017 at 12:00 PM Poliman - Serwis <serwis at poliman.pl> wrote:
>
>
> I turned of ssl_cipher_list in dovecot.conf file (so it's default) but test
> still gives errors:
> Apr 27 08:55:06 serwer-1 dovecot: pop3-login: Error: SSL: Stacked error:
> error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown