Wietse Venema:
> Kris Deugau:
> > grarpamp wrote:
> > > I've done - (qmail) to + (postfix) hurriedly in the past to avoid a
> > > meta issue. Other users migration or dual uses aside, with that
> > > one I wanted to but did not have benefit to research whether
> > > + or - had better merits. Such as which is in more common use now,
> > > which is trending to be more prevalent in the long term. And why?
> > > Honestly, best I could come up with was the large - legacy from
> > > decade old qmail-like installations, and not requiring the shift key
> > > seemed to win, heh :) I'm sure there are more sound thoughts
> > > on the matter in a paper somewhere.
> > 
> > - has the fairly significant advantage of being allowed on more sites
> > that try to validate "well-formed" email addresses - often in
> > Javascript.  Many such validators reject + in an email address.  :(
> 
> It would be relatively easy to implement "truncate the localpart
> at the first instance of any character in the delimiter set, then
> do one table lookup" (basically, replacing strchr() with strcspn()).
> 
> This would allow one to use '-' for some websites and '+' for others.

Unfortunately this would break existing code that expands
$recipient_delimiter, for example the forward_path default value.

This means using a new parameter name for the recipient delimiter
set, and making the recipient_delimiter default value dependent on
the value of that new parameter (for example take the first character).

        Wietse

> This could later be made more configurable, for example "for each
> delimiter in the specified order: truncate the localpart, do
> table lookup, and stop after the first successful lookup".
> 
> As long as users stick to names with [a-zA-Z0-9.], the first,
> simpler, implementation should be sufficient.
> 
>       Wietse
> 

Reply via email to