Cyrus-imapd: Is it possible to transfer the #public namespaces' contents using cyradm xfer?

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












0














We are currently retiring an old server (Debian wheezy) with Cyrus imapd 2.4 which holds about 15 GB of messages. Most of the messages are located in the #public namespace. We would like to transfer all messages to a new server (Debian stretch) with Cyrus imapd 2.5.



Due to the simplicity of the method, we have decided to use cyradm xfer to achieve this goal. Transferring users' mailboxes went as expected: It was reasonably fast, all flags and permissions have been kept, and so on. Most important, subfolders in a user's mailbox have been transferred recursively.



Given that, we were quite surprised that it did not seem possible to recursively transfer the subfolders which are located in the #public namespace. This is a problem because we have thousands of subfolders there. Using wildcards with cyradm xfer does not work either (in contrast to many of cyradm's other commands).



Could anybody please tell us if we do something wrong or if cyradm xfer is indeed not able to do this? If this is true, we could use imapsync instead, but we would prefer an "original vendor" tool.










share|improve this question





















  • I always prefered to do a tar.gz of the involved directory tree in my multiple migrations activities, it is not as you are dealing with a migration in a mail server with a complex DB format. Much simpler to migrate files from one server to another.
    – Rui F Ribeiro
    Dec 15 at 17:45
















0














We are currently retiring an old server (Debian wheezy) with Cyrus imapd 2.4 which holds about 15 GB of messages. Most of the messages are located in the #public namespace. We would like to transfer all messages to a new server (Debian stretch) with Cyrus imapd 2.5.



Due to the simplicity of the method, we have decided to use cyradm xfer to achieve this goal. Transferring users' mailboxes went as expected: It was reasonably fast, all flags and permissions have been kept, and so on. Most important, subfolders in a user's mailbox have been transferred recursively.



Given that, we were quite surprised that it did not seem possible to recursively transfer the subfolders which are located in the #public namespace. This is a problem because we have thousands of subfolders there. Using wildcards with cyradm xfer does not work either (in contrast to many of cyradm's other commands).



Could anybody please tell us if we do something wrong or if cyradm xfer is indeed not able to do this? If this is true, we could use imapsync instead, but we would prefer an "original vendor" tool.










share|improve this question





















  • I always prefered to do a tar.gz of the involved directory tree in my multiple migrations activities, it is not as you are dealing with a migration in a mail server with a complex DB format. Much simpler to migrate files from one server to another.
    – Rui F Ribeiro
    Dec 15 at 17:45














0












0








0







We are currently retiring an old server (Debian wheezy) with Cyrus imapd 2.4 which holds about 15 GB of messages. Most of the messages are located in the #public namespace. We would like to transfer all messages to a new server (Debian stretch) with Cyrus imapd 2.5.



Due to the simplicity of the method, we have decided to use cyradm xfer to achieve this goal. Transferring users' mailboxes went as expected: It was reasonably fast, all flags and permissions have been kept, and so on. Most important, subfolders in a user's mailbox have been transferred recursively.



Given that, we were quite surprised that it did not seem possible to recursively transfer the subfolders which are located in the #public namespace. This is a problem because we have thousands of subfolders there. Using wildcards with cyradm xfer does not work either (in contrast to many of cyradm's other commands).



Could anybody please tell us if we do something wrong or if cyradm xfer is indeed not able to do this? If this is true, we could use imapsync instead, but we would prefer an "original vendor" tool.










share|improve this question













We are currently retiring an old server (Debian wheezy) with Cyrus imapd 2.4 which holds about 15 GB of messages. Most of the messages are located in the #public namespace. We would like to transfer all messages to a new server (Debian stretch) with Cyrus imapd 2.5.



Due to the simplicity of the method, we have decided to use cyradm xfer to achieve this goal. Transferring users' mailboxes went as expected: It was reasonably fast, all flags and permissions have been kept, and so on. Most important, subfolders in a user's mailbox have been transferred recursively.



Given that, we were quite surprised that it did not seem possible to recursively transfer the subfolders which are located in the #public namespace. This is a problem because we have thousands of subfolders there. Using wildcards with cyradm xfer does not work either (in contrast to many of cyradm's other commands).



Could anybody please tell us if we do something wrong or if cyradm xfer is indeed not able to do this? If this is true, we could use imapsync instead, but we would prefer an "original vendor" tool.







imap






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Dec 15 at 17:40









Binarus

237111




237111











  • I always prefered to do a tar.gz of the involved directory tree in my multiple migrations activities, it is not as you are dealing with a migration in a mail server with a complex DB format. Much simpler to migrate files from one server to another.
    – Rui F Ribeiro
    Dec 15 at 17:45

















  • I always prefered to do a tar.gz of the involved directory tree in my multiple migrations activities, it is not as you are dealing with a migration in a mail server with a complex DB format. Much simpler to migrate files from one server to another.
    – Rui F Ribeiro
    Dec 15 at 17:45
















I always prefered to do a tar.gz of the involved directory tree in my multiple migrations activities, it is not as you are dealing with a migration in a mail server with a complex DB format. Much simpler to migrate files from one server to another.
– Rui F Ribeiro
Dec 15 at 17:45





I always prefered to do a tar.gz of the involved directory tree in my multiple migrations activities, it is not as you are dealing with a migration in a mail server with a complex DB format. Much simpler to migrate files from one server to another.
– Rui F Ribeiro
Dec 15 at 17:45
















active

oldest

votes











Your Answer








StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);













draft saved

draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489170%2fcyrus-imapd-is-it-possible-to-transfer-the-public-namespaces-contents-using-c%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes















draft saved

draft discarded
















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid


  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.

To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489170%2fcyrus-imapd-is-it-possible-to-transfer-the-public-namespaces-contents-using-c%23new-answer', 'question_page');

);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown






Popular posts from this blog

Peggy Mitchell

Palaiologos

The Forum (Inglewood, California)