28 Nov
2010
28 Nov
'10
2:23 p.m.
Thomas Leuxner <tlx@leuxner.net> wrote:
Narrowing down the issue a bit. With the code that was present on Nov 22, those Newsletter mails worked (needless to say config wasn't changed):
Same here, but I can limit the window some more. 8adacd9c03b2 from Nov 18th was fine and it was busted with 0bc3751c6657 on Nov 23rd. So it seems the problem has been introduced somewhere between f5bec4e94b55 and 0bc3751c6657.
Bernhard