similar to: Get rid of the "dbox-Mails"-folder

Displaying 20 results from an estimated 7000 matches similar to: "Get rid of the "dbox-Mails"-folder"

2018 Jul 07
1
Get rid of the "dbox-Mails"-folder
Hey again, sorry, but I have to correct me: Even with dot it's not working completely. The subscriptions file is not created and the dovecot-acl file has the wrong path, too. :-( Greetings, Hativ Am 07.07.2018 um 02:26 schrieb Hativ: > Hey again, > > I've found a working configuration: mail_location = sdbox:~/:FULLDIRNAME=. > > I use a dot instead of slash or empty
2018 Jul 08
2
Get rid of the "dbox-Mails"-folder
Hey Aki, DIRNAME with empty value has no effect, just like with FULLDIRNAME. "~/sdbox" instead of "~/" doesn't change that.. Greetings, Hativ Am 07.07.2018 um 20:24 schrieb Aki Tuomi: > Does it work better if you use > > mail_location=sdbox:~/sdbox:DIRNAME= > > > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- >
2018 Jul 07
0
Get rid of the "dbox-Mails"-folder
Hey again, I've found a working configuration: mail_location = sdbox:~/:FULLDIRNAME=. I use a dot instead of slash or empty value. Now my folder structure looks like I want and Dovecot is working fine. Can anyone (maybe even a Dovecot developer?) say if the configuration is okay? I've tried to check the source code, but I don't know C as good as it's needed for that.
2018 Jul 31
0
Get rid of the "dbox-Mails"-folder
Would it be possible to add the possibility in future releases that DIRNAME respectively FULLDIRNAME could be empty (and works properly)? Greetings, Hativ -------- Weitergeleitete Nachricht -------- Betreff: Re: Get rid of the "dbox-Mails"-folder Datum: Sun, 8 Jul 2018 15:40:46 +0200 Von: Hativ <hativ3 at gmail.com> An: dovecot at dovecot.org Hey Aki, DIRNAME with
2018 Oct 12
2
Sieve scripts not replicated
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:
2010 Jul 16
2
Questions about dbox (sdbox?), mdbox
Hello, So ive spent the last 45 minutes or so searching the list for dbox stuff, but Im not seeing anything real definitive. My question is basically whether the dbox format is ready for production environment, is sdbox or mdbox more stable/ready than the other or does it matter? What are people's experience/review with running this format (and if you reply can you tell me which one
2010 Sep 03
1
Suggested location for single-dbox
I've updated http://wiki2.dovecot.org/MailLocation regarding a typical mail_location entry for dbox. Previously it said: mail_location = dbox:~/dbox but of course "dbox" is now the old name for "sdbox", so the example should be updated to say "sdbox" and there might/ought also to be an example for "mdbox". In
2018 Nov 23
2
doveadm dsync-server doesn't use user parameter?
Hi, I tried to migrate my dovecot 2.2 to a new server with a other storage configuration and dovecot 2.3. New (and old) Server uses mysql for user information I use the following storage settings mail_home = /storage1/vmail/%{userdb:path} mail_location =
2011 Jan 24
1
Questiosn about dbox
Hello I have read carefully about dbox (/http://wiki2.dovecot.org/MailboxFormat/dbox/) and I have some questions: - One of the main advantages (speed wise) of dbox over maildir is that index files are the only storage for message flags and keywords. What happens when we want to recover some messages from backup? With maildir we can rebuild message indexes, but I am not sure about
2014 Oct 09
3
Dbox and Exim
The Dovecot wiki [1] doesn't list either Exim, Postfix or anything else as supporting the dbox. I did some searching in the Exim archives and have found only one message mentioning dbox, sdbox or mdbox. [2] I think an RFC would go a long way towards getting the format supported. Has Timo, or anyone else, considered submitting an RFC to the IETF? My question was how are we going to use it
2010 Sep 16
3
Moving from MBOX to Maildir or DBox ?
Hello Actually we use MBOX format for all our IMAP access but users complain they cannot create subfolders in imap folders, of course they cannot because of MBOX format ... I need gurus advices on changing mailbox format Maildir of Dbox ? What would be the safest way to go ? Note : we extensively use Thunderbird here. Thanks
2010 Jul 31
2
performance problems with {s,m}dbox
using rc3 and with the latest pigeonhole, I had problems with dovecot (deliver) keeping up with high volumes of E-mail. I tried sdbox, mdbox, and cyrdir all with similar (failed) result. using the default Maildir I had no problems. I did not try mbox. The problems seemed to happen when there were multiple deliver's running to the same folder I had defined in my sieve rules, either it would
2011 May 20
3
Crash test :)
I'm considering to move my mails from maildir/mbox to mdbox. One of my doubts is: how can I restore my mails when something terrribly wrong happens. I understand that I should use doveadm import "backup_location" "mailbox" all. So I try to import with: doveadm -v import "sdbox:~/Mail/dbox-temp/spamcop/reports/" "#Dbox/spamcop/reports" all #Dbox
2010 Sep 24
3
(Single instance) attachment storage with single-dbox
Just a note to myself and whoever else cares, should be added to wiki once it has its own page about this: With single-dbox messages can be copied with hard linking. This means that there can be multiple files that point to the same attachment file. The attachment is now deleted only once the mail file's link count drops to zero, so this works fine.. ..until someone goes and starts manually
2019 Jan 25
1
Rsync to backup dbox with SIS
We will be deploying a replacement Dovecot server soon, and we are planning to use maildir for the primary storage, but with an archive namespace using mdbox (or perhaps sdbox), and SIS. Our backup servers and (luke)warm spare server need to obtain full copies of the mail store. For the maildirs I know I can simply use rsync (we already use it here). I'm a little wary of using rsync with
2013 Nov 19
2
v2.2.8 released
http://dovecot.org/releases/2.2/dovecot-2.2.8.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.8.tar.gz.sig + Mail cache lookups work for the mail being saved. This improves performance by avoiding the need to parse the mail multiple times when using some plugins (e.g. mail_log). + Mail cache works for recently cached data also with in-memory indexes. + imapc: Many performance
2013 Nov 19
2
v2.2.8 released
http://dovecot.org/releases/2.2/dovecot-2.2.8.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.8.tar.gz.sig + Mail cache lookups work for the mail being saved. This improves performance by avoiding the need to parse the mail multiple times when using some plugins (e.g. mail_log). + Mail cache works for recently cached data also with in-memory indexes. + imapc: Many performance
2011 Feb 04
1
DoveCot 2.0.19: Problem compiling Solaris 10u9 x86 with dbox storage enabled
hi, I can't compile DoveCot 2.0.19 with dbox enabled on our Solaris 10/U9: LDFLAGS="-L/opt/csw/lib -L/usr/lib -R/opt/csw/lib/" ./configure --prefix=/usr/local/dovecot/2.0.19 --with-ssl=openssl --with-rundir=/var/run/dovecot --with-storages=maildir,mbox,dbox --with-ldap=yes gmake -> ========================== [... ../../src/lib-storage/mailbox-list.h:250: warning: parameter has
2011 Oct 07
1
Syntax to specify sdbox: mail_location path?
I'm implementing sdbox. In conf.d/10-mail.conf, with "maildir:" mail_location = maildir:/my_mailbox_path/%d/%n mail gets stored in /my_mailbox_path/%d/%n/new/ With "sdbox:" mail_location = sdbox:/my_mailbox_path/%d/%n mail gets stored in /my_mailbox_path/%d/%n/mailboxes/INBOX/dbox-Mails. How do I get rid of the '/mailboxes/' and '/dbox-Mails/' path
2019 Oct 11
2
Panic: file smtp-client-connection.c: line 1212 (smtp_client_connection_established): assertion failed: (!conn->connect_succeeded)
Hello Aki, I have this problem just with 2.3.8, my self-compiled 2.3.3 works fine. I have previously tried to update from 2.3.3 to higher versions (possibly 2.3.5 or so), but always had this error, which is why I am always back to 2.3.3. Configuration is exactly the same. Here my output from "doveconf -n": # 2.3.8 (9df20d2db): /etc/dovecot/dovecot.conf# Pigeonhole version 0.5.8