similar to: no sieve with lmtp_save_to_detail_mailbox=yes

Hi, I have a dovecot 2.3.2.1 instance running here that is getting userdb and passdb data from a SQL database. This was a cyrus server migrated over and all users are happy. All users except one: Said user asked if it would be possible to disable subaddressing (localuser+folder at example.com) again. The setting controlling that is AFAIK the lmtp_save_to_detail_mailbox item. My idea was to

Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> writes: > On Tue, 10 May 2016, Jon Kristensen wrote: > >> Which Pigeonhole Sieve extension should I use to process/test a >> message >> depending on whether the message is in a particular mailbox? >> (Is it the >> mboxmetadata extension by any chance? If so, I would appreciate >> if >>

Hi I am just learning to setup dovecot as part of a project to move my home mail serving from a large and complex linux computer which is acting as internet router/nat gateway to the internet (this leaving me exposed without internet connection when it goes down) to a raspberry pi - which will be port-forwarded to, when I turn my internet cable modem back into a router/modem. I have chosen

> lmtp_save_to_detail_mailbox = yes Plus-delivery conflicts with existing, reserved files such as "subscriptions": Message for kim+subscriptions@ results in: lmtp(kim@***.com)<14493><SK7sEvaHEWSdOAAAvAYmHA>: Error: ....stat(/var/mails/***/kim/Maildir/subscriptions/tmp) failed: Not a directory Version: 2.3.18

> On 15/03/2023 13:12 EET Dejan <me at dejanstrbac.com> wrote: > > > > lmtp_save_to_detail_mailbox = yes > > Plus-delivery conflicts with existing, reserved files such as > "subscriptions": > > Message for kim+subscriptions@ results in: > > lmtp(kim@***.com)<14493><SK7sEvaHEWSdOAAAvAYmHA>: Error: >

Hi! Since our mails aren't saved correctly since we updated to 2.xx I'd really appreciate some help. What's going wrong? My mistake? Bug? Peer ---------- Weitergeleitete Nachricht ---------- Betreff: [Dovecot] Saving mails to +detail failed: Namespace error Datum: Dienstag, 3. Mai 2011, 12:50:20 Von: Peer Heinlein <p.heinlein at heinlein-support.de> An: dovecot at

We have the following namespace: namespace { inbox = yes list = yes location = prefix = INBOX/ separator = / subscriptions = yes type = private } namespace { list = children location = maildir:%%h:INDEX=%h/shared/%%u:CONTROL=%h/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } and we set: lmtp_save_to_detail_mailbox = yes

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 10 Feb 2014, Alan Chandler wrote: > The problem I am facing is I can find no documentation about what > lmtp_save_to_detail_mailbox actually causes lmtp to actually do. Searching > the wiki refers to it only in the LMTP page. > > How should the detail of the address be formatted to specify a subdirectory - > can it be

Is there any way to control/disable this for certain mailboxes? For one account (that handles bounces) I need it disabled, for all the other (normal) accounts its great. -- Andrew Ray

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

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 _

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Which Pigeonhole Sieve extension should I use to process/test a message depending on whether the message is in a particular mailbox? (Is it the mboxmetadata extension by any chance? If so, I would appreciate if someone could tell me what the reason is for it not being enabled by default.) The reason I want to perform this test is that I have

Steffen Kaiser: > Is the detail delived to Dovecot by the MTA at all? sure! have to say: I faked that example. In reality I tested the inverse way: My lab setup actually *do* deliver to folders and I saw, setting lmtp_save_to_detail_mailbox to 'no' still deliver to folder while INBOX was expected. so, correct hint: I should really try on an other system ... But from my debug logs it

Hello, My dovecot server (2.2.33.2) work with "lmtp_save_to_detail_mailbox = no" Now I would like to enable the feature for /some/ users. Is that an option that could be set from an LDAP entry? I tried the following: modify my ldap schema to allow an optional attribute "lmtp-save-to-detail-mailbox" in /etc/dovecot/ldap.conf user_attrs = ...

Hi Timo, we wrote a simple Patch for the Dovecot quota policy daemon. If a user is over quota, I prefer blocking the user sending e-mails, so I need a policy daemon, that's able to use the envelope or sasl sender as lookup key. I'd be happy if that patch can become part of the normale Dovecot releases. Peer -------- Original-Nachricht -------- Betreff: Re: Fwd: Quota-Patch Datum:

I am struggling with an archive namespace. I am not sure if this is can solved. But if you right click in apple mail on a message and choose archive. It wants to move the message to the folder Archive folder (marked in the attached). If I set inbox=yes it is possible to move the mail in this folder, but then I get other problems (two namespaces with inbox=yes). When I leave it inbox=no, I get

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 As far as I understood fetch -u p.heinlein at jpberlin.de hdr mailbox-guid [...]93d5 uid 58175 should fetch exactly the header of the specified mail. But on my Dovecot 2.2.12 it fetches the header *twice* (same with body, same with text). ======================================== hdr: Return-Path: <hello at example.com> Delivered-To:

Hi, having the attached configuration with Dovecot 2.2.9, Dovecot's crashing when moving a mail from a shared folder into another shared folder. Moving that mail into a "real" folder of the user or moving that mail from a real folder into the shared folder is always working. But moving from a shared folder into a shared folder doesn't work. Sep 2 11:47:42 mail02 dovecot:

We're running Dovecot in a multipe instance cluster with individual userdb-querys to different LDAP-Servers. As far as I can see there's no way to use the doveadm mailbox command with different Auth-Sockets or different configurations. While root at dobby4:/etc/dovecot# doveadm user -a /var/run/dovecot-xy/auth-master p.heinlein at example.com field value uid 10000 gid 10000

i can't delete several folders at once. I have a folder structure like folder1/folder2/folder3 (we use slash as hierarchy separator). When i delete folder1 server1 executes the command correctly Apr 16 13:44:28 server1 dovecot: imap(d.kuhn at heinlein-support.de): Mailbox deleted: INBOX/Trash/folder1/folder2/folder3 Apr 16 13:44:28 server1 dovecot: imap(d.kuhn at heinlein-support.de):