Oliver Giles

Several crashes have been fixed since that version. Please try out your winmail.dat file on ytnef compiled from the master branch.

With zero-initialized structs, calling `TNEFInitialize` wasn't necessary until that change. Of course it should have been done anyway, that looks like my oversight. Hopefully [this](https://gitlab.gnome.org/GNOME/geary/-/merge_requests/509) should fix it.

> It's a caller-initialised, pass-by reference (as in pass-by-pointer) value, right? Those functions expect it to be initialised by the caller, take a pointer to it as an arg, then...

I haven't used FreeBSD so can't help much sorry. Laminar does use a few features that I believe are Linux-specific, such as [this](https://github.com/ohwgiles/laminar/blob/99e2e629063a10059ee33ed3d68fcdde61dab12e/src/leader.cpp#L320), but I think they should be able...

1. Since Laminar run scripts are just regular shell scripts (or anything executable), they can easily be tested on their own before having laminar execute them. 2. Laminar is totally...

Ok makes sense, the latest build numbers are cached in laminar itself, it would need to be restarted after the database is cleaned. Anyway for me this is not a...

The chunked transfer is also great for watching logs with curl, which obviously doesn't have the multiple connection issue. You probably want to run laminar behind a reverse proxy anyway;...

Maybe [this comment](https://github.com/ohwgiles/laminar/issues/115#issuecomment-595738559) would be helpful. Laminar could definitely use some documentation on how to configure a reverse proxy...

Just `curl $LAMINAR_HTTP/log/$JOB/$RUN`. Log output should be delivered to your console as it is produced, as long as your reverse proxy doesn't interfere.

Is this issue still relevant?