/dev/rob0:
> On Wed, Apr 03, 2013 at 04:27:30PM -0400, grarpamp wrote:
> > Is there a facility or ways to configure postfix to
> > recognize and process multiple recipient_delimiter
> > address extensions?
> No. As documented recipient_delimiter is a single character. Please
> also note that the word used here, delimiter, is singular. There's a
> reason for that.
There needs to be a tie-breaking rule when one user's delimiter
appears inside another user's name. There is of course also a
potential performance hit.
As for implementations:
1) One general implementation would support a list of delimiter
characters. It would first search with the complete localpart, and
then for each delimiter, it would try to terminate the localpart
at the first instance of that delimiter character and search the
lookup table. In other words with a set of N delimiter characters,
Postfix would do up to N table lookups with shortened localparts.
The problem is that multiple lookup table could match when one
user's delimiter appears inside another user's name. Which table
match should Postfix use? There can be no more than one. The order
of the list of delimiter characters would have to decide the priority
of one delimiter over another.
2) I would expect that terminating the localpart only once, at the
first match with any delimiter, would work well in practice (basically,
replacing strchr() with strcspn()). This would make only one table
lookup with the shortened localpart. This is guaranteed to match
at most once, but it may not match what you want, when one user's
delimiter appears inside another user's name.
Wietse
