Hi, way forward could be like this:
1) Introduce a new config option 'detail_affix' with parameters 'prefix' and 'suffix', defaulting to 'suffix' making sure not to break existing setups using <user><delimiter><suffix> respectively :user<delimiter>:detail format. If 'detail_affix' is switched to 'prefix' the expected format of local parts turns into <prefix><delimiter><user> respectively :detail<delimiter>:user.
2) Add documentation to the Wiki https://wiki2.dovecot.org/LMTP: * detail_affix = suffix 3) Add description to the relevant default config files¹: # The separator that is expected between the :user and :detail # address parts introduced by the subaddress extension. This may # also be a sequence of characters (e.g. '--'). The current # implementation looks for the separator from the left of the # localpart and uses the first one encountered. The :user part is # left of the separator and the :detail part is right. This setting # is also used by Dovecot's LMTP service. #recipient_delimiter = + + + # Define if :detail is a prefix or a suffix to the :user address part, + # e.g. left or right, when using subaddress extension. + # Defaults to 'suffix' making sure not to break existing setups using + # <user><delimiter><suffix> format. + # Switch to 'prefix' if you use the <prefix><delimiter><user> format + # described in RfC 5233. + #detail_affix = suffix 4) Changelog + now we _fully_ support IETF RfC 5233² (Sieve Subaddress Extension), see new config parameter 'detail_affix'. What do you think? Thanks & greetings, Paul ¹ On my Debian this is /etc/dovecot/conf.d/20-lmtp.conf and /etc/dovecot/conf.d/90-sieve.conf ² https://tools.ietf.org/html/rfc5233 Am 13.05.2019 um 21:48 schrieb Paul Muster via dovecot:
Hi there, Dovecot's LMTP implementation and Pigeonhole Sieve already do support the <user><delimiter><suffix> format. RfC 5233, the Sieve subaddress extension, also offers <prefix><delimiter><user>. Could Docecot's LMTP and Pigeonhole be extended to that effect? Thanks & greetings, Paul
