Hi, I posted a problem about the curmail_size a while ago. I got this patch to fix it. Now I noticed this in my logs:
Mar 26 09:40:15 vs1139181 dbmail/imap4d[11723]: Error:[sql] dbmysql.c,db_query(+290): [You have an error in your SQL syntax; check the man ual that corresponds to your MySQL server version for the right syntax to use near 'THEN curmail_size - 103071 ELSE 0 END WHERE user_idnr = 15' at line 1] [UPDATE dbmail_users SET curmail_size = CASE curmail_size >= 103071 THEN curmail_size - 103071 ELSE 0 END WHERE user_idnr = 15] Mar 26 09:40:15 vs1139181 dbmail/imap4d[11723]: Error:[db] db.c,db_expunge(+4008): error decreasing used quotum for user [15]. Database mi ght be inconsistent now I double checked but the SQL is the same as provided in the patch. My current version of dbmail is 2.2.10. I also hate this message: Mar 26 09:22:57 vs1139181 dbmail/sievecmd[29774]: Error:[sort] sortsieve.c,sort_startup(+663): Sieve notify is not supported in this relea se. I tried to get rid of it by setting [SIEVE] PORT = 2000 SIEVE_NOTIFY = no but it didn't help. If I would upgrade to 2.3, would those problems be gone? How stable is 2.3? Or is it better to keep fixing this in 2.2 and patch the sources? Thanks in advance Am 16.03.2010 16:49, schrieb Paul J Stevens: > Christian Mötzing wrote: > > >> After running the spam script again curmail_size is back to its >> astronomic value. >> > Sounds like an off-by-one error where the currentsize - removedsize ends > up being less than zero, leading to rollover on the unsigned value. > > Please test the patch below: > > http://git.dbmail.eu/cgit/cgit.cgi/paul/dbmail/patch/?id=d6ceab981b8bbbe4925460d2043f4c03453315a5 > > > > > _______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
