Re: [SOGo] Support

2017-10-15 Thread Paul van der Vlis
Op 06-10-17 om 07:52 schreef Julia Schneider
(j...@fabmation.de):
> Hello,
> 
> we're using SoGo since May 2017, we have a problem and we hope you can fix.
> 
> The problem is, we need shared calenders. We have created a user
> (postmaster) where we can add coordinate meetings, vacations, travel,
> etc. The problem is, every scheduled event belongs first to postmaster
> and this account gets the mails about invitations, response, etc., not
> the person who created it.
> 
> So we started to create the event first in our personal calendar, and
> when we finish creating and inviting people we have to move the event to
> the shared calendar. This is very inconvenient and error prone.
> 
> What can we do,  that the person who creates an event is automatically
> the owner?

The person who creates an event can do this with it's own calendar.
People who accepts an invitation will get it in it's own calendar, so
the postmaster calendar is not really needed.

If you like something as an postmaster-calendar I see that as something
extra, you could make one person responsible to keep that calendar
up-to-date. That's less error prone.

Hope this helps!

With regards,
Paul van der Vlis



-- 
Paul van der Vlis Linux systeembeheer Groningen
https://www.vandervlis.nl/

-- 
users@sogo.nu
https://inverse.ca/sogo/lists


[SOGo] SOGoTrustProxyAuthentication = YES results in IMAP4 login failed

2017-10-15 Thread James MCCOY

Hello all,

I'm implementing 2FA to strengthen my SOGo security using this great 
project - https://github.com/clems4ever/authelia


Following 
https://sogo.nu/nc/support/faq/article/how-to-use-webauth-with-sogo-2.html 
login is working and the user gets passed into SOGo webmail with access 
to contacts and calendar, however no emails show as the IMAP login fails 
as no password is passed, however no password is available as the 
authentication has been handled before reaching SOGo.


The SOGo logs shows;

Oct 15 12:03:36 sogod [7]: [ERROR] 
<0x0x56494a8b8b30[NGImap4ConnectionManager]> IMAP4 login failed:

  host=10.10.1.101, user=user@domain.email, pwd=no
  url=imaps://user%40domain.email@10.10.1.101/?tls=YES
  base=(null)
  base-class=(null))
  = <0x0x56494a9ffba0[NGImap4Client]: login=user@domain.email(pwd) 
socket=>
Oct 15 12:03:36 sogod [7]: <0x56494aba22f0[SOGoMailAccount]:0> renewing 
imap4 password
Oct 15 12:03:36 sogod [7]: [ERROR] <0x56494aba22f0[SOGoMailAccount]:0> 
no IMAP4 password available
Oct 15 12:03:36 sogod [7]: [ERROR] <0x56494aba22f0[SOGoMailAccount]:0> 
Could not connect IMAP4


And in the mail.log

Oct 15 12:07:29 mailserver dovecot: imap-login: Disconnected (auth 
failed, 1 attempts in 2 secs): user=>, method=PLAIN, rip=10.10.1.105, 
lip=10.10.1.101, TLS: Disconnected, session=
Oct 15 12:07:32 mailserver dovecot: imap(user@domain.email 
): Disconnected: Logged out in=24114 out=752986


Any suggestions to resolve this please? I've discovered one option which 
was dismissed by SOGo of implementing the master password, but 
presumably someone must be making use of the webauth feature!!


Thanks.

--
users@sogo.nu
https://inverse.ca/sogo/lists