Scalix Forums

Hello,

we try to migrate approx. 3GB of emails from a cyrus 2.1 imap server to scalix 11.0.4.x.
So far with mixed results.

We have used the settings from

http://www.scalix.com/wiki/index.php?ti ... d_imapsync

but we still have some two problems:

1. Emails with german umlauts in the address name are not migrated correctly, they show up as =?iso-8859-1?Q?Daniel_Sch=FC [=?iso-8859-1?Q?Daniel_Sch=FCrer?= <schuerer@ertech.ch>] in scalix.

2. Some emails just "refuse" to get stored in scalix, I then see this error in the imapsync tool:

Couldn't append msg #11 (Subject:[The subject...]) to folder Public Folders/Kunden/thisclient: 54 NO cannot append that message


Any ideas what might cause these two issues and how to solve them ?
Or is there another way of getting the mails from cyrus 2.1 to scalix 11.0.4.x ?

André

Hi André,

What was the address name before migration? Also, for your example, was the whole address :
=?iso-8859-1?Q?Daniel_Sch=FC [=?iso-8859-1?Q?Daniel_Sch=FCrer?= <schuerer@ertech.ch>]

or was it just :
=?iso-8859-1?Q?Daniel_Sch=FCrer?= <schuerer@ertech.ch>

If it was the latter, and Daniel's name was "Daniel Schürer" then this is more correct than
"Daniel Schürer" <schuerer@ertech.ch>
would be (an RFC822 address should only contain 7 bit characters). Most IMAP clients understand the RFC 2047 encoding used by Scalix for address comments which would otherwise contain 8 bit characters.

For the messages which give the result "NO cannot append that message", Scalix believes there is something wrong with the messages that are being appended. This means either that the messages are not correct RFC822 messages or Scalix has bugs which cause it to fail on them We would need to see the IMAP command used in the append to be able to diagnose the issue. You could use wireshark or something similar to trap the network traffic for this (monitor port 143 for IMAP)

Regards,
Gren.

i ve got exactly the same problem. i ll migrate from cyrus v2.1.18 to scalix 11.1.0.45, but if i use imapsync some emails failed with the error message:



did you already find a solution/work-around or do you still need a network dump?

edited: i can t find any error in my logfiles, i looked in mail.log and i also tried omschowlog. Does anybody know where scalix logs these errors? Or do i ve to increase my error level?

Hi,

A network dump would still be extremely useful.
Logging (over and above network tracing) would typically go to the same place omshowlog looks. It is possible to increase the amount of logging for the IMAP server using, say :


The default level is 7. To see higher levels of logging with omshowlog, you could use :

This might or might not help... To some extent, the IMAP server is just saying that it thinks it was given an invalid request and it may not log diagnostics as to why (but it might do!)

You could also add IMAP tracing which might help too. See :
viewtopic.php?t=6560&postdays=0&postorder=asc&highlight=sxlog+user+cfg&start=15

and the references to sxlog.user.cfg

Regards,
Gren

thanks for your fast reply.

i increased the log level:

then i tried again to copy a "non-working" mail and entered "omshowlog -s imap -l 15" as root in console. but i found nothing in the log, the last entry was logged a few days ago.

i ll send you the network dump via email.

Hello again,

Sorry, I forgot that you need to restart the IMAP service to cause the change in logging level to be noticed :


Regards,
Gren.

Hi Patrick,

I've just been looking through the logging you sent me in a personal email.

This line :
[OM 10289] === Tracing - Escaped at /build/11.1.0/src/lib/ual/ual_attach.c:1986 [101:574]
occurs because you do not have access rights to the folder you are attaching to.
I noticed that you were targeting a public folder, so lack of write access to that is probably the reason.

The error reporting is not great here, but how you could sometimes get from 101:574 to a meaningful error...


This gives you a list of groups - The "101" in the error code means "mc_101" which has group OM.UI.

-------------------------------------------------------------------------------
Error Group: OM.UI Error Number: 574

Insufficient access capabilities to perform this command

Regards,
Gren.

regarding my situation:
i try to move our cyrus imap server to a Scalix server on a new (virtual) machine with Debian Etch.

imapsync did a great job, but some mails are dropped by the Scalix imap server:
error message is always "cannot append that message"

i localized one email in a public folder of our cyrus server, which was not copied. then i removed every email from the scalix-public-folder and tried to copy all 49 emails from the cyrus folder to Scalix public folder via Thunderbird. After 19 emails Thunderbird stopped: "cannot append that message". i deselected the message, i already sent to you, and copied the remaining 29emails without any problem.
imho it is the message, but i don t know why? the message contains only a small picture about ~40kb large, some of the other emails in this folder contains attachments of 2-3MB!

so i tested again with this message and i found a "workaround":
i copied the message from cyrus public folder to my Scalix inbox. And then from Scalix inbox to Scalix public folder.

i can also copy that message from Cyrus public folder to my Scalix "sent items".

then i tried the next test:
i copied the same message into my cyrus inbox. then i tried to copy it to Scalix public folders and i still get the same error "cannot append that message". It was no problem to copy the mail to the Scalix inbox.

result of the tests:
i can not copy that single mail from cyrus (any folder) to a scalix public folder, but into my scalix inbox. at first glance i would also say that this should be a access problem, but my user is also owner of some public folders and i also can copy other emails into all public folders - just not that single email (and a feew others)...

i think i ll create a subfolder in my scalix inbox and i ll move the cyrus public folders into that inbox subfolder.

but i m still interesting in finding the error/mistake - if you need any information, please post it.