Skip Menu |

This queue is for tickets about the Mail-IMAPClient CPAN distribution.

Report information
The Basics
Id: 12961
Status: resolved
Priority: 0/
Queue: Mail-IMAPClient

People
Owner: Nobody in particular
Requestors: djc [...] cisco.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Date: Wed, 25 May 2005 16:20:14 -0700
From: Don Christensen <djc [...] cisco.com>
To: bug-Mail-IMAPClient [...] rt.cpan.org
Subject: migrate vs. flags bug
David, First, thanks for such a useful module. I'm faced with migrating lots of mail from lots of folders from one IMAP account to another. I figured this would be a good opportunity to refresh my perl skills and pick up some IMAP skills. Anyway, I was trying to use the "migrate" method to copy the messages from a test folder to another test folder, but it would not copy all of them. After learning even more than I planned while trying alternative solutions, I discovered that the source server supports creating new permanent flags while the destination server (MS Exchange--not my choice) does not. The messages that would not copy over had flags that are not supported on the destination server. It would be nice if the migrate command at least had the optional capability to cleanse the flags of those that are unsupported on the destination server. The best way to do it would be to get the list of supported flags on both sides and take the intersection, but right now I would be satisfied with a hard-coded list of the flags specified in the RFC. Thanks, -Don -- Don Christensen Senior Software Development Engineer djc@cisco.com Cisco Systems, Santa Cruz, CA "It was a new day yesterday, but it's an old day now."
New maintainer. Your request has resulted in a new flag: SupportedFlags, which will be available in 2.99_02