> mysql> select * from dbmail_physmessage where id=3335; > +------+-------------+---------+---------------------+ > | id | messagesize | rfcsize | internal_date | > +------+-------------+---------+---------------------+ > | 3335 | 12 | 2 | 2007-11-07 13:50:41 | > +------+-------------+---------+---------------------+ > 1 row in set (0.00 sec)
No way those are valid messages. I would simply delete them. > How can I workadound this easely? Is this an old known bug? I remember someone having the same problem. Iirc, deleting those broken physmessage entries was the solution. Since the internal_date is quite old, and the rfcsize indicates a NULL message I would expect them to be bogus data anyway. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
