On Thu, Jul 02, 2015 at 02:34:34PM +0200, Tor Houghton wrote: > Hello, >
Hello, > I thought I'd post here, as the documentation appears to only mention '+' as > a local-part suffix (according to RFC specs, I presume). > > Because web, + tends to get translated to %20 (space) when registering on > some sites. This means that per-site mail adresses (e.g. for filtering and > data-leak detection purposes) won't work .. > > If my assumption is correct, is there a plan to support other suffixes as a > non-default option? > Your assumption is only correct if you assume the sites have broken code that doesn't encode/decode properly forms before submitting them. In the event of this happening, other characters would also need to be fixed as + is certainly not the only one that is valid in an email. Now as far as other suffixes are concerned there are no plans to support them in the daemon itself, it has implications [1], but it's likely that a filter to transparently translate suffixes will happen. [1] https://github.com/OpenSMTPD/OpenSMTPD/issues/476 -- Gilles Chehade https://www.poolp.org @poolpOrg -- You received this mail because you are subscribed to [email protected] To unsubscribe, send a mail to: [email protected]
