OK, sounds good, I will go ahead and remove those messages. I am not looking to support this 1.2 install any longer than I have to, hence the migration work. :-)
Thanks much Paul. Bret. On Saturday 08 March 2008 3:52:09 am Paul J Stevens wrote: > Remove all messages and physmessages with size=0 > > Those empty message are very likely a side effect of some bug in 1.2's > insertion code. We've come a very long way since then. > > Noone is interested in supporting dbmail 1.2 anymore unless someone at > IC&S has some compelling business case with one of their customers > running 1.2. > > Bret Baptist wrote: > > Any ideas on this at all? > > > > > > Thanks, > > > > Bret. > > > > On Tuesday 26 February 2008 6:07:22 pm Bret Baptist wrote: > >> On Saturday 16 February 2008 2:09:13 am Paul J Stevens wrote: > >>> Bret Baptist wrote: > >>>> On Friday 15 February 2008 2:47:57 am Paul J Stevens wrote: > >>>>> Bret Baptist wrote: > >>>> > >>>> What does this message mean? Is there anything that > >>>> I can check related to this message to see if there are any issues > >>>> with the migration? > >>> > >>> It's probably not the migration then, but rather an inconsistency in > >>> the database. I can't tell for sure without level5 logs. > >> > >> Here are the level5 logs from a run: > >> Feb 26 17:01:34 bedlam dbmail/maintenance[25449]: Debug:[sql] > >> dbmysql.c,db_query(+287): query [SELECT messageblk, is_header FROM > >> dbmail_messageblks WHERE physmessage_id = 19037459 ORDER BY > >> messageblk_idnr] Feb 26 17:01:34 bedlam dbmail/maintenance[25449]: > >> Debug:[db] > >> dbmodule.c,db_query(+145): last query took [0] seconds > >> Feb 26 17:01:34 bedlam dbmail/maintenance[25449]: Error:[message] > >> dbmail-message.c,_retrieve(+696): blk error > >> Feb 26 17:01:34 bedlam dbmail/maintenance[25449]: Error:[message] > >> dbmail-message.c,dbmail_message_retrieve(+769): retrieval failed for > >> physid [19037459] > >> Feb 26 17:01:34 bedlam dbmail/maintenance[25449]: Warning:[db] > >> db.c,db_update_rfcsize(+1849): error retrieving physmessage: [19037459] > >> > >>> Did you test with outlook/tb etc? Does everything look ok from that > >>> perspective? > >> > >> I did a test and was able to connect and retrieve messages from the > >> server. > >> > >> I did a check in the database and noticed that all the messages throwing > >> this error had a messagesize of 0 in the dbmail_physmessage table. Do > >> you know of a bug in dbmail 1.2.12 that would cause it to create a > >> message with no messageblks associated with it? > >> > >> I checked my live dbmail 1.2.12 database and the same message also had a > >> message size of 0 and no messageblks. These are recently received > >> messages too. > >> > >> After I deleted all the messages from dbmail_messages that had a > >> dbmail_physmessage messagesize of 0, and all the physmessages from > >> dbmail_physmessage that had a messagesize of 0, I was able to run the > >> dbmail-util -by without errors. > >> > >> > >> Thanks for your help. -- Bret Baptist Senior Network Administrator [EMAIL PROTECTED] Internet Exposure, Inc. http://www.iexposure.com (612)676-1946 x17 Providing Internet Services since 1995 Web Development ~ Search Engine Marketing ~ Web Analytics Network Security ~ On Demand Tech Support ~ E-Mail Marketing ------------------------------------------ _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
