search for: sogonativeoutlookconfigurationguide

...ould have nopassword=y set in the first place, so it seems the simplest way to eliminate this problem is to take that out and have a secure environment for sending mail. Yes, however, for SOGo with Native Outlook compatibility or SAML logon, the config is required. (https://sogo.nu/files/docs/v2/SOGoNativeOutlookConfigurationGuide.html) Thanks, MJ

...#39;nopassword=y' does. I'm guessing this is an attempt to allow logging in from localhost without password, but I'd use master password (for applications or webmails), or Yes, the config is taken from the SOGo configuration guide, which can be seen here: https://sogo.nu/files/docs/v2/SOGoNativeOutlookConfigurationGuide.html Yes, but we have args = nopassword=y allow_nets=127.0.0.1/32 so it should only allow passwordless logins from localhost, right..? And in "Debug: static(username,1.2.3.4,<g2/rF+ZnjAAu5ceg>): Allowing any password" 1.2.3.4 is NOT localhost... (obviously 1.2.3.4 is not the *re...

...; does. I'm guessing this is an attempt to allow logging in from localhost without password, but I'd use master password (for applications or webmails), or > > Yes, the config is taken from the SOGo configuration guide, which can be > seen here: > https://sogo.nu/files/docs/v2/SOGoNativeOutlookConfigurationGuide.html > > Yes, but we have args = nopassword=y allow_nets=127.0.0.1/32 > so it should only allow passwordless logins from localhost, right..? > > And in "Debug: static(username,1.2.3.4,<g2/rF+ZnjAAu5ceg>): Allowing any > password" 1.2.3.4 is NOT localhost... >...

ok, fyi: I have now also tested/confirmed this, while looking at the logs, and indeed: Even when the connection is denied because of a wrong password, the message "Allowing any password" is showing up in the logs. Perhaps it is because we have set debug options: > auth_debug = yes > auth_debug_passwords = yes > auth_verbose = yes It would be nice if the "Allowing any

On 2018-03-22 (02:30 MDT), mj <lists at merit.unu.edu> wrote: > > Yes, however, for SOGo with Native Outlook compatibility or SAML logon, the config is required. > > (https://sogo.nu/files/docs/v2/SOGoNativeOutlookConfigurationGuide.html) I don't know what that is, but that is a terrible requirement that makes me very suspicious someone is being either lazy or intentionally breaking security for nefarious purposes. I'd walk away. -- Lister: What d'ya think of Betty? Cat: Betty Rubble? Well, I would go with Betty...

...>> place, so it seems the simplest way to eliminate this problem is to >> take that out and have a secure environment for sending mail. > > Yes, however, for SOGo with Native Outlook compatibility or SAML > logon, the config is required. > > (https://sogo.nu/files/docs/v2/SOGoNativeOutlookConfigurationGuide.html) > > Thanks, > MJ I have no idea *WHY* it is required by SOGo. It does not make sense. Aki

Hi, I noticed the following in the logs of our debian wheezy server: > Mar 21 07:13:47 mail dovecot: auth: Debug: ldap(username,1.2.3.4,<g2/rF+ZnjAAu5ceg>): bind search: base=CN=Users, DC=samba, DC=company, DC=com filter=(&(objectclass=person)(sAMA > ccountName=username)(!(userAccountControl=514))) > Mar 21 07:13:47 mail dovecot: auth: Debug: