similar to: convert plugin created maildirfolder file in root maildir directory

Hello, as the tin says. I have several servers running 2.2.27 (Debian stretch) and am adding new ones with 2.3.4.1 (Debian buster). The configs were upgraded where needed but neither 10-mail.conf nor 15-mailboxes.conf were changed. 15-mailboxes is all commented out (I guess the default is auto-create, which isn't documented anywhere I could find) and the only non-comments in 10-mail.conf are

Can you provide full doveconf -n output? Also how are you delivering mail? Aki On 5.2.2020 4.24, Christian Balzer wrote: > > Hello, > > as the tin says. > I have several servers running 2.2.27 (Debian stretch) and am adding new > ones with 2.3.4.1 (Debian buster). > The configs were upgraded where needed but neither 10-mail.conf nor > 15-mailboxes.conf were changed. >

If I create a new folder using a mail client (eg. kmail/OE), the maildirfolder file is created world-writable. I assume that this is a security risk and should be -rw-------. eg. - create folder "Foo" in mail client ~ $ ls -la .maildir/.Foo/ total 20 drwx------ 5 robert users 4096 2009-01-21 19:56 . drwx------ 43 robert users 4096 2009-01-21 19:56 .. drwx------ 2 robert users 4096

Hi, I'm using version 1.0.13 of dovecot. I know it's somewhat dated, but that's the latest that Debian etch offers, and I would like to avoid compiling by myself if possible. dovecot is not creating the 'maildirfolder' in folders that are created via IMAP. Looking at the NEWS file, this was implemented in v1.0.rc7, so my version should have that working already. Is

Hello, I was asking what was the motivation for not having the envelope From in the Maildir format, as defined in the qmail spec : "The message is delivered without an extra UUCP- style From_ line, without any >From quoting, and without an extra blank line at the end." which may sound silly since we lose an important piece of information. Same question about the motivation in

Hi, we just setup a new mailserver for our company with some sieve filtering in place. Everything works as expected but there is one flaw. We setup the per user sieve filters in files within the users mailbox maildir as follows: lrwxrwxrwx 1 mail mail 21 Jan 13 17:20 .dovecot.sieve -> sieve/phpscript.sieve This link is actually picked up by dovecot and being announced as an IMAP

Hi folks. I was doing some testing this morning and realized Dovecot RC2 isn't fully compliant with the maildir++ specification. Most notably, it appears that Dovecot isn't creating a "maildirfolder" file (0 byte length) in folders it creates. >From http://www.inter7.com/courierimap/README.maildirquota.html "Within each subdirectory there's an empty file,

Hello, I've ran into problem with Dovecot and dsync replication. Everything works perfectly, including replication of sieve scripts, except fact that if user activates the 'managesieve' ruleset (I'm using currently Roundcubemail) on "mail1" host, it wouldn't be activated on "mail2" host, by creating symlink ".dovecot.sieve ->

Hi, I use dovecot-shared to add read permissions to the group in my mail server, which uses virtual users. This is only to ease backups. However, a few files are not created with the permissions in dovecot-shared. I've seen this happen to 'subscriptions', 'maildirfolder' (when dovecot-shared exists; the change to correctly create maildirfolder in this case is very

Hi, Currently using dovecot 2.3.2.1 and pigeonhole 0.5.2 on two identical hosts. I recently noticed ".dovecot.sieve" and ".sieve/managesieve.sieve" are not replicating from one host to the other in either direction. Mail is having no trouble replicating on both hosts with dsync, it is only sieve files that are not replicating for unclear reasons. # doveconf -n host 1:

I am cleaning up some old users, and found that in every maildir folder there is an empty file called maildirfolder, created at the time the original dovecot was installed. Is this empty file necessary for dovecot, or is it left there in an upgrade proces and can it be removed? Dovecot 2.1.7, on Debian wheezy. -- Roel Wagenaar, Linux-User #469851 with the Linux Counter;

Hi Everybody, I'd like to start archiving e-mails by moving them to a server with running Dovecot. I installed "dovecot-core" and "dovecot-imapd" (version 2.3.4.1) on Debian 10. One of a few configurations I made is to use Maildir: # grep '^mail_location = ' /etc/dovecot/conf.d/10-mail.conf mail_location = maildir:~/Maildir I successfully moved some e-mails (at

I'm a total newbie regarding imap servers. I'm trying to set up a Offlineimap/dovecot/Gnus system and Gnus complains that it cannot access the maildir... Here is my setup, put together by copying stuff from around the web without any prior knowledge of these tools... * Offlineimap is setup to use the $HOME/Maildir-free/, using --8<---------------cut

Hi everyone, I have noticed recently that Dovecot creates lock directories under users' Maildirs which look like IMAP folders. This is bad since users will see IMAP folders that are not supposed to be there. In my logs I see dovecot: imap(...): Error: file_create_locked(/.../Maildir/.vsize.lock) failed: Is a directory The directory in question # ls /.../Maildir/.vsize.lock/ cur/

Hi. Even new mails delivered by my MDA don't get the ,S= and ,W= fields set... (but when I "upload" a mail via IMAP to dovecot, they are set) Is there some place in dovecot where I need to enable this? Or would it be the MDA that has to calculate and set this already when placing a file in ./new? Thanks, Chris. -------------- next part -------------- A non-text attachment was

I'm using RC15 on Solaris 9. The wiki indicates that when a dovecot-shared file exists, "Dovecot uses the same permissions and GID when it creates index files, dovecot-uidlist file, new mail files, etc." In my case, Dovecot *is* creating new index files based on dovecot-shared, but dovecot-uidlist and individual message files don't completely match the permissions/group

Over the last year I've had a script moving old mail (120 days) into my annual archive folder. This is the first year I've done this with Dovecot, previously it was running against Cyrus. There's nothing particularly clever: a few conditions to match, then "move message to" the appropriate archive folder. There's one for every year from 2000 to 2015. 2015 is just

Hello Adam, and the dovecot list Just a question, I hate to pollute the thread, so feel free to push these questions into a new thread if deemed necessary. So as you can guess I'm a bit of a newb here, so rather obvious questions are about to arrive.... As you are using GIT for your archive (which is a cool idea by the way) I'm sure you are well aware that not all files types play nicely

Hi, I'm using dovecot imapd 0.99.10.5 from debian unstable and I noticed that dovecot returns everything in the maildir folder that starts with a "." as a folder as the result of LIST "" "%" command without checking if it is really a maildir folder (must contain the directories cur, new, tmp and the file maildirfolder). This is a little bit annoying because

On Date: Sun, 17 Jul 2016 12:24:04 +0200 Luigi Rosa <lists at luigirosa.com> wrote: > > Peter Chiochetti wrote on 17/07/2016 11:01: > > > With Maildir and path separator "." one can have incomplete paths: eg. > > bpatterson.INBOX.2011 will say that there is 2011 within INBOX within bpatterson > > -- while it is possible, that both bpatterson and