-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Luca Olivetti wrote: > Buchan Milne wrote: > >> >> Luca (Olivetti), I have just added this patch (or actually the more > > > I hope you did it to the latest (2.1.14-2mdk) rpm, not to 2.1.14-1mdk.
Yes, I started with your -2mdk. > >> 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 find this patch *extremely* dangerous, but I won't complain too loudly > if the option is left disabled in the default config file. Well, at present it's not applied unless rebuilt with "--with autocreate", but if people are happy that the default config won't be a spam-trap, then maybe we should apply it by default, but keep the default config safe. Thus far it seems ok as such (I got some rejected mail trying to get it to work ;-)). > Note that it > doesn't support murder (see http://email.uoa.gr/autocreate/) > I did notice. >> >> 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'd prefer a *separate* package As in seperate SRPM? >, for a couple of reasons, one because > these are separate, stand alone utilities, and could have a different > release cycle than cyrus (note that they aren't released as a tarball so > it's difficult to track for new versions). Yes, I made a tarball of it ;-). > The other is that there are a > bazillion other utilities to convert from one mail format to another, > mbox to imap or imap to imap, (e.g. I used something from UW imap > utils), and it doesn't make sense to package all of these utilities in > the same SRPM. Well, I would be happy to find *one* solution that: 1)works 2)is not too difficult to use to convert a whole server 3)is free enough to package 4)has no extra requirements I have just tried the bsd2cyrus/folderxfer etc script, but cpmsg doesn't seem to want to do anything with the formail output. BTW, I consider this to be a relatively significant issue, since it seems 95% of all users who start a mail server on Mandrake get trapped in uw-imap, so I feel we should provide an easy way to escape! > Maybe batchreconstruct is the only one really cyrus > specific, but I cannot comment since I didn't need it so far (in ~4 > years of cyrus use). > >> >> Finally, there are a few other patches you don't have, any particular >> reason, or can they be added as well? >> cyrus-imapd-2.1.11-snmpargs.patch > > > the comment and the spec file say that it's only needed for redhat 6.2. > Anyway snmp is disabled in Simon's (and my) package. If someone needs/is > using snmp with cyrus he could give us some advice (on needed > buildrequires, patches, etc.). > Hmmm, the web monitor thingy in contrib would need snmp, and it might be interesting to try it out, but I haven't yet, but I will assume we don't need the patch. >> cyrus-imapd-2.1.14-ipv6-20030703.diff.gz > > > Don't use ipv6 myself so I cannot check if it's working correctly (I > don't doubt the author's knowledge, but mine and/or strange interactions > with linux and/or mandrake). I could test if it builds but nothing more. > If it doesn't break anything (i.e. someone *really* test its > functionality with the mandrake package) I'll have no problem in > including it. But the same problem would arise with the next version of > cyrus-imapd+ipv6 patches. > Indeed. I don't have access to ipv6, but it would be nice if someone could test ipv6 stuff, but I guess if it's not in the mainstream source, it probably means it's not ready yet ... >> cyrus-imapd-2.1.3-flock.patch > > > IIRC (but I may be wrong) it wasn't the correct solution for the problem > at hand and CMU folks were skeptical about this patch: > > http://asg.web.cmu.edu/archive/message.php?mailbox=archive.info-cyrus&msg=15115 > > > note that there's also cricisism about the munge8bit patch, and I'm not > too happy to have it (but if the option is disabled it won't do too much > harm). > A followup message says that recent kernels don't have this problem (and > this was a year ago). OK, then I guess it will come down to adding the optional auto-create patch, and finding the best set of scripts to package up for migrating. 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/HYTjrJK6UGDSBKcRAt3RAKCdD1Z+w2lHCdUMnd9xQV2E1tYSbACdGwtI 7dn/9fxCai8o+RhFuwtKjrc= =DaJd -----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. ******************************************************************
