[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: checked in sieve code - correction to build instructions

From: Alain Magloire
Subject: Re: checked in sieve code - correction to build instructions
Date: Sat, 9 Jun 2001 14:39:32 -0400 (EDT)

> Quoting Alain Magloire <address@hidden>, who wrote:
> > > 
> > > Unused, hardly, all caveats apply.
> > > 
> > > To build, add sieve/Makefile to the AC_OUTPUT statement
> > > at about line 165 of configure.in.
> And add sieve to the SUBDIRS line in the top-level Makefile.am.


> > > -- off topic --
> > > 
> > > I suspect my mbox-explode.c example app of currupting and
> > > truncating a large maibox of mine while running on it and
> > > being SIGINTed, despite having opened it readonly. Also, it
> > 
> > In theory that is not possible, if you open the file readonly
> > you simply can not write to it.  It is not mailutils/mailbox
> > that is preventing this but the OS since the file was open (, O_RDONLY);
> > and for mmap(, PROT_READ);
> > So my guess is, the orginal mailbox was already corrupted
> > by previous experiences and it was unnoticed.
> I haven't been able to prove this, but I'm confused. It's was
> a new mailbox, just written with the results of all the daily
> tests. You are sure that the mailbox isn't opened writeable
> briefly to update/add the Status and uid header fields?

Yep.  The expunge will fail, this is what jakob was seeing with mailutils/mail.
If you pass MU_STREAM_READ, it will be open readonly and all of the
stream_write() will fail. 100% positive, unless :
- libc functions are buggy which I doubt.
- The mailobx was already corrupted and you happen to notice it now.

> The only other program I used was mutt to look at the mailbox.

> I haven't been able to duplicate this, so I guess it's kind of
> nebulous. I was hammering the disk pretty had, linux was basically
> frozen, who knows what could have caused this.

Linux when trashing sometimes kills processes to reclaim memory.

> > > I am trying to save, which may be me using the wrong apis,
> > > or related to the mbox being corrupted, I'm trying to
> > > figure out what happened.
> The reason I was hammering the disk so hard was i was saving
> the entiry msg as an attachment, instead of the part, oops. I'll
> patch the mbox-explode.c soon. But first, spring cleaning.

Yes, I've notice.  I will commit this, since there is one more fix.
Some of my mails did not have a Subject: field and you exit()ed
how rude!

> But first, spring cleaning.

8-), I'm trying to cut the grass here.  There is so many mosquitos
it's like going to a red cross blood donation.
I'm going back to the bushes/war as soon as I get my blood pressure
back again.

- The filter/stream quoted-printable since to be buggy, the attachments
are not well decoded.  Base64 seems solid.

- cvs update -d -P
to get mailbox2, the new mailbox API, pop3 implemented.

au revoir, alain
Aussi haut que l'on soit assis, on est toujours assis que sur son cul !!!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]