similar to: doveadm - mailbox to filesystem directory?

Displaying 20 results from an estimated 20000 matches similar to: "doveadm - mailbox to filesystem directory?"

2012 May 04
1
doveadm mailbox: rc=0 on error
Hi all, I use "doveadm mailbox mutf7 -7 $folder" to convert imap foldernames to UTF-8. If $foldername is not mUTF-7 encoded, doveadm returns "doveadm(root): Error: Mailbox name not valid mUTF-7: $folder" This errormessage is printed on stderr but the returncode of doveadm is zero. I tested with dovecot-2.0.* and dovecot-2.1.* # all right: $ doveadm mailbox mutf7 -7
2020 Jul 27
0
Migration from one server to 2 new servers
This is what my understanding. May be I am also wrong here. Backup option is there in my new server, production2. When I use the command with -R option from new server, it is connecting to old server, Production1 and giving the output of the doveadm backup command in old server to get the data. If you see the command and error I posted, it shows the same. Sorry just incase if I am wrong.
2020 Jul 27
0
Migration from one server to 2 new servers
Oh, I am extremely sorry. I was confused when typing the issue. Please help me in fixing the issue. Production1 is my old server. Production2 is my new server. Typing here correctly. Ignore all previous one's. The new version is: ==================== [root at production2 ~]# dovecot --version 2.2.36 (1f10bfa63) The old version is : ====================== [root at production1 ~]# dovecot
2019 Mar 12
1
Re: “doveadm mailbox” command fails with UTF-8 mailboxes
> On Mar 12, 2019, at 3:28 PM, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > >> On 12 March 2019 21:20 Felipe Gasper via dovecot <dovecot at dovecot.org> wrote: >> >> >> Hello, >> >> I?ve got a strange misconfiguration where the following command: >> >> doveadm -f pager mailbox status -u spamutf8 'messages vsize
2020 Jul 28
0
Migration from one server to 2 new servers
Hey Kishore? I believe this is the thread I mentioned earlier. It is quite long and spans a monthly barrier (Feb\Mar 2012) so if you use the ?Next\Previous message? links, you need to be sure to pick up the thread in each monthly archive. I have provided links to the first post of the thread in each archive here: https://dovecot.org/list/dovecot/2012-February/133718.html
2019 Mar 12
0
Re: “doveadm mailbox” command fails with UTF-8 mailboxes
> On 12 March 2019 21:20 Felipe Gasper via dovecot <dovecot at dovecot.org> wrote: > > > Hello, > > I?ve got a strange misconfiguration where the following command: > > doveadm -f pager mailbox status -u spamutf8 'messages vsize guid' INBOX 'INBOX.*' > > ? fails with error code 68, saying that it can?t find one of the mailboxes. (It lists
2020 Jul 27
2
Migration from one server to 2 new servers
Hi , I have tried the below command from the new server. But I am getting an error. Anything is missing here? ======== [root at production1 test.org.com]# doveadm backup -R -u kishore at test.org.com remote:vmail at production2.baplc.com vmail at production1.baplc.com's password: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] altmove [-u <user>|-A]
2020 Jul 27
2
Migration from one server to 2 new servers
Well that option set still doesn?t look correct? Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36? [Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2 [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm [Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f
2020 Jul 27
0
Migration from one server to 2 new servers
I am executing the command from the new server. I was executing the command from production2 server only. It has the backup option, but whereas production1 doesn't have it. Though I am executing from production2, I am seeing the below error. Is it becasue production1 server doesn't have that option? Please let me know, if it is confusing. The old version is: ==================== [root at
2020 Jul 27
2
Migration from one server to 2 new servers
I seem to recall a post a while back where, due to the age of the remote end, the remote side command had to be entered in the command executed on the local side. Do you have dsync on the 2.0.9 machine? > On Jul 27, 2020, at 4:16 PM, Kishore Potnuru <kishore.reachme at gmail.com> wrote: > > This is what my understanding. May be I am also wrong here. > > Backup option
2020 Jul 27
0
Migration from one server to 2 new servers
> On 27/07/2020 11:59 Kishore Potnuru <kishore.reachme at gmail.com> wrote: > > > Hi > > I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions. > > My Current Production Server details: >
2020 Jul 27
0
Migration from one server to 2 new servers
No, but there is backup option on the new server. That's why the -R, which means "backup to here". Aki > On 27/07/2020 16:20 Kishore Potnuru <kishore.reachme at gmail.com> wrote: > > > Hi, > > But there is no "doveadm backup" option in dovecot 2.0.9 version. > > [root at production ~]# doveadm -backup > doveadm: invalid option --
2020 Jul 28
2
Migration from one server to 2 new servers
Hi! Kishore, you got the command wrong.. `doveadm backup -R -u username-goes-here imapc:` for this to work, you need to configure following things: imapc_host = old-host-name imapc_password = master-password imapc_master_user = master-user-name and on the old host you need passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } This should
2019 Sep 28
0
dsync having problems with @-sign in mailbox names
> On 28 Sep 2019, at 12.21, Philip Iezzi via dovecot <dovecot at dovecot.org> wrote: > > Hi there > > We are running Cyrus-to-Dovecot migrations using dsync on destination Dovecot server (Debian Stretch / latest Dovecot 2.3.7.2 from community repo) like this: > > $ doveadm -o mail_fsync=never backup -R -u <username> imapc: > > For imapc configuration to
2019 Sep 28
0
dsync having problems with @-sign in mailbox names
> On 28 Sep 2019, at 11:48, Philip Iezzi via dovecot <dovecot at dovecot.org> wrote: > > >> On 28 Sep 2019, at 11:28, Sami Ketola via dovecot <dovecot at dovecot.org> wrote: >> >> >> >>> On 28 Sep 2019, at 12.21, Philip Iezzi via dovecot <dovecot at dovecot.org> wrote: >>> >>> Hi there >>> >>> We
2019 Sep 28
2
dsync having problems with @-sign in mailbox names
> On 28 Sep 2019, at 11:28, Sami Ketola via dovecot <dovecot at dovecot.org> wrote: > > > >> On 28 Sep 2019, at 12.21, Philip Iezzi via dovecot <dovecot at dovecot.org> wrote: >> >> Hi there >> >> We are running Cyrus-to-Dovecot migrations using dsync on destination Dovecot server (Debian Stretch / latest Dovecot 2.3.7.2 from community
2016 Jul 23
3
Converting mailboxes to UTF-8
Is any proven routine to migrate mailboxes from mUTF-7 to UTF-8 encoding? I've try to use doveadm list/mutf7/rename but have been stuck with nested inboxes. Say I have the next structure: INBOX INBOX.??? INBOX.???.??? encoded for FS respectively as .INBOX .INBOX.&BDYESwRA- .INBOX.&BDYESwRA-.&BE8ENARK- ?When I've try to rename ?INBOX.??? with doveadm mailbox rename -u me
2020 Jul 27
4
Migration from one server to 2 new servers
Hi I am in the process/planning of moving from my existing dovecot imap/pop3 server to 2 new servers (for HA/Resilience). I will be implementing dovecot replication on new servers. Please find my current and new servers versions. My Current Production Server details: ======================== Linux OS - Red Hat Enterprise Linux Server release 6.5 (Santiago) Dovecot version - 2.0.9
2020 Jul 27
3
Migration from one server to 2 new servers
Hi, But there is no "doveadm backup" option in dovecot 2.0.9 version. [root at production ~]# doveadm -backup doveadm: invalid option -- 'b' [root at production ~]# dovecot --version 2.0.9 Copy the contents by using "scp", will that work? Thanks, Kishore Potnuru On Mon, Jul 27, 2020 at 10:00 AM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > >
2012 Jun 24
0
nouveau _BIOS method
Hi to all! I have a problem with a nvidia geforce 520mx [NVd0 generation card (0x0d9110a1)] i have on my notebook (samsung 3 series). In practice i'm not able to use it with bumblebee and bbswitch. The dmesg message is: [ 13.507435] nouveau 0000:01:00.0: power state changed by ACPI to D0 [ 13.507440] nouveau 0000:01:00.0: power state changed by ACPI to D0 [ 13.507448] nouveau