Working now with rev 1918. I also compiled the bin with -g so next time it
can generate more meaningful messages.
Thanks,
Kevin
works now, thanks.
>
> Seriously? I think sticking with glib-2.6 is better, as it's far more
> readily available in distributions. Is there some significantly better
> functionality that you *really* need?
>
+1
I got the same error, but upgrade to glib-2.8 means the whole system upgrade
:-(
Kevin
Sorry for my ignorance ;-)
The IMAP sequence is:
. login
. SELECT "INBOX"
. UID FETCH 1319:* (BODY.PEEK[HEADER.FIELDS (References X-Ref X-Priority
X-MSMail-Priority X-MSOESRec Newsgroups)] ENVELOPE RFC822.SIZE UID FLAGS
INTERNALDATE)
Command to generate trace:
# cat debug.imap | valgr
I got following error prompt on the console when Outlook Express tried to
retrieve emails:
(process:8443): GLib-CRITICAL **: file gstrfuncs.c: line 2152 (g_strsplit):
assertion `string != NULL' failed
Then I run valgrind got following:
[/var/log]# cat maillog.debug | valgrind --tool=memcheck -v
Just FYI, I'm using pgsql 8.1.0.
Kevin
On 11/10/05, K C <[EMAIL PROTECTED]> wrote:
>
> Thanks, I should have searched the bug db first.
>
> env PGCLIENTENCODING=LATIN1 dbmail-imapd
>
> works for me now (I need to check what I should do to deal with encoding
> at c
Thanks, I should have searched the bug db first.
env PGCLIENTENCODING=LATIN1 dbmail-imapd
works for me now (I need to check what I should do to deal with encoding at
client side).
Kevin
On 11/10/05, Robert Fleming <[EMAIL PROTECTED]> wrote:
>
> K C wrote:
>
> >
> > T
That makes sense.
In 2.0.7 I inserted a check that causes DBMail to bomb out on startup
> with a warning that the database must be US-ASCII. In 2.1.x I'd like to
> do something more clever, like change the encoding at connection time.
That said, are you suggesting that we have to build the datab
My pgsql database was set to use UTF8.
dbmail: 2.1.3
When tried to move a message in Outlook Express from one mailbox(non-dbmail)
into dbmail, through dbmail-IMAP, I got database error when it tries to
insert the body into dbmail_messageblks:
ERROR: invalid UTF-8 byte sequence detected near byte
Should be sent to dev list, anybody can help?
-- Forwarded message --
From: K C <[EMAIL PROTECTED]>
Date: Nov 9, 2005 5:39 PM
Subject: debug/trace
To: dbmail@dbmail.org
I tried move a message from one mailbox(non-dbmail) into dbmail box, and
that one result sql error. H
n table tt instead.
Besides, if you drop primary key index, you lose the ability to search on
id.
Kevin
On 11/7/05, Geo Carncross <[EMAIL PROTECTED]> wrote:
>
> On Sun, 2005-11-06 at 14:28 -0800, K C wrote:
> > I've replaced this kind of unique indexes with just normal
I've replaced this kind of unique indexes with just normal (physmessage_id)
if there is no other index can index physmessage_id. This is to make sure
physmessage_id can use index. But unique index on (physmessage_id, id) is
unnecessary here.
Kevin
On 11/6/05, Aaron Stone <[EMAIL PROTECTED]> wrote
13 matches
Mail list logo
