[SOGo] BTS activities for Saturday, July 25 2015
Title: BTS activities for Saturday, July 25 2015 BTS Activities Home page: http://www.sogo.nu/bugs Project: SOGo For the period covering: Saturday, July 25 2015 idlast updatestatus (resolution)categorysummary 3146 2015-07-25 12:59:47 assigned (reopened) ActiveSync HTML emails are not pushed to Blackberry 10 devices
Re: [SOGo] Adding users via Windows Admin Tools doesn't work
On 2015-07-25 03:12 AM, Rowland Penny wrote:
On 24/07/15 23:03, Gerald Brandt wrote:
On 2015-07-24 03:44 PM, Rowland Penny wrote:
On 24/07/15 19:13, Gerald Brandt wrote:
On 2015-07-24 10:57 AM, Rowland Penny wrote:
On 24/07/15 16:17, Gerald Brandt wrote:
Hi,
I added two users to my SAMBA/SOGo/Openchange server via the
Windows tools from Windows 7. I then went to the Linux server
and ran opechnage_newuser -- create user.
When the user connects via Outlook (2003), they can send and
receive emails, calendar, etc.
When the user connects via IMAP, they can't login. Dovecot can't
find the user in LDAP.
When the user connects voa the SOGo web interface, login takes
awhile, and the user is presented with no email folders.
I added a user with samba-tool user add and the
openchange_newuser --create, and all three (Outlook, IMAP, and
web) work perfectly.
Should I file a bug report with Openchnage on this? With SOGo?
Thanks,
Gerald
Hi, can you post you dovecot ldap conf file (suitably sanitized of
course) also what version of samba4 you are using.
Rowland
Hi,
I'm using everything from the inverse repo. Dovecot authorizes
fine when I use samba-tool to add a user. Samba version is 4.1.18.
I use a script to build my Samba/SOGo/Openchange install. You can
see my script at http://majentis.com/?p=344 . It has every config
file I use.
Here's my dovecot.conf
# Enable installed protocols
!include_try /usr/share/dovecot/protocols.d/*.protocol
postmaster_address=administra...@erlphase.com
# AUTH
disable_plaintext_auth = yes
auth_master_user_separator = *
auth_mechanisms = plain login
# master users
#passdb {
# driver = passwd-file
# master = yes
# args = /etc/dovecot/master-users
# Unless you're using PAM, you probably still want the
destination user to
# be looked up from passdb that it really exists. pass=yes does that.
#pass = yes
#}
# ldap users
passdb {
driver = ldap
args = /etc/dovecot/dovecot-ldap.conf.ext
}
userdb {
driver = ldap
args = /etc/dovecot/dovecot-ldap.conf.ext
}
# trust on 127.0.0.1
passdb {
driver = static
args = nopassword=y allow_nets=127.0.0.1/32
}
# LOGGING
auth_verbose = yes
mail_debug = no
plugin {
# Events to log. Also available: flag_change append
#mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename
# Available fields: uid, box, msgid, from, subject, size, vsize,
flags
# size and vsize are available only for expunge and copy events.
#mail_log_fields = uid box msgid size
}
# MAIL and NAMESPACES
mail_location = maildir:~/maildir
mail_uid = vmail
mail_gid = vmail
mail_plugins = acl quota
namespace {
type = private
separator = /
prefix =
inbox = yes
mailbox INBOX {
auto = create
}
}
namespace {
type = shared
separator = /
prefix = shared/%%u/
location = maildir:%%h/maildir:INDEX=~/maildir/shared/%%u
subscriptions = no
list = children
}
# MASTER
service imap-login {
inet_listener imap {
#port = 143
}
inet_listener imaps {
#port = 993
ssl = yes
}
# this is suboptimal since imap and imaps will also accept nopass
inet_listener imap-nopass {
port = 144
}
}
service pop3-login {
inet_listener pop3 {
#port = 110
}
inet_listener pop3s {
#port = 995
#ssl = yes
}
}
service lmtp {
unix_listener lmtp {
#mode = 0666
}
# Create inet listener only if you can't use the above UNIX socket
inet_listener lmtp {
# Avoid making LMTP visible for the entire internet
address = 127.0.0.1
port = 24
}
}
service imap {
executable = imap postlogin
}
service auth {
# auth_socket_path points to this userdb socket by default. It's
typically
# used by dovecot-lda, doveadm, possibly imap process, etc. Its
default
# permissions make it readable only by root, but you may need to
relax these
# permissions. Users that have access to this socket are able to
get a list
# of all usernames and get results of everyone's userdb lookups.
unix_listener /var/spool/postfix/private/auth {
mode = 0660
user = postfix
group = postfix
}
}
service postlogin {
executable = script-login -d rawlog
unix_listener postlogin {
}
}
# SSL/TLS support: yes, no, required. doc/wiki/SSL.txt
ssl = yes
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_key = /etc/ssl/private/dovecot.pem
# LDA
quota_full_tempfail = yes
protocol lda {
# Space separated list of plugins to load (default is global
mail_plugins).
#mail_plugins = $mail_plugins
}
# PROTOCOLS
protocol imap {
mail_plugins = $mail_plugins autocreate imap_acl imap_quota
}
protocol lmtp {
mail_plugins = $mail_plugins sieve
}
service managesieve-login {
inet_listener sieve {
port = 4190
address = 127.0.0.1
}
}
service managesieve {
}
protocol sieve {
}
plugin {
acl = vfile
acl_shared_dict = file:/var/spool/dovecot/shared-mailboxes.db
quota_rule = *:storage=2G
quota_rule2 = Trash:storage=+100M
quota =
[SOGo] Valid usernames in Sogo connector?
Hello all, I have a question regarding Sogo connector in Thunderbird. A have used it to connect to my owncloud addressbook for a while now without any problems. However, this week I created a new set of users in owncloud and used their email addresses as username. I have 2 remote addressbooks in Thunderbird now, with two different user: bert and b...@example.com mailto:b...@example.com the first one syncs flawlessly and the second one just shows 0 updates and the addressbook remains empty, even though in owncloud it has exactly the same addresses imported. My first suspicion was that SOGO connector can not handle the username format with the @-sign or the dots. Can someone confirm or deny this? Or maybe point at an other source of this problem? Any advice on troubleshooting is welcome. Regards, Bert -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Adding users via Windows Admin Tools doesn't work
yes, it does -- That was the issue with my SOGo upgrade. It would not upgrade the 'samba' package from Inverse. I had originally installed 'samba-ad-dc' from the Samba Wiki https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO Then I setup Dovecot/Postfix and lastly SOGo (trying to follow the Instruction Manual) I have just recently completed the Samba upgrade (and all the SOGo, OpenChange upgrades, etc.) I had a problem with webmail which turned out to be an older 'sogo.conf' and I was missing a couple of packages for Outlook -- 'openchange-ocsmanager' 'openchange-rpcproxy' That was my 'rpcproxy.dll' issue. So, anyway, I am interested in how we might add new uses to the completed server, and right now, I believe the proper way to do so is to run 'samba-tool' and 'openchange_newuser' as you have then login to 'sogo' I'd like to see the Windows AD tools work properly. I used the tools to create a domain login account, but it does not use our mail or calendar services, so I haven't actually tested that function with new domain users. We're using Samba domain users to segregate who has access to certain applications. On 07/24/2015 06:04 PM, Gerald Brandt wrote: I haven't had a chance to try SOGo 2.3.1, but I believe it uses the same Samba. -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Adding users via Windows Admin Tools doesn't work
On 24/07/15 23:03, Gerald Brandt wrote:
On 2015-07-24 03:44 PM, Rowland Penny wrote:
On 24/07/15 19:13, Gerald Brandt wrote:
On 2015-07-24 10:57 AM, Rowland Penny wrote:
On 24/07/15 16:17, Gerald Brandt wrote:
Hi,
I added two users to my SAMBA/SOGo/Openchange server via the
Windows tools from Windows 7. I then went to the Linux server and
ran opechnage_newuser -- create user.
When the user connects via Outlook (2003), they can send and
receive emails, calendar, etc.
When the user connects via IMAP, they can't login. Dovecot can't
find the user in LDAP.
When the user connects voa the SOGo web interface, login takes
awhile, and the user is presented with no email folders.
I added a user with samba-tool user add and the openchange_newuser
--create, and all three (Outlook, IMAP, and web) work perfectly.
Should I file a bug report with Openchnage on this? With SOGo?
Thanks,
Gerald
Hi, can you post you dovecot ldap conf file (suitably sanitized of
course) also what version of samba4 you are using.
Rowland
Hi,
I'm using everything from the inverse repo. Dovecot authorizes fine
when I use samba-tool to add a user. Samba version is 4.1.18.
I use a script to build my Samba/SOGo/Openchange install. You can
see my script at http://majentis.com/?p=344 . It has every config
file I use.
Here's my dovecot.conf
# Enable installed protocols
!include_try /usr/share/dovecot/protocols.d/*.protocol
postmaster_address=administra...@erlphase.com
# AUTH
disable_plaintext_auth = yes
auth_master_user_separator = *
auth_mechanisms = plain login
# master users
#passdb {
# driver = passwd-file
# master = yes
# args = /etc/dovecot/master-users
# Unless you're using PAM, you probably still want the destination
user to
# be looked up from passdb that it really exists. pass=yes does that.
#pass = yes
#}
# ldap users
passdb {
driver = ldap
args = /etc/dovecot/dovecot-ldap.conf.ext
}
userdb {
driver = ldap
args = /etc/dovecot/dovecot-ldap.conf.ext
}
# trust on 127.0.0.1
passdb {
driver = static
args = nopassword=y allow_nets=127.0.0.1/32
}
# LOGGING
auth_verbose = yes
mail_debug = no
plugin {
# Events to log. Also available: flag_change append
#mail_log_events = delete undelete expunge copy mailbox_delete
mailbox_rename
# Available fields: uid, box, msgid, from, subject, size, vsize, flags
# size and vsize are available only for expunge and copy events.
#mail_log_fields = uid box msgid size
}
# MAIL and NAMESPACES
mail_location = maildir:~/maildir
mail_uid = vmail
mail_gid = vmail
mail_plugins = acl quota
namespace {
type = private
separator = /
prefix =
inbox = yes
mailbox INBOX {
auto = create
}
}
namespace {
type = shared
separator = /
prefix = shared/%%u/
location = maildir:%%h/maildir:INDEX=~/maildir/shared/%%u
subscriptions = no
list = children
}
# MASTER
service imap-login {
inet_listener imap {
#port = 143
}
inet_listener imaps {
#port = 993
ssl = yes
}
# this is suboptimal since imap and imaps will also accept nopass
inet_listener imap-nopass {
port = 144
}
}
service pop3-login {
inet_listener pop3 {
#port = 110
}
inet_listener pop3s {
#port = 995
#ssl = yes
}
}
service lmtp {
unix_listener lmtp {
#mode = 0666
}
# Create inet listener only if you can't use the above UNIX socket
inet_listener lmtp {
# Avoid making LMTP visible for the entire internet
address = 127.0.0.1
port = 24
}
}
service imap {
executable = imap postlogin
}
service auth {
# auth_socket_path points to this userdb socket by default. It's
typically
# used by dovecot-lda, doveadm, possibly imap process, etc. Its
default
# permissions make it readable only by root, but you may need to
relax these
# permissions. Users that have access to this socket are able to
get a list
# of all usernames and get results of everyone's userdb lookups.
unix_listener /var/spool/postfix/private/auth {
mode = 0660
user = postfix
group = postfix
}
}
service postlogin {
executable = script-login -d rawlog
unix_listener postlogin {
}
}
# SSL/TLS support: yes, no, required. doc/wiki/SSL.txt
ssl = yes
ssl_cert = /etc/ssl/certs/dovecot.pem
ssl_key = /etc/ssl/private/dovecot.pem
# LDA
quota_full_tempfail = yes
protocol lda {
# Space separated list of plugins to load (default is global
mail_plugins).
#mail_plugins = $mail_plugins
}
# PROTOCOLS
protocol imap {
mail_plugins = $mail_plugins autocreate imap_acl imap_quota
}
protocol lmtp {
mail_plugins = $mail_plugins sieve
}
service managesieve-login {
inet_listener sieve {
port = 4190
address = 127.0.0.1
}
}
service managesieve {
}
protocol sieve {
}
plugin {
acl = vfile
acl_shared_dict = file:/var/spool/dovecot/shared-mailboxes.db
quota_rule = *:storage=2G
quota_rule2 = Trash:storage=+100M
quota = dict:::file:%h/dovecot-quota
sieve = ~/.dovecot.sieve
sieve_dir =
Re: [SOGo] Adding users via Windows Admin Tools doesn't work
just a comment before Rowland responds -- When I first created Samba users, I used 'samba-tool' and 'openchange_newuser' just as you did here. Then I was instructed that by logging into the SOGo web interface, it would create the tables, fields, etc. in MariaDB (I think that was the correct procedure, as it was a bit ago) I used the instructions in the Outlook Configuration PDF (like below) then logged into SOGo as each user. I do not recall doing anything for Dovecot/Postfix other than setup the initial admin account. On 07/24/2015 06:03 PM, Gerald Brandt wrote: Hi, samba-tool user add test openchange_newuser --create test The above commands give me a user that has great access via Outlook, IMAP, and web. Gerald -- users@sogo.nu https://inverse.ca/sogo/lists
