similar to: recipient delimiters

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

I use recipient_delimiter addresseses quiet a bit, and I want to put several of them into a mailbox if anyof (header :contains ["to"] [ ?FOO", ?foo", ?bar", ?florin"]) { fileinto :create ?later"; stop; } When I get an email addressed to me+FOO at example.com or me_florin at example.com, the messages end up in my inbox (Yes, I have both + and _

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

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, I have a forum system which can potentially have users send email to it for posting purposes that arrives addressed to a particular user account with a recipient delimiter: user+1a2b3c4d5e6f at domain.com The forum server is supposed to check the "user" account mailbox's inbox for the messages and post them to the site automatically. This doesn't work right now

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.

Hi! As a new user, I'm trying to set up a postfix + dovecot combination, and so far all is running smoothly. I'm using the guidelines that came with postfix and adjusting them as I go. My user and alias database is stored in MySQL, using the scheme from 'PostfixAdmin' (http://high5.net/page9.html) and I am using the dovecot LDA 'deliver' to drop messages into mailboxes

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

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

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

Hi, Am 15. November 2015 01:46:29 MEZ, schrieb fsantiago at garbage-juice.com: >Hello, > >I have a forum system which can potentially have users send email to it > >for posting purposes that arrives addressed to a particular user >account >with a recipient delimiter: > >user+1a2b3c4d5e6f at domain.com > >The forum server is supposed to check the "user"

Hi, It would be nice if the recipient_delimiter configuration option supported multiple recipient delimiters as Postfix now does. e.g. now if I set: recipient_delimiter = +- in Postfix, then test-extension at sample.com and test+extension at sample.com are both recognized. But if I set: recipient_delimiter = +- in Dovecot, neither of the above are recognized and instead test+-extension at

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

Hi, I'm attempting to proxy lmtp using director to hash to the same backend as pop3/imap. My pop3/imap users are of the form: username and my lmtp users are of the form: <username at domain> Where domain is fairly redundant but does carry some useful information. Now, I can proxy lmtp using user=%{username} and destuser=%{orig_user}, and this all appears to work correctly.

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

From the Notes section of my sieve file, because I always forget this # MORE NOTES: # Using :localpart takes just the local part of an address # header selects a header, address selects an address # Looks like this is the spec: # :localpart = :user+:detail # address are :localpart @ :domain, or :user + :detail @ :domain # See RFC5233 I use this bit for figuring out what :detail something (might)

Dear List, I have an ascii text file with data I'd like to extract. Example: Year Built: 1873 Gross Building Area: 578 sq ft Total Rooms: 6 Living Area: 578 sq ft There is a lot of data I'd like to ignore in each record, so I'm hoping there is a way to use strings as delimiters to get the data I want (e.g. tell R to take data between "Built:" and "Gross" -

Hello, does the recipient_delimiter option accepts multiple delimiter by now? -- Regards J?rg Backschues

On 15/03/2020 21:26, GMX Account wrote: > have a look at this: > > http://www.postfix.org/postconf.5.html#recipient_delimiter > > [...]When the recipient_delimiter [1] set contains multiple characters > (Postfix 2.11 and later), a user name or .forward file name is > separated from its extension by the first character that matches the > recipient_delimiter [1] set.[...]

Dear list, I read in ?plotmath that I can use bgroup to draw scalable delimiters such as [ ] and ( ). The same technique fails with < > however, and I cannot find a workaround, grid.text(expression(bgroup("<",atop(x,y),">"))) Error in bgroup("<", atop(x, y), ">") : invalid group delimiter Regards, baptiste sessionInfo() R version