A NOTE has been added to this issue. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=854 
====================================================================== 
Reported By:                simonlange
Assigned To:                
====================================================================== 
Project:                    DBMail
Issue ID:                   854
Category:                   Command-Line programs (dbmail-users, dbmail-util)
Reproducibility:            unable to reproduce
Severity:                   trivial
Priority:                   normal
Status:                     acknowledged
target:                      
====================================================================== 
Date Submitted:             20-Aug-10 13:03 CEST
Last Modified:              20-Aug-10 20:45 CEST
====================================================================== 
Summary:                    DBMAIL-UTIL DOES NOT FIX NULL MESSAGES
Description: 
Although already 2005 reported
http://www.mail-archive.com/dbm...@dbmail.org/msg06073.html

This bug is still there in dbmail 2.2.16

Usually dbmail-util should fix them but instead it just sets status to 6
of each message. Status 6 is not recognized by any cleanup processes of
dbmail. Thats why null messages do stay in the database.

a manual sql statemente (delete) removes them and fixes the error.

this whole issues was discussed already in 2005 (5 years ago!)

wonder noone else stumbled over it the past 5 years.

Wharever, thats why i write this bug report.
====================================================================== 

---------------------------------------------------------------------- 
 (0003088) paul (administrator) - 20-Aug-10 14:26
 http://www.dbmail.org/mantis/view.php?id=854#c3088 
---------------------------------------------------------------------- 
Simon,

Took you long enough to file the bug then :-)

It seems to me that these null message are an indication of a problem that
arises elsewhere. I for one never see them, and they should not appear
under normal circumstances. 

There may be a problem with your schema, or you maybe using non-dbmail
tools to talk to and write into the dbmail database. 

---------------------------------------------------------------------- 
 (0003089) simonlange (reporter) - 20-Aug-10 17:05
 http://www.dbmail.org/mantis/view.php?id=854#c3089 
---------------------------------------------------------------------- 
Paul,

Its not MY schema. Its DBMAIL's schema. ;)
Im using only dbmail-tools.
its a fresh installation.
database' health is fine.

and the question is how it gets status6 if the util should remove nulls.
and why the heck the util does not remove them anyway? says repaired but
in fact it did nothing to remove them.

so? its def a bug.

my workaround i posted 5years ago still works. but its not the best way.
better the util handles this, not a manual sql-statement. ;)

regards 

---------------------------------------------------------------------- 
 (0003090) simonlange (reporter) - 20-Aug-10 17:26
 http://www.dbmail.org/mantis/view.php?id=854#c3090 
---------------------------------------------------------------------- 
"unable to reproduce"
try harder! ;)
 all u need to know stands there:
(1) NULL messages
(2) Status 6

now check the source or do whatever neccessary to fix that bug.
since it was also in 2.0 branch i bet its a dbmail-util issue.

if u want to know how the null messages were created? although this is not
object of THIS issue, i bet it had something to do with dbmail-imapd. why?
because the amount of null messages i have is EXACTLY the amount of mails i
tried to copy with thunderbird into an imap-directory. (4317 null
messages)

That btw was the same moment as it was several years ago (2005).

i wonder what more u may need to start fixing this.

i dont think its trivial bug as long u dont communicate the workaround.

m2c

Simon 

---------------------------------------------------------------------- 
 (0003091) froeske (reporter) - 20-Aug-10 17:51
 http://www.dbmail.org/mantis/view.php?id=854#c3091 
---------------------------------------------------------------------- 
I also had lots of NULL-Messages when I tried to copy some thousand
messages via IMAP from one server to another via Thunderbird 2, several
years ago.
But I used MyISAM Tables in that set up, I can't remember if I ever had
NULL-Messages with InnoDB.

Kind Regards,
  Frank 

---------------------------------------------------------------------- 
 (0003092) simonlange (reporter) - 20-Aug-10 18:03
 http://www.dbmail.org/mantis/view.php?id=854#c3092 
---------------------------------------------------------------------- 
i cant use innodb since ubuntu does not provide this with 10.04.

whatever, innodb is not a requirement for dbmail. the myisam storage
engine is okay. and since there are no db errors (inconistency or
corrupted/crashed databases) there is no reason for null messages.

innodb has ONLY the advantage that it has a transaction log, allowing nice
things like fast snapshots of the db or repairing within seconds.

but my database is healthy and it has the original dbmail-scheme.

Simon 

---------------------------------------------------------------------- 
 (0003093) paul (administrator) - 20-Aug-10 18:45
 http://www.dbmail.org/mantis/view.php?id=854#c3093 
---------------------------------------------------------------------- 
No innodb on Ubuntu?? What planet are you on?

And no: dbmail doesn't support myisam since 2.2.0!

innodb has the nice advantage of supporting foreign key restrictions which
are in heavy use. 

this bug is marked trivial because it doesn't affect performance,
integrity, or continuity of provided services.

The fact that you use myisam does explain this behaviour. 

---------------------------------------------------------------------- 
 (0003094) simonlange (reporter) - 20-Aug-10 20:45
 http://www.dbmail.org/mantis/view.php?id=854#c3094 
---------------------------------------------------------------------- 
well that happened already on 2.0 branch.
second, yes ubunto rep's mysql 5.1 does not have the innodb storage engine
built in.
Whatever, i have enabled InnoDB via plugins manually. The error persists.

this BUG has nothing to do with foreign keys. and as said it already
showed up with 2.0 branch.

So? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
20-Aug-10 13:03  simonlange     New Issue                                    
20-Aug-10 14:26  paul           Note Added: 0003088                          
20-Aug-10 14:27  paul           Severity                 major => trivial    
20-Aug-10 14:27  paul           Reproducibility          always => unable to
reproduce
20-Aug-10 14:27  paul           Status                   new => acknowledged 
20-Aug-10 17:05  simonlange     Note Added: 0003089                          
20-Aug-10 17:26  simonlange     Note Added: 0003090                          
20-Aug-10 17:51  froeske        Note Added: 0003091                          
20-Aug-10 18:03  simonlange     Note Added: 0003092                          
20-Aug-10 18:45  paul           Note Added: 0003093                          
20-Aug-10 20:45  simonlange     Note Added: 0003094                          
======================================================================

_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev

Reply via email to