-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
magic wrote:
> Hello all,
>
> I've been 'lurking' on the list for about 8 months now, and providing
> comments (as few as they are) whenever I can.
>
> I was wondering how the development process works. Is there a
> centralized list (a basic todo list) for the development direction
> Mandrake is heading?
>
Not really (as in not for previous releases) in terms of publicly
availble (I think that was previously handled internally only), the
cooker wiki is being tried for this. I had meant to put more scyrus
unix - n n - - pipe
user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -r ${sender} -m
${extension} ${user}
tuff in the wiki for LDAP/Mail etc, but haven't had the time. It is
supposed to be a big feature for the "TheBigPicture" entry (ie
out-the-box scalable http://email.uoa.gr/projects/squirrelmail/mail
server solution).
If you haven't got an accout in the wiki, make yourself one (if you have
a bugzilla acount). If you don't have a bugzilla account, mail
[EMAIL PROTECTED] (or Warly directly).
> The reason I ask, is that although I've been following the list, I
> can't seem to visualize the direction development is going (especially
> the server components).
>
> As I'm working on a corporate mailserver, I closely watch the cyrus
> (imap), postfix, openldap, cyrus (sasl) and other related threads. To
> say I've learned alot, would be an understatement.
>
The problem here is that the maintainers of said packages may not be
running the packages in production, so contributors who do often have
greater needs than the maintainer (which is a good reason to get more
contributors write access to the specific component in main).
Florin, I have all the packages (see below) necessary for the migration
away from sasl1 and to db4.1 (well, on the mail server side, ie postfix,
cyrus-imapd/sasl2 from Luca with some small changes, openldap). Someone
still needs to look at ensuring an upgrade from openldap-2.0.x to
openldap-2.1.x with some broken entries will still work (possibly just
by turning schema checking off on an upgrade). I haven't got any
openldap-2.1 servers in our setup here yet, in fact I am waiting to test
whichever package goes into cooker to see if our replication (from 2.0.x
master) still works after an upgrade.
> So, how does the cooker work? What decides if a package goes into
> main, or is a contrib? What determines if a cooker package moves into
> updates?
Only packages in main get updates.
> And if (in the mailserver case above) how is it determined what
> packages are added, and when?
>
On the whim of the maintainer ;-).
> And finally, why doesn't [EMAIL PROTECTED] .com ever answer an email?
It does sometimes, but AFAIK the frequency/response time is inhibited by
Warly's workload ...
BTW, we have now got our new server that will take over mail serving
setup, in production for file serving currently, it will go into
production mail serving once we have migrated our UW mailboxes to cyrus.
We have authentication via LDAP/saslauthd working (I have rebuilt
everything against db4.1, openldap-2.1, sasl2), I still need to look at
postfix auth and mail routing, then antivirus/spam (probably with either
amavis-ng or amavisd-new).
Then, I was wondering if anyone has looked at this:
http://email.uoa.gr/projects/squirrelmail/
We are currently running squirrelmail on our old server, but it required
users to fill in details that were already in LDAP (which this seems to
fix). I was just wondering if anyone who works heavily with cyrus and/or
squirrelmail has looked at these (and the patches/changes).
Then, as someone else had mentioned, it might be an idea to have postfix
work out-the-box with server-side spam prevention and virus-scanning.
This would require that something like amavisd-new go into main (I think
spam-assassin is already in main?). Possibly also clamav? Or would it be
simple enough for the user to just uncomment the appropriate entries in
the main.cf if the right changes are made to the default master.cf?
While on the subject of postfix, there is a small change that should be
made to the cyrus transport to work out-the-box (gc?):
This is the current default transport for cyrus:
cyrus unix - n n - - pipe
user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
Where it should be:
cyrus unix - n n - - pipe
user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -r ${sender} -m
${extension} ${user}
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+9syjrJK6UGDSBKcRAtoGAJ45lQcH3bJZ4iRsc5oDN1NxO/LWDgCfXHyI
VrH933fLNlc4Mj945ePLJWw=
=dzRM
-----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.
******************************************************************
