On 2014-12-20 22:20, Paul J Stevens wrote:
Ok.
Good news: dbmail-3.1 is not affected. Apparently the problem only
occurs in 3.2.0 and 3.2.1. It's definitely a regression.
Bad news: if you use 3.2, you should apply the patch I pushed
yesterday.
The workaround offers no real protection, as Caspar correctly surmised.
Hi.
good that my server isn'T busy I only just noticed this now.
@Paul: any chance for a new version soon that I can package up?
also it might be good to create a CVE:
http://www.cvedetails.com/product/3284/Dbmail-Dbmail.html?vendor_id=1941
Regards
_______________________________________________
DBmail mailing list
DBmail@dbmail.org
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
