imapsync error (\X-Has-Attach)

[roopeshsheth]

I'm currently using Scalix 11.0.4. I am interested in trying out ZCS. I've got the server setup fine, but when trying to imapsync my mailbox, I'm getting the following error:

BAD parse error: non-storable system tag "\X-Has-Attach"

Has anyone seen this and/or know what to do??

[roopeshsheth]

I've spent at least two days on this issue, and will have to give up soon...

imapsync \
        --host1 mail.domain.com --user1 roopesh --password1 password \
        --host2 zimmail.domain.com --user2 roopesh --password2 password \
        --delete2 \
        --expunge2 \
        --authmech2 LOGIN \
        --nosyncacls \
        --syncinternaldates \
        --subscribe \
        --subscribe \
        --folder INBOX  \
        --nofastio1 \
        --nofastio2

gives me

BAD parse error: non-storable system tag "\X-Has-Attach"

on almost every message with an attachment (99%+). But not all (can't figure out the pattern, some .doc and rtf files make it through, not others).

I've tried with/without subscribe, nofastio, syncinternaldates, nosyncacls, but everything returns me the same error on messages with attachments.

I am trying to migrate mailboxes from Scalix 11.0.4 to Zimbra ZCS 4.5 (latest available).

[dkarp]

Basically, what you're running up against is that Scalix broke the IMAP specification in order to add some features to their web client.

If you check out the flag and flag-extension productions in RFC 3501 section 9 (the ABNF grammar), you are not allowed to return a flag that starts with "\" unless it's one of the ones from RFC 3501 ("\Answered", "\Flagged", "\Deleted", "\Seen", "\Recent", or "\Draft") or it's defined in another RFC. Scalix pissed all over this, and as a result imapsync to any other server is probably going to fail.

If there's a way to tell Scalix to not send non-standard system flags, try that. Otherwise, we may have to try to tweak imapsync to drop such flags.

[roopeshsheth]

Thanks for the quick response. I tried

--skipheader "X-Has-Attach"

and

--regexflag 's/"X-Has-Attach"//g'

but neither resolved the issue.

I wish I could tell Scalix to do what I wanted! I don't see a way to force an RFC compliant response.

I have been poking around in the imapsync code, but I haven't seen anything that would resolve this issue (yet). Please let me know if you have any ideas.

FYI - There is also a Barracuda Spam Firewall that front-ends all my email. Could that be adding in the flag?

Thanks!

Roopesh Sheth

[dkarp]

--regexflag   <regex>  : Apply the whole regex to each flags list.
                         Example : 's/\"Junk"//g' # to remove "Junk" flag.

[roopeshsheth]

So I applied

--regexflag 's/\X-Has-Attach//g'

and now I get this:

BAD parse error: zero-length content

But if I look at the output from imapsync, I see this:

now:
flags from : [\Seen $MdnSent \]["12-Mar-2007 20:13:36 -0400"]
before:
flags from : [\Seen $MdnSent \X-Has-Attach]["12-Mar-2007 20:13:36 -0400"]

Where the "\" is after $MdnSent is where the "\X-Has-Attach" used to be. I think I need to get rid of the "\".

[dkarp]

...but you may have to use "\\" in order to escape the backslash.

[roopeshsheth]

Ah, got it figured out:

--regexflag 's/\\X-Has-Attach//g'

I immediately got another X-* flag called "\X-Forwarded". I changed the regex to

--regexflag 's/\\X-*//g'

And everything works fine!

Thanks!! Awesome help on a Saturday!

[illc0mm]

Doh!

I too am migrating from Scalix. I realized this was a Scalix issue and honestly didn't think of even asking about it. I only had a handful of boxes to migrate for our testing so I just used the outlook migration tool.

When we to move to production, however, this will make it much easier!

[roopeshsheth]

I looked at the Outlook Migration wizard, but I'm all Linux (yeah, baby!) and didn't want to deal with Crossover or Wine to run the .exe for the wizard.

Good luck!