If it means that HEAD won't be useable for a day or two, I don't think that you should worry about it. Better that more people are able to see some of the GMime code and begin to understand it, even if it isn't 100% ready.
Aaron Paul J Stevens <[EMAIL PROTECTED]> said: > It's in the retrieval code. GMime does some reformatting in the > mimeheaders (un-wrapping of headers, and unquoting of attributes) > of the mimeparts which are apparently confusing the old mimeparser > used in the retrieval code. > > If it's something minor in the current mimeparser, I'll fix it. > Otherwise, I'll back out the insertion code committed today, and > work on the retrieval code to use gmime as well first. > > I wont be able to work on this until around 12:00 gmt tomorrow. > > Paul J Stevens wrote: >> Sorry guys, >> >> Something is still amiss in the insertion code. I'm on it. >> >> Paul J Stevens wrote: >> >>> >>> Hi all, >>> >>> As promised, I've committed the first gmime code fragments. They are >>> currently used for message insertion only. >>> >>> * dbmail-message.c, dbmail-message.h: new files implement >>> DbmailMessage object and interfaces. >>> * Makefile.am: added dbmail-message.c to COMMON files list >>> * acinclude.m4, configure.in: added gmime support >>> * db.c, db.h, header.c, header.h, lmtp.c, main.c, pipe.c, >>> pipe.h: use new gmime code in dbmail-message.c for message >>> insertion. >>> >>> Please test this code. It works for me, but I'm curious if this solves >>> Dan's problems with dbmail-smtp. >>> >>> >>> >> > > > -- > ________________________________________________________________ > Paul Stevens mailto:[EMAIL PROTECTED] > NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED] > The Netherlands________________________________http://www.nfg.nl > _______________________________________________ > Dbmail-dev mailing list > [email protected] > http://twister.fastxs.net/mailman/listinfo/dbmail-dev > --
