-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

magic wrote:
> Buchan Milne wrote:
>
>> But, note that it seems this patch only makes it *possible* to enable
>> auto-creation, which AFAIK defaults to off. If it is enabled, it can
>> auto-create mail subdirectories and auto-subscribe a user to certain
>> mailboxes, but even if this *is* enabled, manual mailbox creation does
>> not do this. While mailbox autocreation may not be desired on some
>> systems, on any ldap system, it may be preferable to something like
>> kolab (which I still want to investigate packaging, I have a package
>> already, but it needs a lot of work to get it working still ...)
>>
>> Luca (Olivetti), I have just added this patch (or actually the more
>> up-to-date one from Simon Matter's SRPM), which at present I have done
>> as another conditional (--with autocreate), even though I think it would
>> be safe to apply the patch (I will test both with and without the
>> directives in /etc/imapd.conf to see) by default.
>>
>>
>
>   I think I already know the answer to this, but are you compiling
> against db41?

Yes.

> Are you building under a (modified) 91 or cooker
> environment?

9.1, db4.1, openldap-2.1.x (not sure which version is on the server in
question), sasl2 (which I still need to look into, specifically some
patches I received) and postfix. We have put this project back on the
front burner, we hope to take this machine into production as our mail
server within the next week or two.

> Finally, will you be posting the srpm on your site when you
> get finished?

Those which aren't already in cooker.

> I would be very interested in rebuilding on my (slightly
> modified) 91 mailserver build. - The auto creation would be very useful
> to me (as you pointed out) in an ldap environment.
>
>   Also of note, (it's my understanding) the mailbox creation &
> subscribing happens when the new user logs-in to the account for the
> first time, not upon reciept of a mail when the mailbox does not exits.
> (I know there was some concern about this in an earlier thread.)
>

- From the section added to imapd.conf(5) by the patch:
"createonpost: no
            If  yes,  when  lmtpd  receives an incoming mail for an
INBOX that
            does not exist, then the INBOX is automatically created by
lmtpd."

Note, I think the concern about this was that it would be the *default*
behaviour, whereas it would not be.

At least, that is if it works ... at present I haven't got it working ...

>> Another issue is that there are some scripts (cpmsg,
>> bsd2cyrus,folderxfer,batchreconstruct,inboxfer) in Simon Matter's
>> cyrus-imapd for converting from mbox (ie UW-IMAP) format, which you
>> don't have. Since we need to convert from mbox anyway, I would like to
>> add this. Any objection? Should I make a subpackage (they seem to depend
>> on formail, thus will depend on procmail, which would be a bit of a
>> waste ;-)).
>
>   I think the idea of a sub package would be good for the conversion
> utilities. (Not having to worry about added dependancies is a bonus for
> me, as I would not need/use the conversion utilities.)

Hmmm, I wonder if it would be useful to have a 'cyrus-imapd-migration'
package. I will try that.

Regards,
Buchan

- --
|--------------Another happy Mandrake Club member--------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x202
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/HWvprJK6UGDSBKcRAol1AJwP5ejNMIKda/1EoLm2k4J8yu81IQCfSCZy
31g6a2uEOKkTI4UdtT7jRk0=
=DVFx
-----END PGP SIGNATURE-----

******************************************************************
Please click on http://www.cae.co.za/disclaimer.htm to read our
e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy.
******************************************************************

Reply via email to