Calascibetta Romain

Ok, I think the door is open and, as I said we should take the opportunity as soon as we can (before to handle _legacy_ stuffs), so I will propose...

> What do you mean by legacy here? Ah it's a theory about [the software entropy](https://en.wikipedia.org/wiki/Software_entropy) (or the [Zawinski's Law](https://en.wikipedia.org/wiki/Jamie_Zawinski#Notable_Quotes)). The more the software lives, the more complicated it becomes...

See #22

I would like to say that for an `opam` perspective and `dune`, the situation where `httpaf.cm{x}a` is available into the OPAM switch and available into `dream` become a fatal error...

Thanks, @aantron, same as @clecat, I will not be available for a moment but your PR will help us a lot!

Just to give you some projects about emails: - `mrmime` (https://github.com/mirage/mrmime) which is a decoder/encoder of emails - `emile` (https://github.com/dinosaure/emile) which parses email addresses - `colombe` (https://github.com/mirage/colombe) which is an...

The bug about SMTP is fixed, I will try to cut a release as soon as I can.

The current example provided by `dream` has some requirement due to the let's encrypt challenge, so it needs for any targets (including `unix`): - a domain-name (which points to the...

#146 should fix the issue if it corresponds to what you want. I'm not the best to explain stuffs.

On my side, I mostly aware about the initial diff/reason of the `httpaf` fork and I really would like to have only one `httpaf` instead of many and only trust...