Am 21.02.2014 15:06, schrieb Peter Milesson: > On 2014-02-21 13:47, Reindl Harald wrote: >> MySQL 5.1.56 >> >> only a wild guess, maybe there is a in the meantime fixed bug >> in MySQL just triggered with DBMail 3.1.10 and not 3.0.2? >> >> my guess is because very few people these days running 5.1 >> >> this one as example states that MariaDB before 5.5.33a is broken >> with DBMail 3.1, a complete different story but a good example >> how a bug in one of the components may hit DBMail >> https://mariadb.atlassian.net/browse/MDEV-4978 > > Hi Harald, > > The database backend is MariaDB 5.5.34
ok, than it is not the database, MariaDB 5.5.34 works fine with DBmail otherwise i would have noticed this the hard way after the migration yum.log of our main DBMail machine: Jan 07 20:07:08 Updated: 1:mariadb-server-5.5.34-4.fc19.20140107.rh.x86_64 Jan 30 18:44:35 Updated: 1:mariadb-server-5.5.35-2.fc19.20140129.rh.x86_64 ________________________________________ i am unsure if that was changed, but Paul statet as i assumed that you took the dbmail-master and not the 3.1 stable snapshot we are currently on dbmail-3.1.10-3.fc19.20140219.rh.58386719c660a493cb56d1607c1e7ec9eaa4a1b2.x86_64 http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1&id=58386719c660a493cb56d1607c1e7ec9eaa4a1b2 http://git.dbmail.eu/paul/dbmail/log/?h=dbmail_3_1 not sure how easy a downgrade in case of the 3.2/master scheme changes goes at all
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list [email protected] http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
