similar to: Long delays when deleting a message in inbox

Which log would you suggest? There's nothing for these times in mail.log, messages and syslog. Yves Goergen http://unclassified.software ________________________________________ Von: Aki Tuomi Gesendet: Fr, 2016-04-29 08:05 +0200 On 28.04.2016 20:54, Yves Goergen wrote: > Hi, > > Since recently, there's a long delay when deleting any message from my > inbox folder. This

This sounds more like misconfiguration to me. Can you provide doveconf -n and full output of namei -vl /full/path/to/mailbox ---Aki TuomiDovecot oy -------- Original message --------From: Yves Goergen <nospam.list at unclassified.de> Date: 19/05/2018 18:51 (GMT+02:00) To: Dovecot Mailing List <dovecot at dovecot.org> Subject: Re: Cannot delete folder The issue still exists. Can

Assuming '8' = mail, i cannot see anything wrong here... Can you turn on 'mail_debug=yes' and attempt folder deletion, and check logs after that? Aki > On 20 May 2018 at 16:19 Yves Goergen <nospam.list at unclassified.de> wrote: > > > Here's the output of 'doveconf -n': > > # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf > # Pigeonhole

I guess you have had different version(s) or setting(s) in the past, and you can probably fix this by setting perms to same as the new folders. Aki On 21.05.2018 11:46, Yves Goergen wrote: > I couldn't find anything relevant between all the debug log lines. Is > that in /var/log/mail.log? > > Here's the lines I think are related to creating and deleting the folder: >

Hi there, I cannot delete IMAP folders in new mailboxes. When trying to delete a folder in Thunderbird I get the error message "renaming not supported across conflicting directory permissions". Looking up the error on the web led me to checking the mailbox directory's permissions. They're inconsistent in new mailboxes. While every single directory in an old mailbox has

Hello, I am setting up a new server and migrating my Dovecot 1.2.9 config to the new 2.2.9 version. There wasn't much to keep from the old version so I had to recreate the config from scratch. Now I think I'm done but I can't login to IMAP. The log says this: > dovecot: auth: Error: prefetch(box@****.de,2001:****:7765,<bzAOP5QJXwAgAQpgEAXJAZyOMB1qBXdl>): userdb lookup not

Hello, the migration guide from Courier-IMAP to Dovecot says that I should change the folders namespace to "INBOX." if I want a seamless migration. Isn't it that e-mail clients determine that namespace automatically? At least I never needed to enter one in Thunderbird and then it was there. What happens if I copy the database, all the Maildir files, run the migration script to

Yves Goergen wrote: > The issue still exists. Can anybody explain to me why dovecot creates > IMAP folders with the wrong filesystem permissions? On a lark, I looked through my dirs @ permissions. Shorted lines a bit so they'd fit w/o extra lines between them using: (get rid of text before permissions, and shorten user/group to a few letter) find . -type d -ls|sed -r

Am 07.12.2014 um 00:56 schrieb Alexander Dalloz: > You did fulfill the requzirements for prefetch to work documented in the > wiki? > > http://wiki2.dovecot.org/UserDatabase/Prefetch Ehm, this is my SQL configuration 'dovecot-sql.conf.ext': > driver = mysql > connect = host=**** user=**** password=**** dbname=**** > default_pass_scheme = PLAIN > password_query = \

I couldn't find anything relevant between all the debug log lines. Is that in /var/log/mail.log? Here's the lines I think are related to creating and deleting the folder: > May 21 10:36:14 mond2 dovecot: imap(yg@****.de): Debug: Namespace : /var/mail/virtual/****.de/yg/.Test doesn't exist yet, using default permissions > May 21 10:36:14 mond2 dovecot: imap(yg@****.de): Debug:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 21 May 2018, Yves Goergen wrote: >> May 21 10:36:14 mond2 dovecot: imap(yg@****.de): Debug: Namespace : >> /var/mail/virtual/****.de/yg/.Test doesn't exist yet, using default >> permissions >> May 21 10:36:14 mond2 dovecot: imap(yg@****.de): Debug: Namespace : Using >> permissions from

Here's the output of 'doveconf -n': # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/local.conf:21: ssl_parameters_regenerate should have 'hours' suffix # OS: Linux 4.4.0-124-generic x86_64

Thank you for your reply. It's not that simple, though. Just because some core algorithms are standardised and should be compatible doesn't mean their use in different implementations leads to interoperable data. The key point here seems to be that Dovecot just supports SHA-1 with PBKDF2, not SHA-256. So I'm out of luck here. The different formats are no longer relevant then.

Hello, I'm setting up a new server and, again, seek for a decently secure (from a security specialist's POV) way to store and verify user passwords in a database. Additionally now, GDPR requires me to use a solid state-of-the-art solution. My OS is Ubuntu 20.04, Dovecot version 2.3.7, database backend with PostgreSQL 12. Obviously, storing the plaintext password is a terrible idea.

The issue still exists. Can anybody explain to me why dovecot creates IMAP folders with the wrong filesystem permissions? Every new folder that I create in the mailbox through Thunderbird (IMAP) has the wrong permission and cannot be deleted anymore. This looks like a dovecot bug to me. -Yves ________________________________________ Von: Yves Goergen Gesendet: Di, 2018-03-06 20:55 +0100 Hi

On 06.03.2018 21:55, Yves Goergen wrote: > Hi there, > > I cannot delete IMAP folders in new mailboxes. When trying to delete a > folder in Thunderbird I get the error message "renaming not supported > across conflicting directory permissions". Looking up the error on the > web led me to checking the mailbox directory's permissions. They're > inconsistent in

In case you are interested, https://wiki.dovecot.org/HowTo/ConvertPasswordSchemes By the way, I am bit sceptical that CRYPT-SHA512 is less secure than PBKDF2. CRYPT-SHA512 is not "just" SHA512(salt||password), it does at least 1000 rounds of hashing in similar way as PBKDF2 does. So, what is your reasoning for claiming that PBKDF2 is much secure than CRYPT-SHA512? Also, if you look

> On 29/08/2020 23:49 Yves Goergen <nospam.list at unclassified.de> wrote: > > > Hello, > > I'm setting up a new server and, again, seek for a decently secure (from > a security specialist's POV) way to store and verify user passwords in a > database. Additionally now, GDPR requires me to use a solid > state-of-the-art solution. > > My OS is

Am 07.12.2014 um 00:22 schrieb Yves Goergen: > Hello, > > I am setting up a new server and migrating my Dovecot 1.2.9 config to > the new 2.2.9 version. There wasn't much to keep from the old version so > I had to recreate the config from scratch. Now I think I'm done but I > can't login to IMAP. The log says this: > >> dovecot: auth: Error: >>

Hello- I have set up Dovecot before and feel fairly comfortable with it but am having some issues with a new setup and have not been able to find a solution via Google or the list archives. I use offlineiimap to sync an IMAP account with an email provider. After the sync is complete, my ~/Maildir is set up with a folder called INBOX (with cur,new,tmp inside) and all my other folders set up at