[Dbmail-dev] Fwd: debug/trace

2005-11-10 Thread K C
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. However, the

[Dbmail-dev] mail content-type and database encoding

2005-11-10 Thread K C
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

Re: [Dbmail-dev] mail content-type and database encoding

2005-11-10 Thread Robert Fleming
K C wrote: 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

Re: [Dbmail-dev] mail content-type and database encoding

2005-11-10 Thread Aaron Stone
On Thu, 2005-11-10 at 13:26 -0800, Robert Fleming wrote: This has been discussed a couple times before. I've tried to summarize it here: http://www.dbmail.org/dokuwiki/doku.php?id=unicode_postgresql_database Bug 218 had to do with problems with Unicode encoding prior to PostgreSQL 8.1.

Re: [Dbmail-dev] mail content-type and database encoding

2005-11-10 Thread K 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: That makes sense. In 2.0.7 I

Re: [Dbmail-dev] mail content-type and database encoding

2005-11-10 Thread K C
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 client side). Kevin On 11/10/05,

[Dbmail] update wiki for full postfix 2.2 + dbmail integration

2005-11-10 Thread [EMAIL PROTECTED]
For those looking for detailed and complete install instruction of Postfix 2.2 + dbmail + mysql + sasl2 (smtp authentcation), I have rewritten the previous wiki article with full doc on the integration procedure. Major changes to article: 1) SASL2 how to: Cyrus SASL2 mysql compile is a pain

[Dbmail] debug/trace

2005-11-10 Thread K C
I tried move a message from one mailbox(non-dbmail) into dbmail box, and that one result sql error. However, the sql statement was truncated in /var/log/maillog that I can't investigate the cause(or potential a bug). Nov 9 17:36:46 dhcp-6op7-6op8-6op9-east-130-35-57-132 dbmail/imap4d[4177]:

Re: [Dbmail] debug/trace

2005-11-10 Thread Leonel Nunez
K C wrote: I tried move a message from one mailbox(non-dbmail) into dbmail box, and that one result sql error. However, the sql statement was truncated in /var/log/maillog that I can't investigate the cause(or potential a bug). Nov 9 17:36:46 dhcp-6op7-6op8-6op9-east-130-35-57-132

[Dbmail] The table 'dbmail_messageblks' is full error message (yelp!!!)

2005-11-10 Thread Simon
Hi There, Running dbmail Version: 2.0.7+20050927-1 on debian sarge with mysql 4.1 and getting this error all of a sudden, (trace 5 turned on now): Nov 10 16:31:17 mx1 dbmail/smtp[23103]: dbmysql.c,db_query: mysql_real_query failed: The table 'dbmail_messageblks' is full Nov 10 16:31:17 mx1

[Dbmail] mysql_real_query failed: Can't open file: 'dbmail_messageblks.MYI' (errno: 144)

2005-11-10 Thread Simon
Now im getting these errors: Nov 10 16:55:52 mx1 dbmail/smtp[2721]: main(): exit code is [75]. Nov 10 16:55:52 mx1 dbmail/smtp[2722]: dbmysql.c,db_query: mysql_real_query failed: Can't open file: 'dbmail_messageblks.MYI' (errno: 144) Nov 10 16:55:52 mx1 postfix/pipe[2719]: A91C82620177: to=

Re: [Dbmail] mysql_real_query failed: Can't open file: 'dbmail_messageblks.MYI' (errno: 144)

2005-11-10 Thread [EMAIL PROTECTED]
1) Disk full. 2) More likely. You have reached the max row count limit of the table. This is a well known problem that can be easily fixed by rebuldind the mysql table with ALTER and changing the avg row size I believe. Do a show tables in phpmyadmin and you see if you have reached this

Re: [Dbmail] mysql_real_query failed: Can't open file: 'dbmail_messageblks.MYI' (errno: 144)

2005-11-10 Thread Simon
I had a f*ked dbmail_messageblks.MYI file, so did a repair on that table and things have come right. The dbmail_messageblks.MYD is 3.9GB, checking the number of records in the dbmail_messageblks table, there are 107107. Here is a error report after restarting mysql: warning : Table is marked as

Re: [Dbmail] debug/trace

2005-11-10 Thread K C
Thanks for the tip...it should work for me since I'm just testing it. Kevin On 11/9/05, Leonel Nunez [EMAIL PROTECTED] wrote: K C wrote: I tried move a message from one mailbox(non-dbmail) into dbmail box, and that one result sql error. However, the sql statement was truncated in

[Dbmail] SMTP Service

2005-11-10 Thread [EMAIL PROTECTED]
I've had dbmail installed and running great since 1.2.x. I'm now using 2.0.7on Debian Sarge with exim4 as the MTA. My question is simple. DBmail's install for pop3 and imap are so easy and the configuration to make local domains + mailboxes all virtual (mysql driven) is so complicated are there

Re: [Dbmail] SMTP Service

2005-11-10 Thread Blake Mitchell
This has been discussed at length several times in the past. MTAs are deceptively complicated systems, and there are many good ones already available. It may be worthwhile however, to package up an existing MTA such as Sendmail or Postfix so that it installs pre-configured to work with dbmail.