Re: [SOGo] Outlook EAS with mailboxes > 3GB
We have the same problem here, people with large mailboxes using EAS with Outlook 2013 have issues with initial sync being slow, some mails never even show up in Outlook and the same goes for the calendar, some events never sync. The same people are using EAS on their Android phones and it's working fine there. Right now I too recommend them to use IMAP and CalDavSynchronizer. Now that I took a quick peek in our logs I found this one that I haven't seen before I think... "Fatal error occured - tried to call -processSyncAddCommand: ... on a mail folder. We abort" ... other than that it's mostly just "found no viewer for MIME type". I suspect this might have nothing to do with it though and it's probably more than one issue. // Mattias * Peter Beck (pe...@datentraeger.li) wrote: > On 10/10/2015 08:22 PM, Alain Abbas wrote: > > for now we had stopped the deployement of activesync and outlook2013 > > Hi Alain, > > good to know I am not the only one ;-) > I've also switched (at least the big mailboxes) to IMAP and > CalDavSynchronizer (which will hopefully soon get CardDAV support). > > But still hoping someone can enlighten us here on the list... > > Regards > Peter > -- > users@sogo.nu > https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Event created in Outlook doesn't sync to SOGo
If I create an event in Outlook (using EAS) it doesn't sync to SOGo however if I create an event in SOGo it does get synced to Outlook. When I have SOGoEASDebugEnabled turned on I can see the event I created in the SOGo web interface being synced through EAS to Outlook but I see no such log entry for the other one. // Mattias -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo 2.3 throws errors after weblogin
Here's a little step-by-step. # echo deb http://security.debian.org/ wheezy/updates main contrib /etc/apt/sources.list.d/wheezy.list # apt-get update # apt-get install libldap-2.4-2=2.4.31-2 # rm /etc/apt/sources.list.d/wheezy.list # apt-get update # echo \ Package: libldap-2.4-2 Pin: version 2.4.31-2 Pin-Priority: 1001 /etc/apt/preferences.d/libldap * Rasca Gmelch (rasca.gme...@artcom.de) wrote: Hi, do you have a step by step for this downgrade / pinning as it worked for you? apt-get Would be very nice. Thx+Regards, Rasca Am 10.06.2015 um 17:02 schrieb Mattias Fliesberg: I have no insight into what the actual issue is. I could however downgrade to the wheezy libldap (and pin the package) so it works for now. A developer needs to take a look at this issue though, I'm not of much help. * Rasca Gmelch (rasca.gme...@artcom.de) wrote: Hi Matthias, Thank you for your answer. Recompiling is not an option for us. I tried downgrading the libldap with an Debian 7 package but it failed because of unresolved dependencies. Is it a bug in the libldap or just some kind of incompatibility between libldap and sogo? Or would it be the best option to switch away from Debian to Ubuntu 14.04/64bit? Any recommendations? Regards, Rasca Am 10.06.2015 um 12:42 schrieb Mattias Fliesberg: I had the same issue, solved it by downgrading libldap http://www.sogo.nu/bugs/view.php?id=3211 * Rasca Gmelch (rasca.gme...@artcom.de) wrote: Hi, after upgrading from sogo 2.2.17a and Debian 7 to sogo 2.3 and Debian 8 I see continuous errors in sogo.log as soon as I login on the web interface. Sometimes the errors stop after about twenty entries, but if I switch to the mail tab it looks like the errors are not stopping until I kill the sogod process. The CPU load of the sogod process goes up to 100% and it looks like the process is eating more and more memory until the process is kill by hand or killed by OS (out of memory). The error in the logfile is: sogod [18302]: [ERROR] 0x0x7f010a3b3930[WOHttpAdaptor] http server caught: NGCouldNotAcceptException: 0x7f01118192d0 NAME:NGCouldNotAcceptException REASON:Could not accept: descriptor is not a socket descriptor INFO:(null) The setup in general: openLDAP for user database, postgreSQL as database backend and apache for web access. Any ideas? -- Rasca Gmelch | IT | JabberID: rasca.gme...@artcom.de OpenPGP Key ID: 8168E925, Key server: pool.sks-keyservers.net Fingerprint 1FD0 3199 13B7 7ADC 5DF1 A8EF FA4C 4AC0 8168 E925 -- users@sogo.nu https://inverse.ca/sogo/lists -- Rasca Gmelch | IT | JabberID: rasca.gme...@artcom.de OpenPGP Key ID: 8168E925, Key server: pool.sks-keyservers.net Fingerprint 1FD0 3199 13B7 7ADC 5DF1 A8EF FA4C 4AC0 8168 E925 ART+COM AG | Kleiststr. 23-26 | 10787 Berlin | Germany Fon: +49.30.21001-466 | Fax: +49.30.21001-555 http://www.artcom.de/ HRB 68308 | Amtsgericht Charlottenburg Vorstand: Andreas Wiek, Prof. Joachim Sauter Aufsichtsratsvorsitzender: Volker Tietgens USt-IdNr.: DE811998328 -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] EAS in Outlook incorrectly parses addresses
Hi, I'm having an issue with Outlook and EAS when I try to send a mail to multiple recipients. If I enter t...@example.com, te...@example.com the resulting To header looks like this to: t...@example.com te...@example.com i.e. The mail only gets sent to te...@example.com with the label t...@example.com. The same thing occurs if I enter the addresses from my address book or in any other way I've tried. Unfortunately I don't see anything interesting in sogo.log even with SOGoEASDebugEnabled enabled. Also, this doesn't only occur for me but for other people using this SOGo server. // Mattias -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo 2.3 throws errors after weblogin
I had the same issue, solved it by downgrading libldap http://www.sogo.nu/bugs/view.php?id=3211 * Rasca Gmelch (rasca.gme...@artcom.de) wrote: Hi, after upgrading from sogo 2.2.17a and Debian 7 to sogo 2.3 and Debian 8 I see continuous errors in sogo.log as soon as I login on the web interface. Sometimes the errors stop after about twenty entries, but if I switch to the mail tab it looks like the errors are not stopping until I kill the sogod process. The CPU load of the sogod process goes up to 100% and it looks like the process is eating more and more memory until the process is kill by hand or killed by OS (out of memory). The error in the logfile is: sogod [18302]: [ERROR] 0x0x7f010a3b3930[WOHttpAdaptor] http server caught: NGCouldNotAcceptException: 0x7f01118192d0 NAME:NGCouldNotAcceptException REASON:Could not accept: descriptor is not a socket descriptor INFO:(null) The setup in general: openLDAP for user database, postgreSQL as database backend and apache for web access. Any ideas? Thx+Regards, Rasca -- Rasca Gmelch | IT | JabberID: rasca.gme...@artcom.de OpenPGP Key ID: 8168E925, Key server: pool.sks-keyservers.net Fingerprint 1FD0 3199 13B7 7ADC 5DF1 A8EF FA4C 4AC0 8168 E925 -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Sogo 2.3 throws errors after weblogin
I have no insight into what the actual issue is. I could however downgrade to the wheezy libldap (and pin the package) so it works for now. A developer needs to take a look at this issue though, I'm not of much help. * Rasca Gmelch (rasca.gme...@artcom.de) wrote: Hi Matthias, Thank you for your answer. Recompiling is not an option for us. I tried downgrading the libldap with an Debian 7 package but it failed because of unresolved dependencies. Is it a bug in the libldap or just some kind of incompatibility between libldap and sogo? Or would it be the best option to switch away from Debian to Ubuntu 14.04/64bit? Any recommendations? Regards, Rasca Am 10.06.2015 um 12:42 schrieb Mattias Fliesberg: I had the same issue, solved it by downgrading libldap http://www.sogo.nu/bugs/view.php?id=3211 * Rasca Gmelch (rasca.gme...@artcom.de) wrote: Hi, after upgrading from sogo 2.2.17a and Debian 7 to sogo 2.3 and Debian 8 I see continuous errors in sogo.log as soon as I login on the web interface. Sometimes the errors stop after about twenty entries, but if I switch to the mail tab it looks like the errors are not stopping until I kill the sogod process. The CPU load of the sogod process goes up to 100% and it looks like the process is eating more and more memory until the process is kill by hand or killed by OS (out of memory). The error in the logfile is: sogod [18302]: [ERROR] 0x0x7f010a3b3930[WOHttpAdaptor] http server caught: NGCouldNotAcceptException: 0x7f01118192d0 NAME:NGCouldNotAcceptException REASON:Could not accept: descriptor is not a socket descriptor INFO:(null) The setup in general: openLDAP for user database, postgreSQL as database backend and apache for web access. Any ideas? -- Rasca Gmelch | IT | JabberID: rasca.gme...@artcom.de OpenPGP Key ID: 8168E925, Key server: pool.sks-keyservers.net Fingerprint 1FD0 3199 13B7 7ADC 5DF1 A8EF FA4C 4AC0 8168 E925 -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] No events in web UI since updating to 2.2.17a.20150518-1
Since I updated to the latest nightly I no longer see events in the web UI and I'm getting... NAME:ExecutionFailed REASON:Unknown column 'a.c_description' in 'field list' .. errors in sogo.log. Sort of looks to me like som database migration wasn't run or something. What do I need to do? // Mattias -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] No events in web UI since updating to 2.2.17a.20150518-1
Well look at that, there was a migration script, sql-update-2.1.17_to_2.1.18-mysql.sh Ran it, now it's working again. * Mattias Fliesberg (mattias.fliesb...@chas.se) wrote: Since I updated to the latest nightly I no longer see events in the web UI and I'm getting... NAME:ExecutionFailed REASON:Unknown column 'a.c_description' in 'field list' .. errors in sogo.log. Sort of looks to me like som database migration wasn't run or something. What do I need to do? // Mattias -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
Re: [SOGo] Is there a way to have SOGo not send mail alarms as the organizer?
I thought about that, then realized that I could just use the sendmail transport and my local postfix could just relay it to the one requiring authentication. I obviously also needed to have the SOGo host in mynetworks there with some permit_mynetworks in smtpd_sender_restrictions and smtpd_recipient_restrictions etc. Just having this with the SMTP transport didn't work because authing in the webinterface of SOGo started failing. Also, sending mail in Outlook with OpenChange didn't work with it just giving up after EHLO for some reason... might have been a different issue, last week is a total blur, but using the sendmail transport solved all my mail-sending issues at least. // Mattias * Marcel Waldvogel (mar...@wanda.ch) wrote: Mattias, can you make Postfix listen on another port for SOGo, where only SOGo is allowed to login and where reject_sender_login_mismatch is not active? -Marcel Am 10.11.2014 um 10:42 schrieb Mattias Fliesberg mattias.fliesb...@chas.se: Hi, We have a postfix server with... smtpd_sender_restrictions = reject_sender_login_mismatch This means that the user we use for the sogo-ealarms-notify cronjob can't send as all the other users. Is there a way to make SOGo not try to send From the organizer? If not, how have other people with this kind of setup solved this issue? Thanks, // Mattias -- users@sogo.nu https://inverse.ca/sogo/lists -- users@sogo.nu https://inverse.ca/sogo/lists
[SOGo] Is there a way to have SOGo not send mail alarms as the organizer?
Hi, We have a postfix server with... smtpd_sender_restrictions = reject_sender_login_mismatch This means that the user we use for the sogo-ealarms-notify cronjob can't send as all the other users. Is there a way to make SOGo not try to send From the organizer? If not, how have other people with this kind of setup solved this issue? Thanks, // Mattias -- users@sogo.nu https://inverse.ca/sogo/lists
