Nice

How was your no-captcha registration experience?

HOW DO YOU KNOW I DIDN'T GET A CAPTCHA REQUEST LOL

Possible bug here. When the reply notification came to my email, the subject was formatted as an HTML entity reference. Until we transition to UTF-8 support, I think the numeric references need to be stripped from the subject line. I can check if there's any alternative method of rendering an emoji in an email subject without some crazy conversion of the entire email.

Making a test reply so I can see the notification email.

I love how this one single post exposed a massive encoding bug in the board software. :P

Email delivery from this server is crazy slow, so I'm testing on a personal server today.

Learned so far: Emails with content type text/html still don't tolerate HTML character entity references in the Subject header. There does exist a method to encode UTF-8 within a Subject header, however I don't know yet if that's even possible with the Symfony mailer. Stripping the references is the best solution so far.

So this is interesting. For extra fun, I submitted a U2U with an emoji encoded as UTF-8 converted to ISO-8859-1 and then selected the send to e-mail option. This allows the browser to pass the data to the website using on-page code points. The Symfony mailer detected the mismatched content types and automatically encoded the Subject header in the appropriate UTF-8 format without changing any of the XMB code.

Email bugs should be fixed.

I checked everything on my end regarding delivery problems. It seems something is wrong with the server at DreamHost, accepting mail but not delivering anything today. I put in a support ticket about that.

The server issue should be resolved now.

Looks like I forgot to subscribe to this thread. Trying to properly test this now.