silverwind

If I understand these headers correctly: - `Return-Path` is for bounced error e-mails only, e.g. sent by smtp servers, not by users - `Reply-To` is what the clients will reply...

We should only set `Reply-To` when it's different than `From` [because](https://karl-voit.at/2021/07/21/reply-to/): > Some email clients issue a warning message when Reply-To: is set I do see we already set this...

I guess in any case, having this `Return-Path` option will be good to have, even thought it does likely not solve your use case.

Happy to merge this as-is for the Return-Path option. Could add check to compare it to `FROM` and skip setting it if equal but it would need to perform rfc5322...

BTW I just checked: Multiple headers values split on `,` and sub-values split on `;` and I think this is true for both mail and http headers.

Interesting block syntax, where's it from? At least GFM can't seem to render it.

> > Interesting block syntax, where's it from? At least GFM can't seem to render it. > > docusaurus buildin syntax > > https://docusaurus.io/docs/markdown-features/admonitions Thanks, I see https://github.com/facebook/docusaurus/issues/7471 is related.

Still want to do this, just haven't gotten around to it yet.

https://github.com/shoelace-style/shoelace looks like a interesting library of web components. It uses `floating-ui` so should be top-notch for placment of floating content.

What does "implementing via tailwindcss" exactly mean? You can't implement stuff like interactivity, reactivity, a11y and many other things with CSS alone.