Invalid Flag
ytodros
I saw someone had earlier posted a problem they were having with the
\Recent flag. I am having a similar problem with the \Forward flag, I
am trying to copy mail from a mail server by a company called vircom,
to Zimbra, and on first run it stopped and I got this (personal info
starred):
[Oct 21 11:04:36] [info] info@***.com@s11.***: INBOX: fetching message
headers 1..59
Segmentation fault
#
When I ran it again, I immediately got this:
[Oct 21 11:53:07] [info] info@***.com@s11.***:
Net::IMAP::BadResponseError: parse error: invalid flag: \Forward (will
retry)
[Oct 21 11:53:10] [info] info@***.com@s11.***:
Net::IMAP::BadResponseError: parse error: invalid flag: \Forward (will
retry)
[Oct 21 11:53:13] [error] Net::IMAP::BadResponseError: parse error:
invalid flag: \Forward (giving up)
#
Any thoughts/suggestions?
Thanks.
Ryan Grove
\Forward isn't defined as an IMAP system flag in the spec, so it
shouldn't have a backslash in front of it. Some IMAP servers support
custom flags, called keywords, which aren't preceded by backslashes,
but I don't know if Zimbra is one of them.
It sounds like one of two things may be happening: either your vircom
server uses a non-standard \Forward system flag in violation of the
IMAP spec (which Zimbra chokes on when Larch tries to copy it), or
vircom is using a "Forward" keyword that Larch is somehow mangling
into a system flag (though this seems unlikely). Either way, though,
Larch should do a better job of verifying that the flags it's
transferring are supported on the destination server before trying to
copy them.
If possible, could you run Larch with with -V insane to capture the
full IMAP conversation up until this error occurs, and send it to me
for debugging (after first stripping out your username/password from
the logs)? That will help me track down the root of the problem.
- Ryan