[Kroupware] Trial run with kmail and outlook bynari plugin
ralph escherich
kroupware@mail.kde.org
Mon, 16 Dec 2002 15:48:10 -0800
--------------010808090204050201000106
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Martin Lillepuu wrote:
>Ühel kenal päeval (esmaspäev, 16. detsember 2002 19:54) kirjutas ralph
>escherich:
>
>>1. SMTP authentication with postfix using outlook does not work.
>> I added the broken_sasl_auth_clients = yes switch to the
>> postfix main.cf, but still it didn't work.
>> The following variable has to be set this way:
>> smtpd_sasl_local_domain = $mydomain.
>> This is crucial, because smtp authentication seems to use
>> <name>@domain as the ID for authentication. If
>> smtpd_sasl_local_domain does not match the domain id part
>> of your email address in the ldap database, authentication
>> will fail with all clients.
>>
>
>I could not get this working either. Nice to know that there's simple
>workaround to get it working.
>Btw, did you get server side filters (sieve) working?
>
I did not try the sieve stuff yet, but I'll start looking into it
>
>
>>3. kmail/calendar <-> kmail/calendar
>> works well. A lot of features are still missing in the KDE
>> client, like gantt chart like calendar, automatic viewing
>> of free/busy for attendees, accept, reject, propose new time
>> features.....
>>
>
>At least accepting/rejecting appontments was there and working correctly for
>me.
>
Our mistake was to take the last official kde3.1, not the latest cvs
head. We are compiling it right now
and I'll try then again.
>
>>4. kde client <-> outlook
>> this does not work for me at all. Appointments sent from
>> outlook are not interpreted correctly by kmail. Its showing
>> up as a regular mail, and the vcalendar mime stuff is
>> not looked at
>> Appointments sent out by the kde calendar tool are recognized
>> as an icalendar format, but there are not accept, reject ...
>> possibilities in outlook. The messages are either not completely
>> assembled or outlook does not understand them right.
>>
>
>I didn't have much luck with this one either. But after testing I discovered
>this document and I suppose enabling iCAL should be the key (haven't had the
>time to test it yet):
>
>http://kolab.kde.org/concept-1.0.1/c493.html
>
I read the document and configured as suggested. Still didn't work. I'll
try with the latest
cvs head again and will let you know.
>
>>5. free busy posting
>> free/busy posting from outlook does not work with the ftp approach.
>> I made a shared disk space though samba and that worked. I guess
>> the ftp server coming from kolab is not configured right to allow
>> anonymous access without a password.
>>
>
>Same here, even though I enabled both ftp/http free-busy services from admin
>interface and added according urls to outlook free-busy options. No luck with
>free-busy.
>
>>- to be able to achieve easy migration from one email server to another,
>> changing the email address should be possible. right now, once a user
>> is put into the system, the email address cannot be changed.
>>
>
>I tried moving kolab from one system to another (suse 8.0 -> debian 3.0). Only
>problem I had was with sldapd picking up depenency of db4 from "outside" the
>bootstrap environment and thus had to be rebuilt on debian system. after
>building and installing openpkg bootstrap, it was only matter of tar/untar.
>changing users e-mail domain names was simple operation of:
>
> 1) dump ldap schema
> 2) replace olddomain -> newdomain with texteditor
> 3) reload ldap schema.
>
Thanks for the suggestion here, how do I dump the ldap schema and relaod
it??
>
>>- a check should be performed when kolab is started up (maybe part of
>> the rc script) to check if any other daemons that are using kolab ports
>> are running. I had some problem figuring out why postfix, ftp where not
>> running properly.
>>
>
>I guess QIM should mention that one must disable/remove any
>smtp/imap/pop3/web/ldap services currently running on the server before
>trying kolab but IMO it's quite obvious anyway.
>
Yes, QIM would be a good start. The automatism can come at a later more
mature state.
I only mentioned it to be complete.
>
>>- using the unix id and passwd instead of storing new information in the
>>sasl
>> ldap database should be an option. Otherwise the double password mess
>>starts
>> again.
>>
>
>would it be possible to add unix userid (and passwd?) data to existing kolab
>user schema and then configure pam to authenticate against it?
>
I actually thought the same thing. I read somewhere that the sasl
package can work with pam, but didn't
have a chance to try it out. Maybe a more experienced developer can give
us some hint here.
>
--
Ralph Escherich 2900 Gordon Avenue Suite 203
Senior IC Design Engineer Santa Clara, CA 95051-0718
Phone: 408-328-9333
Fax: 408-735-1163
http://www.mobilesmartsinc.com
--------------010808090204050201000106
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit
<html>
<head>
</head>
<body>
<br>
<br>
Martin Lillepuu wrote:<br>
<blockquote type="cite" cite="mid:200212170201.08193.martin@lillepuu.com">
<pre wrap="">Ühel kenal päeval (esmaspäev, 16. detsember 2002 19:54) kirjutas ralph <br>escherich:<br><br></pre>
<blockquote type="cite">
<pre wrap="">1. SMTP authentication with postfix using outlook does not work.<br> I added the broken_sasl_auth_clients = yes switch to the<br> postfix main.cf, but still it didn't work.<br> The following variable has to be set this way:<br> smtpd_sasl_local_domain = $mydomain.<br> This is crucial, because smtp authentication seems to use<br> <name>@domain as the ID for authentication. If<br> smtpd_sasl_local_domain does not match the domain id part<br> of your email address in the ldap database, authentication<br> will fail with all clients.<br></pre>
</blockquote>
<pre wrap=""><!----><br>I could not get this working either. Nice to know that there's simple <br>workaround to get it working. <br>Btw, did you get server side filters (sieve) working?</pre>
</blockquote>
I did not try the sieve stuff yet, but I'll start looking into it<br>
<blockquote type="cite" cite="mid:200212170201.08193.martin@lillepuu.com">
<pre wrap=""><br><br></pre>
<blockquote type="cite">
<pre wrap="">3. kmail/calendar <-> kmail/calendar<br> works well. A lot of features are still missing in the KDE<br> client, like gantt chart like calendar, automatic viewing<br> of free/busy for attendees, accept, reject, propose new time<br> features.....<br></pre>
</blockquote>
<pre wrap=""><!----><br>At least accepting/rejecting appontments was there and working correctly for <br>me.<br></pre>
</blockquote>
Our mistake was to take the last official kde3.1, not the latest cvs head.
We are compiling it right now<br>
and I'll try then again.<br>
<blockquote type="cite" cite="mid:200212170201.08193.martin@lillepuu.com">
<pre wrap=""><br></pre>
<blockquote type="cite">
<pre wrap="">4. kde client <-> outlook<br> this does not work for me at all. Appointments sent from<br> outlook are not interpreted correctly by kmail. Its showing<br> up as a regular mail, and the vcalendar mime stuff is<br> not looked at<br> Appointments sent out by the kde calendar tool are recognized<br> as an icalendar format, but there are not accept, reject ...<br> possibilities in outlook. The messages are either not completely<br> assembled or outlook does not understand them right.<br></pre>
</blockquote>
<pre wrap=""><!----><br>I didn't have much luck with this one either. But after testing I discovered <br>this document and I suppose enabling iCAL should be the key (haven't had the <br>time to test it yet):<br><br><a class="moz-txt-link-freetext" href="http://kolab.kde.org/concept-1.0.1/c493.html">http://kolab.kde.org/concept-1.0.1/c493.html</a> <br></pre>
</blockquote>
I read the document and configured as suggested. Still didn't work. I'll
try with the latest<br>
cvs head again and will let you know.<br>
<blockquote type="cite" cite="mid:200212170201.08193.martin@lillepuu.com">
<pre wrap=""><br></pre>
<blockquote type="cite">
<pre wrap="">5. free busy posting<br> free/busy posting from outlook does not work with the ftp approach.<br> I made a shared disk space though samba and that worked. I guess<br> the ftp server coming from kolab is not configured right to allow<br> anonymous access without a password.<br></pre>
</blockquote>
<pre wrap=""><!----><br>Same here, even though I enabled both ftp/http free-busy services from admin <br>interface and added according urls to outlook free-busy options. No luck with <br>free-busy.<br><br></pre>
<blockquote type="cite">
<pre wrap="">- to be able to achieve easy migration from one email server to another,<br> changing the email address should be possible. right now, once a user<br> is put into the system, the email address cannot be changed.<br></pre>
</blockquote>
<pre wrap=""><!----><br>I tried moving kolab from one system to another (suse 8.0 -> debian 3.0). Only <br>problem I had was with sldapd picking up depenency of db4 from "outside" the <br>bootstrap environment and thus had to be rebuilt on debian system. after <br>building and installing openpkg bootstrap, it was only matter of tar/untar.<br>changing users e-mail domain names was simple operation of:<br><br> 1) dump ldap schema<br> 2) replace olddomain -> newdomain with texteditor<br> 3) reload ldap schema.<br></pre>
</blockquote>
Thanks for the suggestion here, how do I dump the ldap schema and relaod
it??<br>
<blockquote type="cite" cite="mid:200212170201.08193.martin@lillepuu.com">
<pre wrap=""><br></pre>
<blockquote type="cite">
<pre wrap="">- a check should be performed when kolab is started up (maybe part of<br> the rc script) to check if any other daemons that are using kolab ports<br> are running. I had some problem figuring out why postfix, ftp where not<br> running properly.<br></pre>
</blockquote>
<pre wrap=""><!----><br>I guess QIM should mention that one must disable/remove any <br>smtp/imap/pop3/web/ldap services currently running on the server before <br>trying kolab but IMO it's quite obvious anyway.<br></pre>
</blockquote>
Yes, QIM would be a good start. The automatism can come at a later more mature
state. <br>
I only mentioned it to be complete.<br>
<blockquote type="cite" cite="mid:200212170201.08193.martin@lillepuu.com">
<pre wrap=""><br></pre>
<blockquote type="cite">
<pre wrap="">- using the unix id and passwd instead of storing new information in the<br>sasl<br> ldap database should be an option. Otherwise the double password mess<br>starts<br> again.<br></pre>
</blockquote>
<pre wrap=""><!----><br>would it be possible to add unix userid (and passwd?) data to existing kolab <br>user schema and then configure pam to authenticate against it?<br></pre>
</blockquote>
I actually thought the same thing. I read somewhere that the sasl package
can work with pam, but didn't<br>
have a chance to try it out. Maybe a more experienced developer can give
us some hint here.<br>
<blockquote type="cite" cite="mid:200212170201.08193.martin@lillepuu.com">
<pre wrap=""><br></pre>
</blockquote>
<br>
<pre class="moz-signature" cols="$mailwrapcol">--
Ralph Escherich 2900 Gordon Avenue Suite 203
Senior IC Design Engineer Santa Clara, CA 95051-0718
Phone: 408-328-9333
Fax: 408-735-1163
<a class="moz-txt-link-freetext" href="http://www.mobilesmartsinc.com">http://www.mobilesmartsinc.com</a></pre>
<br>
</body>
</html>
--------------010808090204050201000106--