Am 25.09.2013 23:25, schrieb Jorge Bastos: >>> Does everyone agree with me? >> >> yes >> >> 3.1.6 AFAIK was also a real fine release >> >> the most important commit from 3.1.7 is >> "POP3: audit message retrieval and align with imap code" >> >> pop3 broke multimime-messages with parts like below at least on Fedora >> 18 while F19 was fine with same dbmail/libzdb/gmime >> >> Content-Type: multipart/mixed; boundary=Barracuda.8651408061166 >> Content-Type: multipart/related; boundary="Barracuda.8651738179060" >> Content-Type: multipart/alternative; >> boundary="Barracuda.86511333652098" >> >> only god knows what "multipart/related" *and* "multipart/mixed" in a >> message with 6 lines text wrapped in plaintext/html, both base64 >> encoded and blown up to 53 KB is good for :-) > > But are you saying this problem still exists in 3.1.7 ? > In my case, I do not rely on OS versions of gmime/zdb/whatver, so my > question is, if this still is a problem in 3.1.7, which gmime version are > you (the OS) using?
no, it's fixed, that's why i said "most important commit" http://git.dbmail.eu/paul/dbmail/commit/?h=dbmail_3_1&id=1eeb3ff20cb89b37dfba6b00d5efc44223be121a my environment is for testing Fedora 19 and in production Fedora 18 and i am mainting the 3 main-dependency-pakcages at my own normally it should not matter, gmime-2.6.12 on Fedora 18 at least broke dbmail-3.0.2 horrible, older and newer seems to be fine [harry@srv-rhsoft:~]$ rpm -q libzdb gmime libevent dbmail libzdb-2.12-2.fc19.20130919.rh.x86_64 gmime-2.6.18-2.fc19.20130919.rh.x86_64 libevent-2.0.21-4.fc19.20130923.rh.x86_64 dbmail-3.1.7-1.fc19.20130924.rh.3.1.7.x86_64
signature.asc
Description: OpenPGP digital signature
_______________________________________________ DBmail mailing list DBmail@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
