http://blog.gmane.org/gmane.mail.imap.dbmail hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://comments.gmane.org/gmane.mail.imap.dbmail/14239 <pre>Hi i am fine with this but http://koji.fedoraproject.org/koji/packageinfo?packageID=325 Fedora 17 (released in two weeks is the first one with 2.6) i do not like to upgrade to F17 until it is hardly needed because currently are too much php-pecl extensions still not supporting PHP 5.4 (the most important suhosin) please do not require gmime 2.6 too soon because Fedora is bleeding edge and other distributions are behind _______________________________________________ DBmail mailing list DBmail&lt; at &gt;dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail </pre> Reindl Harald 2012-05-23T16:22:03 http://comments.gmane.org/gmane.mail.imap.dbmail/14237 <pre>I am using dbmail 3.0 and while sieve scripts work fine, I can't use the vacation script. I tried a very simple one like: require ["vacation"]; if header :matches "subject" "*" { vacation :subject "Automatic response" "I'm away -- send mail to foo in my absence"; } But it doesn't work. I get the following error in the debug log: May 22 17:24:37 dbmail32 dbmail-lmtpd[4512]: [0x9bc3fb8] Debug:[sort] sort_debugtrace(+625): sieve: [sv_interface,script.c,libsieve_eval: [VACATION aborted: no match found in script.] Any idea? Can you provide me your sieve script for example? Leandro </pre> Leandro 2012-05-22T15:56:04 http://comments.gmane.org/gmane.mail.imap.dbmail/14233 <pre>I’m attempting a migration of a Dbmail 2.2.17 installation to 3.0.2 with a backup of our production database on a spare machine to test the procedure. Our dbmail installation contains some 900k messages and is some 360gig (data; index 1.9gig). The primary reason for wishing to migrate is for the single instance storage of mime-parts to hopefully reduce the storage space significantly (when I tried the same migration last year with the RC there was a reduction by some 60%). I am at the stage of running dbmail-util –My to convert the message attachments to the new storage system and am hitting a brick wall in the sense that dbmail-util is repeatedly coredumping. If I run the dbmail-util command immediately again I receive foreign key errors: May 22 10:34:35 dbm3 dbmail-util[6041]: [0x80240b040] Error:[db] db_exec(+319): SQLException: Cannot add or update a child row: a foreign key constraint fails (`dbmail`.`dbmail_partlists`, CONSTRAINT `dbmail_partlists_ibfk_1` FOREIGN KEY (`physmessage_id`) RE</pre> Daniel Schütze 2012-05-22T09:51:15 http://comments.gmane.org/gmane.mail.imap.dbmail/14232 <pre>Hi, Has anybody done any performance and storage tests for innodb with regard to dbmail 3.0. Like using compression and partitioning on the email data tables? https://dev.mysql.com/doc/refman/5.5/en/innodb-compression.html https://dev.mysql.com/doc/refman/5.5/en/partitioning.html Also, any recommendations on setting the various innodb buffer sizes, that deviate from the standard recommendations? Maybe someone can simply share their experiences with tweaking innodb on a dbmail install. Regards, Aleksander Kamenik </pre> Kamenik, Aleksander 2012-05-18T13:22:23 http://comments.gmane.org/gmane.mail.imap.dbmail/14229 <pre>Hello, am I wrong or there is no dbmail-util procedure to delete headervalues no more connected to messages? After deleting some users directly from the dbmail_database and running the dbmail-util -ay housekeeping utility, I noticed the dbmail_headervalue table size remains pretty the same. If I run manually the query: select count(*) from dbmail_headervalue where id not in ( select headervalue_id from dbmail_header ); I discovered a large number of no more connected header values. Almost the same if I check the headernames with the query: select count(*) from dbmail_headername where id not in ( select headername_id from dbmail_header ); Leandro </pre> leandro 2012-05-15T15:08:29 http://comments.gmane.org/gmane.mail.imap.dbmail/14228 <pre>hi http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_0&amp;id=9e2f272541621d898d9485bfbf43818d7dce708c in 2da7411789e03a9b51f2e286ea1ea6cc4f3e4303 this seems to be broken again as long i reset user-preferences and do not touch sort all is fine but from the moment you are sorting for anything it gets broken _______________________________________________ DBmail mailing list DBmail&lt; at &gt;dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail </pre> Reindl Harald 2012-05-14T09:45:42 http://comments.gmane.org/gmane.mail.imap.dbmail/14223 <pre>Hello, I'm trying to clear the inbox for an user. To do it i execute: #dbmail-export -u TheUserId -m INBOX -d -o /tmp/in.mbox #dbmail-util -dpy /tmp/in.mbox is created but the inbox is not cleared. ¿What is the correct way? I'm using dbmail 2.2.11 with PostgreSQL Thanks </pre> Oswaldo 2012-05-09T07:44:23 http://comments.gmane.org/gmane.mail.imap.dbmail/14220 <pre> Hello &lt; at &gt;all, i started to develop a simple web-GUI to administrate DBMail, like the commandline tool. The DBMailAdmin (http://www.dbmailadmin.org) was to much for me. The GUI opensource and written in PHP, you can find it at: https://code.google.com/p/simple-dbmail-admin/ I hope someone will give it a try and a feedback. (Or much better join the development!) Best regards Claas </pre> cl445 2012-05-07T15:47:54 http://comments.gmane.org/gmane.mail.imap.dbmail/14211 <pre> Has anybody an idea, to get SASL to work with encrypted passwords in the database? I used Cyrus SASL and it seems to be impossible. </pre> cl445 2012-05-03T14:22:50 http://comments.gmane.org/gmane.mail.imap.dbmail/14210 <pre> Hello everybody, I'm started to develop a very simple Admintool in php for my own. But all the documentation is still for DBMail 2.2 and older. Is it possible to update the documentation, especialy the ER-Model? Best, Claas </pre> cl445 2012-05-03T14:19:57 http://comments.gmane.org/gmane.mail.imap.dbmail/14208 <pre>Dear all, New version of the unofficial DBMail admin panel, DBMailAdmin-MySQL-1.1.0, has been released. You can download it here: http://dbmailadmin.org/download.html Detailed ChangeLog * Improvements: + Show search string in search result page. + Able to execute addition SQL commands after creating user. * Fixed: + Incorrect SQL table name used for deleting admin accounts. + Missing some msg handlers in account list pages. Thanks Jure Pečar &lt;jure.pecar _at_ arctur.si&gt; for the report. + Incorrect per-user quota usage calculation. Thanks paparaciz &lt;helpaz&lt; at &gt;gmail&gt; for the report and suggested fix. + Fix possible 'internal server error' caused by incorrect timestamp of dbmail_users.last_login. Thanks Jure Pečar &lt;jure.pecar _at_ arctur.si&gt; for the report. * New and updated translations: + Slovenian (sl_SI). Thanks Marko Kobal &lt;marko.kobal _at_ arctur.si&gt;. + Polish (pl_PL). Thanks Adrian (adi _at_ zwami.pl) How to upgrade from old releases 1) Download version 1.1.0 and uncompres</pre> Zhang Huangbin 2012-04-23T12:04:48 http://comments.gmane.org/gmane.mail.imap.dbmail/14205 <pre> I'm running dbmail 3.0.2 with: Postgresql: 9.1.2 DBmail: 3.0.2 Fedora Linux: 3.3.2-1.fc16.x86_64 Postfix: DBMA: v2.5.4 I have everything up and running as far as dbmail is concerned, but could anyone recommend a good admin tool for dbmail 3. Some functions in DBMA don't seem to be working and the DBMA project seems to be looking for a new team leader. Regards, LelandJ </pre> lelandj 2012-04-22T18:22:10 http://comments.gmane.org/gmane.mail.imap.dbmail/14190 <pre>Hello, I work on a product that uses dbmail. Our new version is running dbmail 3.0 and everything is fine. But I have a customer running an old version with dbmail 2.2.26, and they reported a bug that I need to produce a patch for. The symptom is: a user sends an email where the following number gets split into two lines as: 3 ..375% Dbmail changes this into 3 ..75% I am comparing the code and bug fixes regarding 'dot' on the two dbmail versions, but cannot find where the problem is in 2.2.26. I noticed that a lot changed between the two source trees. I read about some dot-stuffing changes in various places, but can't find what I need to fix. I am hoping to be able to patch the C code in 2.2.26 and produce a patch for this customer. Enclosed is an output of mysql queries comparing the text stored in dbmail between 2.2.26 and 3.0-rc3. FYI: the 2.2.26 runs on Fedora 8 and my current 3.0-rc3 runs on CentOS 6.2. Thank you, Dirce _______________________________________________ DBmail mailing list DBmail</pre> drsystems< at >globalcerts.net 2012-04-19T15:42:27 http://comments.gmane.org/gmane.mail.imap.dbmail/14189 <pre> Hello, After dbmail upgrade from 2.2.17 to 3.0.2 fileinto :flags "\\Seen" "Junk"; stopped working. I upgraded db schema with /usr/share/dbmail/mysql/2_2-3_0.mysql then run dbmail-util -ay and see no other errors. libsieve is 2.2.7 Does anybody have the same problem or I did something wrong? </pre> Sergej Pupykin 2012-04-18T09:30:52 http://comments.gmane.org/gmane.mail.imap.dbmail/14186 <pre>Hello I am following Reindl Harald dbmail3-migration procedures. Upstream version dbmail v2.2.17 with mysql 5.5.21. Target server is dbmail v3.0.2 with mysql 5.5.21 and Reindl's proposed config setup files in dbmail3-migration.zip package (dbmail.conf, my.cnf). Used scenario was: 1) mysqldump dbmail from v2.2.17 2) create fresh new dbmail v3 database 3) import mysqldump.sql 3) run sql-convert-2_2-3_0.sql After waiting several hours dodropkeys() procedure to be done, I got the following error: .... -------------- DROP TABLE IF EXISTS `dbmail_envelope` -------------- -------------- CREATE TABLE `dbmail_envelope` ( `physmessage_id` BIGINT(20) UNSIGNED NOT NULL DEFAULT '0', `id` BIGINT(20) UNSIGNED NOT NULL AUTO_INCREMENT, `envelope` TEXT NOT NULL, PRIMARY KEY (`id`), UNIQUE KEY `physmessage_id_1` (`physmessage_id`), UNIQUE KEY `physmessage_id_2` (`physmessage_id`,`id`), CONSTRAINT `dbmail_envelope_ibfk_1` FOREIGN KEY (`physmessage_id`) REFERENCES `dbmail_physmessage` (`id`) ON DELETE C</pre> Pascal Longrais 2012-04-17T08:30:43 http://comments.gmane.org/gmane.mail.imap.dbmail/14183 <pre>My dbmail-imapd daemon died, because it tried to store a message bigger than max_allowed_packet setting in MySQL. I would expect it to rollback that transaction instead of dying, but it probably took some time processing it and hit wait_timeout. If this happens, I think the better behavior would be to try and reconnect to the database, at least a couple of times, before dying. Apr 13 10:30:23 dbmail-lmtpd[17011]: [0x1c39f40] Warning:[clientbase] ci_readln(+415): insane line-length [72453] Apr 13 10:33:31 dbmail-imapd[16948]: [0xc03d10] Error:[message] blob_exists(+170): SQLException: Got a packet bigger than 'max_allowed_packet' bytes Apr 13 10:33:32 dbmail-imapd[16948]: [0xc03d10] Error:[message] blob_insert(+207): SQLException: Lost connection to MySQL server during query SQLException: MySQL server has gone away raised in Connection_rollback at src/db/Connection.c:274 Also, is there a way to set mysql connection flags in dbmail? specifically CLIENT_INTERACTIVE. I can't increase wait_timeout, but i coul</pre> Martin Mačura 2012-04-13T17:36:05 http://comments.gmane.org/gmane.mail.imap.dbmail/14179 <pre>this is becoming a real problem 1958 MB real and 338 GB virtual memory afer &lt; 4 hours Active: active (running) since Thu, 12 Apr 2012 12:06:25 +0200; 3h 28min ago i have no idea what exactly actions of clients can trigger this but i fear we are reaching soon the point where the daily restart at 3:00AM is not enough :-( there are 288 active users and many of them even do only use POP3 _______________________________________________ DBmail mailing list DBmail&lt; at &gt;dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail </pre> Reindl Harald 2012-04-12T13:37:51 http://comments.gmane.org/gmane.mail.imap.dbmail/14164 <pre> Hello all, I see there are some dbmail and roundcube users on this list. I'm deploying dbmail+roundcube+dbmailadmin solution and am in the final stages of testing. There are still some interesting bugs to sort out. For example, if I create a mailbox with artificially small quota (say, 1MB) to easily test near and over quota scenarios, this is what happen: when appending mail to a 99% full mailbox that would put it over quota, roundcube freezes. Looking into what's going on I discovered this in imap protocol dialog: C: A0003 LSUB "" Sent S: * LSUB (\hasnochildren) "/" "Sent" S: A0003 OK LSUB completed C: A0004 LIST "" Sent S: * LIST (\hasnochildren) "/" "Sent" S: A0004 OK LIST completed C: A0005 APPEND Sent (\Seen) {12824} S: + OK C: MIME-Version: 1.0 &lt;content of mail&gt; &lt;no reply from server&gt; So roundcube is right in freezing, since it waits for a reply from imap server that never comes. Looking at this protocol dialog, server is misleading the client when it replies OK to an APPE</pre> Jure Pečar 2012-04-10T15:37:56 http://comments.gmane.org/gmane.mail.imap.dbmail/14161 <pre>Hello, I noticed that when the SMTP daemon is trying to deliver a message to dbmail lmtpd and the mailbox is full, lmtpd answers with a 522 Recipient &lt;*****&gt; Permanent Failure Mailbox Status Mailbox full Unfortunately, using exim (but maybe with other MTA), the message is discarded, immediately. Maybe it can be more correct to have lmtpd answers with just a 422 (Quota Exceeded) because the mailbox full is not a "permanent" condition: if the user delete some message, the message can be delivered. It will be very useful to have exim retry later to deliver the message. Leandro </pre> Leandro 2012-04-10T14:00:33 http://comments.gmane.org/gmane.mail.imap.dbmail/14150 <pre>Hi http://blog.dbmail.eu/archives/12-Pruning-the-dbmail_headervalue-table.html this is nice and as noticed needs the follwong query to get the values away (laso from deleted messages -&gt; dbmail-util missing it) delete from dbmail_headervalue where id not in (select headervalue_id from dbmail_header); this query alone removed 700000 rows from around 2 Mio after the first call and since then in is pruning around 30.000 records each day (removed messages) _____________________ but since this tables are "only" used for search and message-list and there are only a few geadernames relevant would it be not better have here a sane built-in which headernames to cache which can be overriden in "dbmail.conf"? in my opinion this makes more sense as killing explicitly named ones manually from time to time many people out there are really "creative" by adding mail-headers see the list below and this is after removing the 200 dumbest jokes 2058 rows in set (0.01 sec) _____________________________ mysql&gt; select heade</pre> Reindl Harald 2012-04-09T20:28:52 http://comments.gmane.org/gmane.mail.imap.dbmail/14130 <pre>on our roundcube sort by date is still broken completly see screenshot - thunderbird is not affected IMAP feels more and more like a gambling machine by notice each client with a different behavior for the same basic-tasks :-( ______________________ roundcubemail-0.7.2-3.fc16.20120326.rh.noarch the setps below were done last weekend database: SET FOREIGN_KEY_CHECKS=0; TRUNCATE `dbmail_header`; TRUNCATE `dbmail_headername`; TRUNCATE `dbmail_headervalue`; SET FOREIGN_KEY_CHECKS=1; terminal: dbmail-util -by _______________________________________________ DBmail mailing list DBmail&lt; at &gt;dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail </pre> Reindl Harald 2012-04-04T11:06:38 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.mail.imap.dbmail