I think I'm beginning to see the problem now. My dbmail_messageblks table has the messageblk column as type TEXT not bytea.
How should I go about converting that? I thought that was part of the conversion from 2.0 to 2.2. -- David A. Niblett | email: [EMAIL PROTECTED] Network Administrator | Phone: (352) 334-3400 Gainesville Regional Utilities | Web: http://www.gru.net/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Niblett, David A Sent: Thursday, November 09, 2006 4:41 PM To: DBMail mailinglist Subject: RE: [Dbmail] DBMail 2.20rc1 and SquirrelMail Here are the database settings: dbmail=# \set VERSION = 'PostgreSQL 8.1.5 on i686-pc-linux-gnu, compiled by GCC i686-pc-linux-gnu-gcc (GCC) 4.1.1 (Gentoo 4.1.1)' AUTOCOMMIT = 'on' VERBOSITY = 'default' PROMPT1 = '%/%R%# ' PROMPT2 = '%/%R%# ' PROMPT3 = '>> ' DBNAME = 'dbmail' USER = 'niblettda' PORT = '5432' ENCODING = 'SQL_ASCII' HISTSIZE = '500' -- David A. Niblett | email: [EMAIL PROTECTED] Network Administrator | Phone: (352) 334-3400 Gainesville Regional Utilities | Web: http://www.gru.net/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul J Stevens Sent: Thursday, November 09, 2006 4:35 PM To: DBMail mailinglist Subject: Re: [Dbmail] DBMail 2.20rc1 and SquirrelMail David, What encoding is set on the dbmail database? Niblett, David A wrote: > I took the plunge and converted my personal server to 2.2.0rc1 to > start testing. I have an interesting error, and I'm hoping that it's > something very simple. > > I followed the conversion process from 2.0 to 2.2 and all my existing > messages are great. The problem seems to be when I get new mail and > try to view it in SquirrelMail (all I use at home). > > Any new message, I get the error: > > Body retrieval error. The reason for this is most probably that the > message is malformed. > Command: FETCH 125624 BODY[1] > Response: OK > Message: UID FETCH completed > FETCH line: * 2 FETCH (UID 125624 BODY[1] NIL) > > > The message isn't malformed (or at least it wasn't when it was > sent) and it's all new mail since the upgrade. I noticed that the > messages seem to all be something like: > > Received: from localhost (unknown [127.0.0.1])\011by asok.niblett.org > (Postfix)\012\011with ESMTP id 056D52EA4D\011for > <[EMAIL PROTECTED]>;\012\011Thu, 9 Nov 2006 18:02:30 +0000 > > For some reason there are a bunch of \011 codes in the message. In > checking the dbmail_messageblks for that message it's all jumbled in > with the \011. > > I'm running DBMail 2.2.0rc1 > Postfix delivery via dbmail-lmtpd > Postgresql 8.1.5 > > I don't think this is a problem with dbmail-imapd, maybe an issue with > dbmail-lmtpd, but also could be an issue with postgesql. > > Any thoughts? > > -- > David A. Niblett | email: [EMAIL PROTECTED] > Network Administrator | Phone: (352) 334-3400 > Gainesville Regional Utilities | Web: http://www.gru.net/ > > _______________________________________________ > DBmail mailing list > DBmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail > -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list DBmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail _______________________________________________ DBmail mailing list DBmail@dbmail.org https://mailman.fastxs.nl/mailman/listinfo/dbmail
