similar to: Rails query param delimiter?

On 6/2/2016 3:50 PM, Tanstaafl <tanstaafl at libertytrek.org> wrote: > On 6/2/2016 10:35 AM, Tanstaafl <tanstaafl at libertytrek.org> wrote: >> Trying to find out if dovecot supports the use of multiple recipient >> delimiters, as postfix does, but can't find an answer... > > The reason this is important is simple. I've encountered a lot of sites > that

Trying to find out if dovecot supports the use of multiple recipient delimiters, as postfix does, but can't find an answer... The wiki only mentions it in two meaningful places (that I can find)... With respect to postfix: /wiki.dovecot.org/LDA/Postfix The above seems to imply that for postfix/LDA all I need to do is define it in postfix (which supports multiple recipient delimiters). And

Since many broken websites and idiot companies will not allow a ?+? in an email address, I have long used two delimiters in postfix: recipient_delimiter = +_ However, now that dovecot is handling verification for postfix via reject_unverified_recipient, dovecot complains about any address using an _ as a delimiter. I don?t see a way to tell dovecot what delimiters to use, and it appears it is

hi all, i've exim 4.53RC2 + dovecot-cvs on OSX 10.4.2. i'm working on implementing recipient-delimiters for delivery from exim to a user's imap store using dovecot's cvs-lda. reading on the wiki (Jakob's latest comments?): " ... the part after the delimiter is passed to the lda as an additional parameter. so dovecot-lda should handle that parameter and leave the

I read in the list archives about work in progress on an lmtp delivery agent.As a previous cyrus user where that was the preferred delivery method from postfix, this sounds interesting. I was wondering whether it will handle recipient delimiters. ie will it be able to map user+foo at example.com to user at example.com? I'm not interested in the delivery into folder stuff, just the plain

Hello, There is a disconnect between the way Postfix handles recipient_delimiter and the way Dovecot handles it. For Postfix, it is a set of delimiters that can each individually be used to separate the address from the . In Dovecot, having multiple characters in recipient_delimiters simply makes it a multi-character single delimiter. For my purposes, the Postfix method is much more

On Sun, 2017-04-02 at 22:42 +0100, Michael Miller via samba wrote: > Hi > > I could not get a custom "shadow:delimiter" for the vfs shadow_copy2  > module to work successfully for me with Samba 4.6.2. I did not try  > previous versions. Based on my testing it seems that an additional line  > of code is needed in vfs_shadow_copy2.c as shown in the patch below  >

I''ve read about the problems of using page cache when there''s a query string, i.e. /article/list?page=1 will cache /article/list.html, then /article/list?page=5 will retrieve /article/list.html regardless of query string. I''m using a workaround, it looks almost obvious but since I haven''t found it mentioned anywhere I''m afraid there''s some

Hi (+mailing list again for the archives) My config which does show previous versions: # /usr/local/samba/sbin/smbd --version Version 4.6.11 To avoid having this config block within in each share, I define the following within the [global] section:   shadow:snapprefix = ^\(monthly\)\{0,1\}\(weekly\)\{0,1\}\(daily\)\{0,1\}$   shadow:delimiter = _UTC_   shadow:format =

Hi, As per the list.samba.org link, did you try including the delimiter within the format, ie as shown in the following? shadow:snapprefix = ^d[A-Za-z0-9]*y$ shadow:delimiter = _IPG_ shadow:format = _IPG_%Y.%m.%d-%H.%M.%S Regards, Mike On 16/02/2018 16:50, Edouard Guigné via samba wrote: > Hello Dear Samba Users, > > I have sucessfully set a samba share on a centos 7 box (samba 4.6.2)

On Wed, 12 Apr 2023 08:29:50 +0000 Emily Bakker <emilybakker at outlook.com> wrote: > Some example data: > ?leucocyten + gramnegatieve staven +++ grampositieve staven ++? > ?leucocyten ? grampositieve coccen +? > ? > I want to split the strings such that I get the following result: > c(?leucocyten +?, ??gramnegatieve staven +++?, > ??grampositieve staven ++?) >

Hi I could not get a custom "shadow:delimiter" for the vfs shadow_copy2 module to work successfully for me with Samba 4.6.2. I did not try previous versions. Based on my testing it seems that an additional line of code is needed in vfs_shadow_copy2.c as shown in the patch below (some comment updates are included too for code readability). Without the below patch, previous versions

Hi, I notice you're using 4.6.2 and I'm using 4.6.11. I made the following comment at some point within [global]:   #disable "unix extensions" to avoid using "allow insecure wide links"   #  for access to ../xxxx_SNAPS for BTRFS "previous versions" snapshots   #  --it seems to have reverted once more to not need the below two settings   ##unix

On 20/06/2019 01:20, @lbutlr via dovecot wrote: > On 18 Jun 2019, at 15:03, @lbutlr via dovecot <dovecot at dovecot.org> wrote: >> I don?t see a way to tell dovecot what delimiters to use, and it appears it is still using a single delimiter only despite postfix having added support for more than one years ago. > Ideas? There is the recipient_delimiter setting. For recent

Hi all, I've been scratching and poking, but basically, the file I need to read has two delimiters that I need to contend with. The first is that the file contains tabs (\t) , instead of newlines (\n), and the second is that the fields have | for the seperators. I can easily do a read if I first convert the \t to \n and then use read.table to get the file read with the | separator. But, what

Dear all after an upgrade to 1.6 from 1.4 (as explained in the UPGRADE-1.6.txt file) the | delimiter is not working by default. I've added a compat section in asterisk.conf a [options] dontwarn = yes [compat] pbx_realtime=1.4 res_agi=1.4 app_set=1.4 And restarted Asterisk, but i still have problem to have the | delimiter working, [Jun 9 23:20:54] DEBUG[11744]: pbx.c:3122

query strings built by R method can''t handle multiple values from checkbox selections R(SomeRoute, :reply_status=>%w{1 2 4}) should return query_string=" http://localhost:3301/someroute/?reply_status_id=1&reply_status_id=2&reply_status_id=4 " qsp(query_string) -> {"reply_status_id"=>["1", "2", "4"]} from

Hi All, I'm new to rsync usage in Mac OS X. I'm having a strange issue with -- files-from option. I'm providing the --files-from to provide a file , which contains the list of files separated by newline character , to perform backup operation. Especially in Mac OS X , particular tiff bundle files are having \r as part of the filename.When rsync reads the filepaths using delimiter

On 18 Jun 2019, at 15:03, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > I don?t see a way to tell dovecot what delimiters to use, and it appears it is still using a single delimiter only despite postfix having added support for more than one years ago. Ideas? -- Lead me not into temptation, I can find the way.

As RFC3501 (IMAP) say: 'A NIL hierarchy delimiter means that no hierarchy exists; the name is a "flat" name.' How to change delimiter to NIL? We have flat namespaces in our storage. Now I hardcoded this and everything is working, but maybe it is another possibility... -- Konrad