
Any comments from any one?kowal wrote:OX Gentoo HOWTO specifies to modify ldap ebuild by adding code with round bracketsI think it should be curley bracket as belowCode: Select all
myconf=$(myconf) --enable-aciEmerging ldap with round brackets brings up error right at the beginningCode: Select all
myconf=${myconf} --enable-aciCode: Select all
/usr/lib/portage/bin/ebuild.sh: line 1: myconf: command not found
Code: Select all
myconf="${myconf} `use_enable crypt`"
myconf="${myconf} `use_enable ipv6`"
myconf="${myconf} `use_with sasl cyrus-sasl` `use_enable sasl spasswd`"
myconf="${myconf} `use_with readline`"
myconf="${myconf} `use_with ssl tls` `use_with samba lmpasswd`"
myconf="${myconf} `use_enable tcpd wrappers`"
myconf="${myconf} `use_enable odbc sql`"
myconf="${myconf} `use_enable perl`"
myconf="${myconf} `use_enable slp`"
HOWTO fixed and updated...init-zero wrote:about the proper syntax of an ebuild ?
it should be { }
Check out the ebuild you will see a few examples of the same..
Code: Select all
myconf="${myconf} `use_enable crypt`" myconf="${myconf} `use_enable ipv6`" myconf="${myconf} `use_with sasl cyrus-sasl` `use_enable sasl spasswd`" myconf="${myconf} `use_with readline`" myconf="${myconf} `use_with ssl tls` `use_with samba lmpasswd`" myconf="${myconf} `use_enable tcpd wrappers`" myconf="${myconf} `use_enable odbc sql`" myconf="${myconf} `use_enable perl`" myconf="${myconf} `use_enable slp`"


Code: Select all
access to dn="ou=addr,uid=(.*),ou=Users,ou=OxObjects,dc=zednax,dc=com" attr=uid,objectClass,entry filter=(objectClass=OXUserObject)
by self write
by dn="uid=$1,ou=Users,ou=OxObjects,dc=zednax,dc=com" write
by * none
access to dn.subtree="o=AddressBook,ou=OxObjects,dc=zednax,dc=com"
by group="cn=AddressAdmins,o=AddressBook,ou=OxObjects,dc=zednax,dc=com" write
by users read
by * none

Hula project - Novell and Netline, perfect together.
You may have already seen the exciting announcement by Novell and Netline on the Hula Project -- a new community project to create an open source e-mail and collaboration server.
Novell and Netline decided several months ago to have two independent open source projects independent but also very complementary. That strategy gives Netline the opportunity to cooperate first with Novell, but allows us also to keep our overall integration approach in place -- for client and server infrastructure -- and also be able to cooperate with other vendors in the market.
Only after Netline had open sourced OPEN-XCHANGE was Novell in a position to complement Netmail with this well established open source project.
Hula and Netline are a perfect complement. Where the strengths of Netmail are on the infrastructure side, OPEN-XCHANGE is something completely different: a modular, modern, open, standards-based architecture with superior groupware features and integration capabilities with other groupware environments like Microsoft Exchange.
Hula is positioned as a solid mail server with an open architecture, where OPEN-XCHANGE will expand that functionality to become a real collaboration solution. Hula is not able to support the Outlook client and they are not intending to do so, because their technical and feature approach does not match with Outlook features.
Using NetMails NMAP protocol now available through public licenses as part of this initiative -- in addition to the standard SMTP/LDAP protocols allows for richer functionality and much tighter integration of OPEN-XCHANGE and e-mail in general, enabling the community to create even more advanced functionality.
Combining these advanced mail functions with our award-winning collaboration attributes gives the open source world a rallying point to create a competitive alternative to the traditional proprietary solutions.
We will use Hula as a scalable and robust mail server when we ship OPEN-XCHANGE through Novells channels. But we will not rely completely on the Hula mail server technology. It is simply one of several options for the customer.
Making e-mail part of the standard data formats mix of OPEN-XCHANGE creates a significant addition to the "personal information hub" platform functionality of OPEN-XCHANGE. And adding replication by e-mail to this "hub" will make this information location independent, allowing for integration of mobile devices of all kinds and for multi-site and cluster configurations.
In the future, adding Novells Identity Management and products such as Evolution and iFolders will provide a powerful end-to-end solution to customers so far unavailable in the Linux space.
Please join us in embracing this important initiative.
Frank Hoberg (CEO) & Martin Kauss (CTO)
Netline Internet Service GmbH
So I said, narrow the focus. Your "use case" should be, there's a 22 year old college student living in the dorms. How will this software get him laid?
That got me a look like I had just sprouted a third head, but bear with me, because I think that it's not only crude but insightful. "How will this software get my users laid" should be on the minds of anyone writing social software (and these days, almost all software is social software).
which was explained in OX_install-v0.15-1.pdf .SMTP Authentication and Relay Control
/etc/postfix/main.cf
Code: Select all
smtpd_sasl_auth_enable = yes smtpd_sasl2_auth_enable = yes smtpd_sasl_security_options = noanonymous broken_sasl_auth_clients = yes smtpd_sasl_local_domain = smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination
The above URL does not seem to be valid as of now. Is it updated?bitwh0re wrote:Good day all,
I've finished a rough draft outlining how to get OX installed on Gentoo using:
- Postfix / Cyrus / SASL
- OpenLDAP
- Apache 2 / Tomcat 5
- PostgreSQL
As I said, it's a rough draft, so I don't go into detail on each services but it should give you enough info to get the basics for OX up and running. I welcome any comments, suggestions, fixes, and additions. You can currently find it in PDF here:
http://www.mikefetherston.ca/OX/OX_Install.pdf
Yes, the HTML HOWTO is still in "beta" even though it covers a completely updated install of 0.7.5. If you're looking for those "extra" instructions you can find them in the PDF still. I plan on updating the HOWTO to cover OX v0.8PR. At that time I also plan to add the supplemental instructions from the PDF HOWTO.leynux wrote:It works extremely wonderful to me..![]()
In the "HOWTO: Gentoo Open-Xchange Installation v0.20b" , it miss this partwhich was explained in OX_install-v0.15-1.pdf .SMTP Authentication and Relay Control
/etc/postfix/main.cf
Code: Select all
smtpd_sasl_auth_enable = yes smtpd_sasl2_auth_enable = yes smtpd_sasl_security_options = noanonymous broken_sasl_auth_clients = yes smtpd_sasl_local_domain = smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination
Thanks a lot..
Chotchki, glad to hear it helped you out! The HOWTO is geared towards Gentoo, but if you're familiar with Linux you can easily adapt it to your distro of choice. I intended it to be a guide to take you from a completely fresh and bare Gentoo install to a working mail and ldap server and then build on that to get OX working, which explains the length of the document.chotchki wrote:I would like to send out a big thank you for all those who help write this document. After fighting with Fedora 3, I am halfway through the install with this guide. If all goes well this should be a great way to sneak gentoo into my organization.
Hope that can help anyone attempting the OX0.8PR install!Hi All
I've manged to get the OX 0.8 Administration tools working on SuSE 9.2
and Martin Kauss sugested I tell you all about it. This may work on
other platforms but let me know...
1. Extract OX and run a ./configure with all the options
2. Edit the OXEXTRACTION/system/umin/oxuserminconfig.properties and edit
the LDAP details so they
match what OpenLDAP is set with (I had to change the
LDAP_BASEDN=dc=example,dc=org line)
3. Run a make and make install
4. Copy the PREFIX/lib/umin.war to TOMCATHOME/webapps
5. Restart Tomcat
6. Check that umin.war has extracted into TOMCATHOME/webapps/umin
7.
a.) If using mod_jk2, edit workers2.properties with
[uri:/umin/*]
worker=ajp13:localhost:8009
b.) If using mod_jk (like I was), edit your /etc/apache2/conf.d/jk.conf
with
JkMount /umin/* ajp13
8. Restart Apache2
9. It works!
As I said, let me know how you get on.
Seb
_______________________________________________
General mailing list
General@open-xchange.org
http://www.open-xchange.org/cgi-bin/mai ... fo/general