Koozali.org formerly Contribs.org

SOGO for Sme

Re: SOGO for Sme
« Reply #90 on: May 21, 2010, 07:25:35 AM »
Hey all,

Having trouble with installing this...

Fresh install of 8b5. Followed Wiki to a tee and when I run yum, I get this:

Code: [Select]
memcached-1.4.2-1.el5.i386 from sogo has depsolving problems
  --> Missing Dependency: libevent-1.1a.so.1 is needed by package memcached-1.4.2-1.el5.i386 (sogo)
Error: Missing Dependency: libevent-1.1a.so.1 is needed by package memcached-1.4.2-1.el5.i386 (sogo)
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
                        package-cleanup --dupes
                        rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.

Any ideas?

Thanks!

Joe

Offline mdo

  • *
  • 355
Re: SOGO for Sme
« Reply #91 on: May 21, 2010, 08:29:24 AM »
There is a discussion about this here: http://forums.contribs.org/index.php/topic,46012.0/topicseen.html

Another idea is to apply all available updates (Sme + CentOS) and then try again.
Michael
...

Re: SOGO for Sme
« Reply #92 on: May 21, 2010, 10:19:07 AM »
Hi Joeg1484

got the same issue here....

my workaround:

do a manual install of libevent-1.1a. you can find it via rpmfind or google or just take the link below (it worked for me)

wget ftp://mirror.switch.ch/pool/3/mirror/centos/5.4/os/i386/CentOS/libevent-1.1a-3.2.1.i386.rpm
yum localinstall libevent-1.1a-3.2.1.i386.rpm

after
signal-event yum-modify

then you can install smeserver-sogo package

yum install smeserver-sogo --enablerepo=nethsme --enablerepo=sogo

hope that helps

kg66




Re: SOGO for Sme
« Reply #93 on: May 21, 2010, 04:58:01 PM »
Hi Joeg1484

got the same issue here....

my workaround:

do a manual install of libevent-1.1a. you can find it via rpmfind or google or just take the link below (it worked for me)

wget ftp://mirror.switch.ch/pool/3/mirror/centos/5.4/os/i386/CentOS/libevent-1.1a-3.2.1.i386.rpm
yum localinstall libevent-1.1a-3.2.1.i386.rpm

after
signal-event yum-modify

then you can install smeserver-sogo package

yum install smeserver-sogo --enablerepo=nethsme --enablerepo=sogo

hope that helps

kg66

Yeah, this worked... However, 2 more questions:

1. After installing the libevent rpm, SME wants to upgrade it to something like 1.4. Will this pose  a problem.
2. When I try to access my sogo from outside the network, it lets me log in, but then redirects me to a site internal and I loose connection. Is there a way to specify global access fro this?

Thanks!

Joe

Offline Stefano

  • *
  • 10,779
  • Skype account: maghissimo
    • Smeserver italian community
Re: SOGO for Sme
« Reply #94 on: May 21, 2010, 05:21:01 PM »
1. After installing the libevent rpm, SME wants to upgrade it to something like 1.4. Will this pose  a problem.

just exclude it with --exclude=libevent in the yum command
« Last Edit: May 21, 2010, 05:23:11 PM by Stefano »
Consulente di Smeserver.it -  Soluzioni e supporto su Sme server in Italia

Re: SOGO for Sme
« Reply #95 on: July 17, 2010, 05:33:48 PM »
Anyone have an idea on how to change the default domain that SOGo resolves to...

Here is my problem... I have a local domain joeman1.local and an external mail domain mail.joeman1.com. When I try to access SOGo from mail.joeman1.com, it tries to redirect to joeman1.local and this fails from outside my network.

I tried to expand the template 10defaults to point my domain to the external and ran the expand-template command, but it is still trying to redirect https to the local domain.

Any workarounds for this?

Thanks!
Joe

Offline edform

  • *
  • 178
    • http://www.workgroupsolutions.co.uk
Re: SOGO for Sme
« Reply #96 on: July 20, 2010, 06:09:27 PM »
Anyone have an idea on how to change the default domain that SOGo resolves to...

Here is my problem... I have a local domain joeman1.local and an external mail domain mail.joeman1.com. When I try to access SOGo from mail.joeman1.com, it tries to redirect to joeman1.local and this fails from outside my network.

I tried to expand the template 10defaults to point my domain to the external and ran the expand-template command, but it is still trying to redirect https to the local domain.

Any workarounds for this?

I think you have a fundamental misunderstanding of the way in which SME server should be set up. It isn't like a Windows server where you set the domain on the server to joeman1.local and then tell the exchange server to act as the mailhost for joeman1.com. An SME server is expected to be the authoritative mailhost for your domain name. When you set it up you actually give the system your fully qualified domain name as its domain - in your case joeman1.com.

If this gives problems because you have joeman1.com hosted by an ISP you can use the 'Hostnames and addresses' facility in the server manager to change the locations of the various domain entities from 'Self and the IP address of your server' to 'Remote and the correct IP address for your ISP's facilities'.

You might also need to alter the email settings away from the standard SMTP in and out to take account of your arrangements with your ISP.

Ask again if you need any more details.

Ed Form

Re: SOGO for Sme
« Reply #97 on: July 20, 2010, 07:41:52 PM »
I think you have a fundamental misunderstanding of the way in which SME server should be set up. It isn't like a Windows server where you set the domain on the server to joeman1.local and then tell the exchange server to act as the mailhost for joeman1.com. An SME server is expected to be the authoritative mailhost for your domain name. When you set it up you actually give the system your fully qualified domain name as its domain - in your case joeman1.com.

If this gives problems because you have joeman1.com hosted by an ISP you can use the 'Hostnames and addresses' facility in the server manager to change the locations of the various domain entities from 'Self and the IP address of your server' to 'Remote and the correct IP address for your ISP's facilities'.

You might also need to alter the email settings away from the standard SMTP in and out to take account of your arrangements with your ISP.

Ask again if you need any more details.

Ed Form

LOL, yeah, I have spent more time in the Windows trenches than in the Linux trenches as of late, so you are correct on that aspect. I was wondering about the domain setup when I was installing, so I decided to just go with what i know.

I did figure out how to modify the config files to get it to work, but I was thinking about renaming my server to joeman1.com as that is how my domain is setup. Its not hosted though my ISP, although I use dyndns.org to keep my ip address up to date.

Do you have or know of a process where I can rename my server correctly? Or should I just rebuild it with the correct naming?

Thanks for the help!

Joe

Offline edform

  • *
  • 178
    • http://www.workgroupsolutions.co.uk
Re: SOGO for Sme
« Reply #98 on: July 20, 2010, 07:52:04 PM »

Do you have or know of a process where I can rename my server correctly? Or should I just rebuild it with the correct naming?

Just login to the server console as 'admin' with the root pasword and you'll get a menu. The second item in the menu is 'Configure this server' and that opens exactly the same dialogue as you went through when you first set the server up. At the end of the questions you get to reboot and the server reconfigures itself as you have just told it.

Ed Form

Re: SOGO for Sme
« Reply #99 on: July 20, 2010, 08:44:25 PM »
Wonderful!!! I will give it a go when I get home.

Thanks so much!

Joe

Offline edform

  • *
  • 178
    • http://www.workgroupsolutions.co.uk
Re: SOGO for Sme
« Reply #100 on: July 20, 2010, 10:28:09 PM »
We have made rpm for Sme, install notes here:
http://smeserver.nethesis.it/sogo/
Your Comments Are Appreciated

I ran into a problem using this rpm which hasn't been reported to this thread; so here goes...

I ran the install on my SME 8b5, Server only machine following your howto and solving the various glitches as I went along. I finished up with an install that didn't work properly. I could raise the SOGo login screen with http://hostname/SOGo and, using a valid username/password combination, the system plainly authenticated the user because the URL changed to https://hostname.domain/SOGo/so/username/Mail, but the system did not display the page.

I then reasoned that the URL was incorrect for my install, so I changed the URL to "https://hostname/SOGo/so/username/Mail/View" and up came the correct screen. Most of the functionality of SOGo worked but logging out and then logging back in didn't work and changing the URL back to the one with no domain name did not produce the correct screen until the workstation had been logged out and back in.

It is pretty obvious that the rpm does not produce a working SOGo system on a 'Server only' SME machine so I added a second network card to my server and reconfigured it as a Dedicated Server and Gateway. Once that was complete the unchanged SOGo install began working perfectly using http://hostname.doman-name/SOGo or https://hostame.domain-name/SOGo as the calling URL.

These problems may be caused by the fact that the 'Server-only' install was not the DHCP master for the network or it may be that the rpm is not sufficiently explicit in setting the hostname and domain name information in the configuration files.

Since I now know that the rpm works fine - with a couple of glitches that need modifications to the instructions - I'd be happy to settle for the fact that it works perfectly on a Server and Gateway.

I'll publish a complete Howto shortly including all of the extra steps needed to make it work.

Ed Form

Offline alefattorini

  • **
  • 61
  • www.nethserver.org
    • www.nethserver.org
Re: SOGO for Sme
« Reply #101 on: July 22, 2010, 05:30:51 PM »
>  the rpm is not sufficiently explicit in setting the hostname and domain name information in the configuration files.

Yes, this is the problem. If NethService isn't your dns, you should configure your DNS server for resolve IP_SME = hostname = hostname.domain
Bye

Offline edform

  • *
  • 178
    • http://www.workgroupsolutions.co.uk
Re: SOGO for Sme - damage to SME update system
« Reply #102 on: July 27, 2010, 06:50:56 PM »
I've discovered that the 'Software Installer' function in server manager has failed repeatedly since I installed SOGo. The culprit is the libevent dependency which I cured while installing SOGo by downloading the rpm libevent-1.1a-3.el4.i386.rpm and installing it.

Now, when I run the software installer in the server manager the updates fail with the message...

---> Package yum.noarch 0:3.2.22-26.el5.centos set to be updated
--> Finished Dependency Resolution
memcached-1.4.2-1.el5.i386 from installed has depsolving problems
  --> Missing Dependency: libevent-1.1a.so.1 is needed by package memcached-1.4.2-1.el5.i386 (installed)
Error: Missing Dependency: libevent-1.1a.so.1 is needed by package memcached-1.4.2-1.el5.i386 (installed)
 You could try using --skip-broken to work around the problem
 You could try running: package-cleanup --problems
                        package-cleanup --dupes
                        rpm -Va --nofiles --nodigest
The program package-cleanup is found in the yum-utils package.
yum update apr-util.i386 at.i386 audit-libs-python.i386 audit-libs...

Does this mean that SME 8 is dependent on a specific version of this package and can't update properly without it?

If this is the case I'll report it as a bug.

Ed Form

Re: SOGO for Sme
« Reply #103 on: July 27, 2010, 07:29:24 PM »
I ran into the same issue, so what I do for now is when I going in to update my server, I simply unselect the libevent package and select the others. This will allow the server to get all the other updates but not the broken one.

Until this is resolved, it will get your machine updated.

Hope this helps!

Joe

Offline edform

  • *
  • 178
    • http://www.workgroupsolutions.co.uk
Re: SOGO for Sme
« Reply #104 on: July 27, 2010, 10:04:48 PM »
I ran into the same issue, so what I do for now is when I going in to update my server, I simply unselect the libevent package and select the others. This will allow the server to get all the other updates but not the broken one.

Until this is resolved, it will get your machine updated.

Hope this helps!

Joe

Worked perfectl;y. Well done!

Ed Form