Topic: Open-Xchange on sme7alpha4: Stuck on imap

[DarkMirage]

(Edit:) I solved the issue in the title; new script are online; I've updated the instructions below (/edit)

Following up on some previous threads about Open-Xchange I have made a script which makes for a nice start.
However, I could use some assistance with doing things right (secure).

Below is a howto on my open-xchange scripts, so you needn't start from scratch if you want to try this.

This works on a clean installation of SME7alpha4 and SME7alpha5.
This will absolutely not work on SME6.x.
You need 2 boxes, or network storage while reinstalling the same box.

Get the following Java files (links are to Java License Agreement):
The jta files are in the same place.

jdk-1_5_0_02-linux-i586.bin
javamail-1_3_2.zip
jaf-1_0_2-upd.zip
jta-1_0_1B-classes.zip
jta-1_0_1B-doc.zip
jmx-1_2_1-ri.zip[/list]

From the directory containing the above, enter the following commands:

Code: [Select]

wget http://ainigma32.lir.dk/ainigma32/Open-Xchange-devel
chmod +x Open-Xchange-devel; ./Open-Xchange-devel
This should take some time depending on your download and computer speed...
(It took ca 30m on my DSL, 256M ram and 3000+ proc )

The script may halt on missing files. Here's what to do:
Check file OX-missing.list

Code: [Select]

pico OX-missing.list
Get any missing packages
You should re-run the wget file, it won't download existing packages.
It will place found packages in the right directory.
That goes for packages previously downloaded, packages in the current directory and packages downloaded just now, in that order.

When it's done you can save /SME7Open-Xchange-devel.tgz so you can skip the download if you're going to start over.

Copy /SME7Open-Xchange.tgz to a clean installation (or a network path while you reinstall the same box). You should move into it's dir or specify a path with the tarball. Then execute the install script.

Code: [Select]

tar -zxPf SME7Open-Xchange.tgz
./Open-Xchange-install
Enter the admin password and wait untill it finishes. (Took ca 5 minutes with 256M ram and 3000+ proc )  

You should be able to login at http://<yourdomain>/cgi-bin/login.pl with the admin account.

You can add users as follows:

Code: [Select]

/usr/local/ox/sbin/adduser_ox \
 --username='doej' \
 --passwd='<yourpass>' \
 --name='John' \
 --sname='Doe' \
 --maildomain='<yourdomain>' \
 --ox_timezone='Europe/Amsterdam'


Note: The correct-filespool script from open-xchange is commented out.
      It takes way long, and it doesn't fix anything I've seen.

Also: I've used a lot of sources for this, including the phpwiki page right here on contribs.org, and would like to thank everyone posting helpfull info on this. I'll try to work out a list of sources to put into a later (hopefully completely working) version of this howto.
     
And last of all: To get this to work on SME6.x I would have to build openldap --enable-aci compatible with glibc2.2, for a start. This isn't going very well with me. If anyone knows how to do that, that would be great.

[gregswallow]

There is a howto for openxchange on Fedora Core 3 with Dovecot here:
http://easy-technologies.com/ox-fc3.html
...unfortunatley in Spanish.

I wish I had time to work on this too.  Maybe ask in the forums on open-xchange.org.

[DarkMirage]

I'm well aware of the FC3 howto, but thanks anyway.
You can find a crude translation on this at http://ainigma32.lir.dk/ainigma32/index.php?module=pagesetter&func=viewpub&tid=2&pid=34. The script isn't working as of yet, I'm still trying to get it to work on fedora, but I'm having trouble with the ldap (client-side) there...

The problem with imap, I think, has something to do with the changed frontend in sme. I'm not sure how this is done in sme7. I do know I'm getting an 'access denied' in some log, when open-xchange tries to contact imap at webmail-login. So this should mean I have to configure open-xchange to authenticate with imap using a set password and/or enable what I believe to be some sort of ldap based interaction...

[DarkMirage]

Well, I figured it out. Users have to be created in sme before they are allowed to access their e-mail. Offcourse this does have potential, looking at the administrative part of open-exchange.
I mean, how hard would it be to add the commandline for creating an ox user to the new user script, and dito for modifying and deleting. Also, changing the mailadmin to admin seems just one sed away

I will be looking into finetuning the installation and figuring out which packages are redundant next, after that I'll see what I can do for server-manager administration of ox.

For now, anyone willing to try this: Add a user in sme, in ox, and all is well. You might need to create the folders for the user, I haven't found the mailbox configuration just jet.

[RobH]

Hi DarkMirage,

I'm very intereted in testing open-xchange on SME7alpha
Can you please send me you Open-Xchange-wget script.

Thanks,
Rob.

[jester]

DarkMirage,

Did you take your script offline, or has it been placed somewhere else?!
I wanted to give it a test on alpha5, but can't seem to find it.

Jester.

[ergozd]

Hi DarkMirage!

Tried your script on a fresh SME7_alpha5, in Open-Xchange-devel script openexchange rpms doesn't build.

[DarkMirage]

I have taken the scripts offline (some already downloaded them ) but they should be back this week. I've removed some packages, making the download about 2/3 of the original. I've also replaced the default mailadmin with admin, so you can immediatly log in to groupware and mail with the admin account. I'll also look into the password thing, as it's currently using the admin password for pgsql, which ox places in plain text in their confs (which is bad   ).

The next version should run on sme7alpha5, if I can get it to work there. I also intend to start using ox 0.8 asap. All in all, it's still a long way from done, but I'll be happy to post new versions, as long as they're working (which it's not at the moment )

[jester]

I think there are several people definitly willing to test the scripts.
Ergozd beat me to it on alpha5  

jester.

[RobH]

I'm really interested in testing open-xchange on sme server!

I've been working on it with fedora core 3 and suse 9.2 & suse enterprise server, and would love to get it working on SME!

Rob.

[DarkMirage]

So I've posted new scripts, and I'm wondering. I don't know anything about perl, but I would like to integrate ox user administration with sme user administration. Seems to be something which shouldn't be that hard, if you know perl   Anybody any ideas?

I was also thinking of a user panel containing ox settings, but I'm wondering which settings would be interesting to put there...so please post your results here

I'm also interested to hear how tests with the script went..

[gregswallow]

Anybody any ideas?

Integrating it with SME would be ideal.  I don't know much about perl either, but I think you'd have to modify some files in the e-smith-base rpm, like /etc/e-smith/events/actions/user-create-unix, so that after a user is created, if OX is installed, it performs the steps to add the user to OX.  I think the key would be that if you modify any existing files, that they still work the same way if OX isn't installed.  

For any other configuration/templating that doesn't have to modify any existing files, maybe start with an rpm like e-smith-horde for reference and create e-smith-ox.

[dmac]

Could you have it that when OX is installed, it backs up the existing user manager file and replaces with the one that integrates the OX user creation script?  Then If you remove OX, restore the existing one.

Simple, but not elegant.

When running the Wget command, receive a 404 Not Found error.  Have you moved the location of the Script?

Darin

PS, will try the OX install script later today.  Have been battling with OX installation on Xandros and have about given up.

[gregswallow]

Could you have it that when OX is installed, it backs up the existing user manager file and replaces with the one that integrates the OX user creation script?  Then if you remove OX, restore the existing one.

That would work until you updated to a newer version of SME - e-smith-base is frequently modified and your changes would be overwritten.  Once it was figured out what changes exactly needed to be made to any existing files, then those changes could be submitted to the core developers in the form of a patch.  There is a good howto on patching rpms here: http://mirror.contribs.org/smeserver/contribs/dmay/smeserver/6.x/howto/rpm-patch-howto.html

[ergozd]

As I was surfing around I saw

http://www.linwave.de/index.php?id=153

May be of some help if we use the src.rpm file and re-generate for CentOS 3.4 (!)