similar to: .dovecot.sieve.log/tmp failed: Not a directory

> On 19/03/2020 10:10 mabi <mabi at protonmail.ch> wrote: > > > Hello > > I am running Dovecot 2.3.9 for IMAP access with RainLoop webmail and have noticed for an account where I have some filters setup that I get the following error messages in the dovecot log file: > > Mar 17 19:02:50 mbox dovecot: imap(mail at domain.tld)<10511><ubAzvhCh1N2yxeu/>:

??????? Original Message ??????? On Thursday, March 19, 2020 9:13 AM, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > This is usually prevented by not configuring mail_home and mail_location to same directory: > > mail_home=/var/vmail/%Ld/%Lu/ > mail_location=maildir:~/mail Thanks for the tip. This means that if I now configure "mail_location=maildir:~/mail", I

Hello, I am running Dovecot 2.3.5.1 on OpenBSD 6.5 with RainLoop as IMAP webmail client and just noticed the following error messages about duplicate transaction log sequences in the index log: Jul 01 13:15:58 Error: imap(<REMOVED_EMAIL1>)<21324><TVSmwJyMd0C5D+Vb>: Transaction log /var/vmail/<REMOVED_DOMAIN>/<REMOVED_EMAIL1>/dovecot.index.log: duplicate transaction

On Fri, 10 Nov 2017 03:41:20 -0500 Bill Shirley <bill at KnoxvilleChristian.org> wrote: > No it isn't shown as a folder.? All folder directories here begin with a dot. > i.e.? .INBOX? .Trash? .Drafts > > Bill No, they don't. me thought that, too. But using the rainloop webmail interface on top of such a config showed the sieve folder in the overview. Sometimes you can

The issue was in the systemd service file. The option PrivateDevices was setted. It prevents the service to have access to physical devices. I removed this option and from there, quota is reported without errors. Thanks for your support Regards, - Eric Grammatico _/) 14 mars 2019 16:42 "Eric Grammatico" <e.grammatico at gmail.com> a ?crit: > Sure !! > > I got it ! I

Hi, I try to migrate an old fashioned mailsystem to Debian 9.7 / dovecot 2.2.7. I "have" to cope with mbox for now. I try to get rid of Sun OS 5.9 sendmail before mbox to mdbox migration (I'm fine if you laugh loudly ^^). Intended setup : 2 VM with exim (smtp in, smtp out roughly), 3 VM with dovecot (mbox, maildir, testbed), 1 VM with IMAP proxy and LMTP proxy. doveconf -n is

Hello, I use dovecot replication and the sieve scripts are not replicated. Mail replication is working fine. Log when sieve script (with Rainloop webmail) is created: Oct 12 12:57:57 srv1 dovecot: managesieve-login: Login: user=<hativ at example.com>, method=PLAIN, rip=91.67.174.186, lip=195.201.251.57, mpid=5360, TLS, session=<OXvK9QV4fOBbQ666> Oct 12 12:57:57 srv1 dovecot:

Hi, I have a working Installation with: Ubuntu 16.04 LTS Dovecot 2.2.22 MySql 5.7.24 Postfixadmin 3.2 Apache 2.4.18 Rainloop 1.12.1 I manage the E-Mail Accounts with postfixadmin in a MySql-DB. Also I use quotas with Quota Backend postfixadmin-DB (dict). Everything works fine. Now I installed a new Server with the following Versions and migrate the Configs to the new System. Ubuntu 18.04 LTS

I am running samba 3.0.20a in my FC4 linux machine, its running for two days. In /tmp direcotry I see lots of temporary files. Is it safe to remove these files? also I would like to why its creating these many files? SMBclose.8.req SMBreadX.58.resp SMBsesssetupX.61.req SMBtrans2.3.resp SMBwriteX.60.req SMBclose.8.resp SMBreadX.59.req SMBsesssetupX.61.resp

With quota count and quota_clone it works, but can I use noenforcing with quota count? quota = count:User quota:noenforcing When I test this config, I receive no quota-warning E-Mail: service quota-warning { executable = script /usr/local/bin/quota-warning.sh # user = dovecot user = vmail unix_listener quota-warning { user = vmail group = vmail mode = 0660 } } plugin {

Hello, What is the best way to hide sieve folders from IMAP clients? old config mail_home = /var/vmail/%d/%n plugin { sieve_dir = /var/vmail/%d/%n/.sieve/ sieve = /var/vmail/%d/%n/.dovecot.sieve } new config (hide sieve folder) mail_home = /var/vmail/%d/%n maildir_stat_dirs = yes plugin { sieve_dir = /var/vmail/%d/%n/sieve/ sieve = /var/vmail/%d/%n/.dovecot.sieve } Is there a better way

Hello In my setup I have the following in dovecot.conf (dovecot 2.0.12) mail_home = /buzones/mydomain/%2.26Hn/%2.200Hn/%n/home_usuario/ mail_location = mdbox:/buzones/my_domain/%2.26Hn/%2.200Hn/%n:INDEX=/indices_dovecot/indices/%2.26Hn/%2.200Hn/%n My problem is with the autocreation of mail_home. We are using roundcube+sieve plugin and the first time a user tries to use sieve fails with

Hi Folks, I am having a problem configuring imapsieve via dovecot-pidgeonhole on CentOS7. After following the docs here: https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve I get: dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process returned 89

On 3/21/19 3:57 PM, Aki Tuomi via dovecot wrote: > This because you have a very common misconfiguration, which is that your mail_home and mail_location are pointing to same directory, and that lead into this problem. > > Solution is of course to use: > > mail_home = /var/mail/vmail/%d/%n > mail_location = maildir:~/Mail > > Aki While not very intuitive, I have : mail_home

Hi, FWIW this was also reported back in August[1] - experienced with 2.3.2.1 (not sure if earlier 2.3 releases were affected) and currently reproducible with latest 2.3.3 stable release. [1] https://www.dovecot.org/pipermail/dovecot/2018-August/112548.html Cheers, Tony On 2018-10-12 04:26, Pascal wrote: > Hello, > > I use dovecot replication and the sieve scripts are not

Thanks for the additional hints, I have the following 2 questions first: - In order to launch the index heal is the following command correct: gluster volume heal myvolume - If I run a "volume start force" will it have any short disruptions on my clients which mount the volume through FUSE? If yes, how long? This is a production system that's why I am asking. > --------

Excuse me for my naive questions but how do I reset the afr.dirty xattr on the file to be healed? and do I need to do that through a FUSE mount? or simply on every bricks directly? > -------- Original Message -------- > Subject: Re: [Gluster-users] self-heal not working > Local Time: August 28, 2017 5:58 AM > UTC Time: August 28, 2017 3:58 AM > From: ravishankar at redhat.com >

Hi there, Well.. I didn't find a way to strace imap. If I well understood, the faulty IMAP is launched by dovecot from or after a succesfull imap-login process. I have executed manually '/usr/libexec/dovecot/imap -u eric' and typed getquotaroot "INBOX" which didn't reproduce the error seen in the dovecot logs and reported the correct quota. Any idea how to find the imap

Hello, Config infos below. Short version, I am getting this weird anomaly on my main email account. Such that, "dovecot.sieve" is showing up as a mailbox in my various email clients (e.g. k-9 (mobile), and Evolution). I have tried deleting the "rogue folder" with doveadm, but it just returns. Anyone have any suggestions where I can track this down. dovecot --version

On 08/22/2017 02:30 PM, mabi wrote: > Thanks for the additional hints, I have the following 2 questions first: > > - In order to launch the index heal is the following command correct: > gluster volume heal myvolume > Yes > - If I run a "volume start force" will it have any short disruptions > on my clients which mount the volume through FUSE? If yes, how long?