Paul J Stevens wrote:
Jake Anderson wrote:
Any idea when the next version will be a "release"?
(2.3.5)
I've held off migrating my production system untill this system is
"stable" ish
Looks like that's pretty close now. (I'm just not a big fan of compiling
my own code)
2.3.5 is getting
Jake Anderson wrote:
> Any idea when the next version will be a "release"?
> (2.3.5)
> I've held off migrating my production system untill this system is
> "stable" ish
> Looks like that's pretty close now. (I'm just not a big fan of compiling
> my own code)
2.3.5 is getting very close. There are
Any idea when the next version will be a "release"?
(2.3.5)
I've held off migrating my production system untill this system is
"stable" ish
Looks like that's pretty close now. (I'm just not a big fan of compiling
my own code)
Paul J Stevens wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stirr = ?
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:dbmail-dev-
> [EMAIL PROTECTED] On Behalf Of Paul Stevens
> Sent: terça-feira, 18 de Novembro de 2008 22:13
> To: DBMAIL Developers Mailinglist
> Subject: Re: [Dbmail-dev] DBMail 2.3.4 released
>
>
ro de 2008 7:55
To: DBMAIL Developers Mailinglist
Subject: Re: [Dbmail-dev] DBMail 2.3.4 released
Fool proof:
git fetch
git clean -f -x -d
git reset --hard origin/master
this will always reset your tree to the state of the remote master.
In this case you probably changed something manually in d
feira, 18 de Novembro de 2008 7:55
> To: DBMAIL Developers Mailinglist
> Subject: Re: [Dbmail-dev] DBMail 2.3.4 released
>
>
> Fool proof:
>
> git fetch
> git clean -f -x -d
> git reset --hard origin/master
>
> this will always reset your tree to the state o
it/dbmail#
>
>
>
>> -Original Message-
>> From: [EMAIL PROTECTED] [mailto:dbmail-dev-
>> [EMAIL PROTECTED] On Behalf Of Jorge Bastos
>> Sent: domingo, 16 de Novembro de 2008 22:19
>> To: 'DBMAIL Developers Mailinglist'
>> Subject: RE: [Db
gt; From: [EMAIL PROTECTED] [mailto:dbmail-dev-
> > [EMAIL PROTECTED] On Behalf Of Jorge Bastos
> > Sent: domingo, 16 de Novembro de 2008 21:27
> > To: 'DBMAIL Developers Mailinglist'
> > Subject: RE: [Dbmail-dev] DBMail 2.3.4 released
> >
> > Paul,
>
mingo, 16 de Novembro de 2008 21:27
> To: 'DBMAIL Developers Mailinglist'
> Subject: RE: [Dbmail-dev] DBMail 2.3.4 released
>
> Paul,
> I believe it's fixed this!
> Lmtpd it's ok now, but imapd still dies sometimes, could it be some
> look of
> the d
ngo, 16 de Novembro de 2008 20:49
> To: DBMAIL Developers Mailinglist
> Subject: Re: [Dbmail-dev] DBMail 2.3.4 released
>
> I looked into it. The failure in question may happen during database
> contention (locks). Shouldnt lead to program exit. Please apply below
> patch and try aga
I looked into it. The failure in question may happen during database
contention (locks). Shouldnt lead to program exit. Please apply below
patch and try again.
Paul Stevens wrote:
Some message fails to insert, leading to an exit(113). That shouldn't
happen: insertion failure should be more in
Some message fails to insert, leading to an exit(113). That shouldn't
happen: insertion failure should be more informative, and shouln't lead
to program failure.
I'll fix the first and that should provide enough information to fix the
latter.
--
___
Niente
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Jake Anderson
Sent: sábado, 15 de Novembro de 2008 23:08
To: DBMAIL Developers Mailinglist
Subject: Re: [Dbmail-dev] DBMail 2.3.4 released
Is there anything in the mysql logs when that happens?
Jorge Bastos wrote
15 de Novembro de 2008 8:01
To: DBMAIL Developers Mailinglist
Subject: Re: [Dbmail-dev] DBMail 2.3.4 released
Jorge Bastos wrote:
Paul, the link below for the changelog show's nothing.
fixed.
This has the lmtpd+imapd issue that I posted to
Jorge Bastos wrote:
Paul, the link below for the changelog show's nothing.
fixed.
This has the lmtpd+imapd issue that I posted to you fixed?
NO. I can't reproduce them. And I did try. A lot.
--
Paul Stevens
de 2008 23:10
To: 'DBMAIL Developers Mailinglist'
Subject: RE: [Dbmail-dev] DBMail 2.3.4 released
Paul, the link below for the changelog show's nothing.
This has the lmtpd+imapd issue that I posted to you fixed?
-Original Message-
From: [EMAIL PROTECTED] [mailto:dbmail-
On Fri, 2008-11-14 at 21:17 +0100, Paul J Stevens wrote:
> > Do you consider the database schema pretty much set in stone?
>
> Pretty much, sure. No plans to change them on this end.
There was the mention of the cplogs patch recently, with schema changes
(if it gets updated for 2.3). Might ju
IL Developers Mailinglist'
> Subject: RE: [Dbmail-dev] DBMail 2.3.4 released
>
> Paul, the link below for the changelog show's nothing.
> This has the lmtpd+imapd issue that I posted to you fixed?
>
>
>
> > -Original Message-
> > From: [EMAIL PROT
>
> Yes, but starting with Glib 2.14:
> http://library.gnome.org/devel/glib/stable/ix09.html
>
> Aaron
>
Thanks. INSTALL file needs to be updated with this as it indicates 2.8.
>
> On Fri, Nov 14, 2008, Larry Low <[EMAIL PROTECTED]> said:
>
> > Is 'g_string_append_vprintf' supposed to be in Glib
Paul, the link below for the changelog show's nothing.
This has the lmtpd+imapd issue that I posted to you fixed?
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:dbmail-dev-
> [EMAIL PROTECTED] On Behalf Of Paul J Stevens
> Sent: sexta-feira, 14 de Novembro de 2008 13:48
> To: DBM
Yes, but starting with Glib 2.14:
http://library.gnome.org/devel/glib/stable/ix09.html
Aaron
On Fri, Nov 14, 2008, Larry Low <[EMAIL PROTECTED]> said:
> Is 'g_string_append_vprintf' supposed to be in Glib2? Using 2.12 but it does
> not seem to be in there on CentOS 5.
>
> Oddly I was also ha
Is 'g_string_append_vprintf' supposed to be in Glib2? Using 2.12 but it does
not seem to be in there on CentOS 5.
Oddly I was also having problems with libzdb as the PostgreSQL check of
PQprepare was segfaulting. I just bypassed the check so that I could get it
compiled. Need to look into it
Larry Low wrote:
> Do you consider the database schema pretty much set in stone?
Pretty much, sure. No plans to change them on this end.
> I'm considering beginning testing in my lab and looking forward to testing if
> the expunging has been improved.
O yeah! The imap code has been extensivel
Do you consider the database schema pretty much set in stone? I'm considering
beginning testing in my lab and looking forward to testing if the expunging has
been improved.
>
> Hi all,
>
> It is with great pleasure that I'm announcing the availability of
> DBMail
> version 2.3.4, the latest in
Aleksander Kamenik wrote:
> Have you discarded the idea of including the cplogs patch in dbmail or
> is it not included only because of the missing postgresql schema?
Not at all. As far as I know the cplogs patch is against 2.2. If you
have a patch that applies to the main git branch, please send
Paul J Stevens wrote:
The main focus of this release has been stability. I hope and expect
this version to mark the final milestone before 2.4.0.
Hi,
Have you discarded the idea of including the cplogs patch in dbmail or
is it not included only because of the missing postgresql schema?
Reg
26 matches
Mail list logo
