On Sat, 28 Mar 2015 08:55:24 -0700 Seth wrote: > > > If the filesystem supports case sensitivity then I can understand users > > > expecting the current behaviour but it doesn't seem practical to me and > > > I couldn't see a format specifier to lowercase deliveries to Maildir > > > expanding to just TAG. > > > > > > When someone sends to a tag user+...@users.org and there is an existing > > > folder Tag then it works great and I really love it, however I am sure > > > I cannot always trust senders to keep the case correct. > > > > > > Am I missing a configuration tweak? > > > > I use the lowercase delivery option to address this issue. > > > > accept from <blah blah blah> deliver to maildir > > "/var/vmaildir/%{dest.domain:lowercase}/%{dest.user:lowercase|strip}/mail/"
> As far as I can tell so far, this has no bearing on lower casing the > TAG? (portion after the + and before the @). Doh!, when I did that test I was editing the from any rule and sending from local. I thought it was strange that it did the same thing. So... Ace, this feature can work this way but you need a dot in front of the folder for IMAP client compatibility and I'll have to find a way to automatically check for new folders regularly or on client startup. /%{user.username}/.%{dest.user:lowercase}" Still trying to decide if it's worse but leaning to actually better? than a patch or filter which only delivers if the directory already exists (still creates both) and may save me the time I haven't got, Thanks. -- You received this mail because you are subscribed to misc@opensmtpd.org To unsubscribe, send a mail to: misc+unsubscr...@opensmtpd.org