From: Steve <gentoo_sjh@shic.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Web application for contact management...
Date: Fri, 19 Jun 2009 10:58:29 +0100 [thread overview]
Message-ID: <4A3B6145.101@shic.co.uk> (raw)
In-Reply-To: <200906161940.09928.michaelkintzios@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3007 bytes --]
Mick wrote:
> On Tuesday 16 June 2009, Steve wrote:
>
>> So far I've not got far with either Groupware suite... they're both
>> close - I wonder how hard it would be to tailor them... Hmmm.
>>
>
> Have a quick look at InfoLog of eGroupware. I think that either on its own,
> or as it integrates with AddressBook/ProjectManager/Calendar will do more
> than what you want. I'll be surprised if you need to customise it at all.
>
> I have not installed this application, but from a little reading I did, it
> seems simply a matter of running apache/MySQL/PHP and unpacking the
> filesystem of egroupware under your /var/www/htdocs/egroupware or what have
> you. The process is similar to drupal, or any other php based website/CMS
> that I have come across. Gentoo helps you do this by emerging egroupware and
> I suspect you will then run webapp-config to configure it.
>
I'm glad I persevered with eGroupware - it looks as if it should be
superb. While I'm still only beginning the learning curve, its features
do seem to be just what I was looking for.
One (of many) problems I'm having, however, relate to configuration/email...
At the setup phase, I get this rather un-nerving warning:
> Warning Checking PEAR::Auth_SASL is installed: False
> PEAR::Auth_SASL is needed by: EMailAdmin, felamimail. You can install
> it by running: pear install Auth_SASL
However, I've installed PEAR::Auth_SASL - and running the command gives me:
> $ pear install Auth_SASL
> Ignoring installed package pear/Auth_SASL
> Nothing to install
> $ pear -V
> PEAR Version: 1.6.2
> PHP Version: 5.2.9-pl2-gentoo
> Zend Engine Version: 2.2.0
> Running on: Linux svr 2.6.23-gentoo-r3 #5 SMP Tue Jan 8 22:41:42 GMT
> 2008 i686
> $
I've included the pear version info because all the problems I've found
via google have related to a Pear version of below 1.6.1.
Stumped by why the installation test for SASL failed, I ploughed on to
see where it took me. The answer to this, is as far as trying to access
my (working) IMAP server... eGroupware reports:
> *The connection to the IMAP Server failed!!*
>
> NO, Authentication failed.
I'm stumped as to quite what is wrong - it might be that SASL isn't
working; it might be that eGroupware is having a strop that my SSL Cert
for my IMAP server doesn't match the FQDN I'm using... or it might mean
that I've been bamboozled about how to configure eGroupware and it needs
me to configure usernames/passwords somewhere I've not found. Any hints
about this would be much appreciated.
On a more positive note, the address book (once I've got the hang of it)
combined with Infolog (assuming it continues to behave as it appears to
at the moment) are exactly what I was looking for. What's more, I'm
loving the integrated document management, issue tracker - and might
even make use of the timesheet facility in future. eGroupware is an
excellent find... Thanks... (all I need to do now is overcome the
configuration glitches...)
Steve
[-- Attachment #2.1: Type: text/html, Size: 3850 bytes --]
[-- Attachment #2.2: dep.png --]
[-- Type: image/png, Size: 701 bytes --]
next prev parent reply other threads:[~2009-06-19 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 20:30 [gentoo-user] Web application for contact management Steve
2009-06-14 22:04 ` Mick
2009-06-14 22:29 ` Joshua Murphy
2009-06-15 12:22 ` Steve
2009-06-15 22:08 ` Mick
2009-06-16 12:09 ` Steve
2009-06-16 13:27 ` Steve
2009-06-16 18:39 ` Mick
2009-06-19 9:58 ` Steve [this message]
2009-06-19 10:32 ` Steve
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A3B6145.101@shic.co.uk \
--to=gentoo_sjh@shic.co.uk \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox