Small error in a 2.3.8 patch + some info on a critical bug

[Farzad FARID]

Hi folks,

Sorry for not having contributed to the 2.3 branch recently as I've been
busy with non mail related projects recently...

I haven't checked the entire commit logs for the 2.3.8 branch, but I
nevertheless spotted an error in the postrm patch:

debian at incase.de a écrit :
> Author: sven
> Date: Fri Jun 22 15:18:25 2007
> New Revision: 738
>
> [...]
>  			db_get cyrus-common-2.3/removespools
>  			[ "${RET}" =3D "true" ] && {
> -				for i in /var/spool/cyrus /var/lib/cyrus \
> -				         /var/spool/sieve /etc/sieve ; do
> -				        find "$i" -type f -exec rm -f '{}' \; || true
> -				        find "$i" -type d -depth -not -name 'lost+found' -exec rmdir '=
> {}' \; || true
> +					 /var/spool/sieve /etc/sieve ; do
> +					find "$i" -type f -exec rm -f '{}' \; || true
> +					find "$i" -type d -depth -not -name 'lost+found' -exec rmdir '{}' \; =
> || true
>  				done
>   
This patch deletes the "for i in..." by mistake.

By the way, I have an written a (somewhat ugly) patch against 2.3.7 to
correct a critical problem related to the use of "unified murder"
setting. I don't know if the problem appears in other murder
configuration, but it is critical enough to deserve a patch, although
nobody ever responded to my mails in the "info-cyrus" list. If my memory
doesn't fail me, the cyrus bugzilla even seems to indirectly mention
this problem, in a very old ticket that has never been resolved.
Unfortunately I don't remember the ticket number. I think the settings
were so peculiar at that time in september 2006 (unreleased 2.3.7,
unified murder config), that nobody else had this same setup.

You can check my posts entitled "Loss of mail with Murder+LMTP (imapd
2.3.7): incoming mail rejected just after server restart":
http://lists.andrew.cmu.edu/pipermail/info-cyrus/2006-September/023595.html
and
http://lists.andrew.cmu.edu/pipermail/info-cyrus/2006-September/023695.html

I don't know if the 2.3.8 release corrects this problem, I have neither
checked the diffs nor upgraded my customer's config (which by the way
seems to work like a charm with Debian Cyrus 2.3.7 and a unified murder
config, and has not been restarted since I installed it in november
2006!). Without this patch, during the imap server startup time (when
the processes are being launched, but the mupdate slave is not ready
yet) all mails sent with LMTP by the postfix server are rejected with a
fatal error and therefore lost.

I have attached my patch to this mail. I'd appreciate your comments, and
would be more than glad if someone could reproduce the problem or
confirm that it is solved :) "karavel" is the name of my customer. I
added depencencies on "psmic" and "iptables" to be able to add my checks
in the startup script, I warned you that the patch was ugly ;)

 Best regards,

-- 
Farzad FARID / Architecte Open Source - Associé
Pragmatic Source / http://www.pragmatic-source.com
Tel : +33 9 53 19 21 90 / Mob : +33 6 03 70 65 46
Rejoignez mon réseau de contacts :
 http://www.viadeo.com/invitationpersonnelle/002ic6twokcvmi

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 95-karavel-specific.dpatch
Url: http://lists.alioth.debian.org/pipermail/pkg-cyrus-imapd-debian-devel/attachments/20070626/9681ddb7/attachment.txt