I don't know what that file is for. The list may know...? I am glad I could help but the real help is this list. That's where I've found my answers. I'm really just a sogo newb and have only recently started using it more often as I previously used roundcube and imap almost exclusively.
Sincerely, Fabian Santiago Sent from my iPhone > On Mar 13, 2016, at 9:15 PM, Jim Fridlund <jfridl...@gmail.com> wrote: > > Hi Fabian. I tried what you suggested. I reinstalled sope49-\* packages and > restarted SOGo. I still got the same Proxy Error from the web browser. > > I also noticed the attachments not working properly. A few of our users are > using iOS and we could no longer see attachments after the 3.0.2 update. The > work around was to remove the account from iOS and re-add it as Other (IMAP) > instead of Microsoft Exchange account. That seems to work, but we lose some > functionality. > > So, I just went ahead and changed my repo to point to nightly. I did a ‘yum > check-update’ and it showed that sope49 packages were out of date. So, I went > ahead and updated it from nightly. This seemed to fix my login problem! I can > login on SOGo again from the web. Will try again to see if MS Exchange > attachments is working again. > > btw, do you know what this file is for, > /usr/share/doc/sogo-3.0.2/SOGo-apple-ab.conf? Is this to give better > integration for OS X and iOS? > > Thanks so much for your help! > — > Jim > >> On Mar 13, 2016, at 9:31 PM, Fabian Santiago <fsanti...@garbage-juice.com> >> wrote: >> >> Hi Jim, >> >> I learned I had to forcibly reinstall all of the soap packages. This fixed >> me up. I used yum: >> >> Yum reinstall sope49-* >> >> Was my command line. >> >> Restarted sogod afterwards and was good to go. >> >> Since then I've also switched my yum repo definition for sogo to the nightly >> builds repo because you'll also discover after going to v3.0.2 that mime >> parts are broken in email viewing via EAS / mobile devices. The fix is >> slated for v3.0.3 I believe but it is in the nightly build repo for now. >> >> I also updated my nginx configs for sogo based on the lists recommendations. >> Only minor tweaks. I have those too if need be. Let me know. >> >> Hope this helps. >> >> Sincerely, >> >> Fabian Santiago >> >> Sent from my iPhone >> >>> On Mar 13, 2016, at 4:04 AM, Jim Fridlund <jfridl...@gmail.com> wrote: >>> >>> Hi Fabian. I saw your post regarding SOGo issue. I did a google search and >>> stumbled across your article. Unfortunately, I made the same error doing a >>> "yum update". I am using CentOS 6.7 with iRedMail and I am seeing the same >>> problem you’re seeing. It started to work at first. The users were >>> commenting on the new SOGo look which they liked, but then we’re seeing >>> Proxy Error message on our browser. We have not been able to use SOGo for a >>> week now. I am having my users use RoundCube instead. >>> >>> I was not aware that this was a major update. This seems kind of bad, but I >>> guess I get what I paid for… If you were able to fix the problem, can you >>> please share your fix? Thanks in advance. >>> — >>> Jim >>> >>> http://article.gmane.org/gmane.comp.groupware.sogo.user/23871 > -- users@sogo.nu https://inverse.ca/sogo/lists
