Displaying 3 results from an estimated 3 matches for "staticpassword".
2018 Mar 22
2
why is dovecot "Allowing any password"
On 03/22/2018 09:34 AM, Aki Tuomi wrote:
> I have no idea*WHY* it is required by SOGo. It does not make sense.
Well, the thing is: SOGo has this ability to behave like a *real*
exchange server, as if it's running on a windows server. And this
enables Outlook to connect to it like it would to an exchange server.
(so: not in imap mode, and not using regular username/password
2015 Jun 03
1
Misleading SSL/TLS Log Messages
...ond to last line, which indicates I never tried to log in, correctly
states that I used TLS. All the lines for SSL debugging, though, state I
used SSL or SSLv3.
This is a test setup, so it accepts any mail from @example.com addresses
over LMTP and allows any user to connect with the password
"staticpassword". Here's the output of "dovecot -n":
# 2.2.15: /usr/local/etc/dovecot/dovecot.conf
# OS: Darwin 14.3.0 x86_64 hfs
default_client_limit = 50
default_internal_user = _dovecot
default_login_user = _dovenull
default_process_limit = 10
listen = 127.0.0.1
mail_gid = admin
mail_locati...
2018 Mar 22
0
why is dovecot "Allowing any password"
...the regular
> username/unknownpassword into username*master/masterpassword, and get
> rid of the 127.0.0.1 passwordless listener.
>
> Right?
>
> But SOGo doesn't do that. (afaik)
>
> MJ
I would recommend using master password (that is, replace nopassword=y
with password=staticpassword). I know that from localhost perspective
this isn't much different, but it will reduce accidents.
Aki