Pilerimport imap error
Hi guys, we're testing piler for a small implamentation (150 users in exchange 2010 env.)
I've a strange error here, importing emails for a user via imap works just fine for the first 2944, from email 2945 I receive arrors:
duplicate: 47781-imap-2943.txt (duplicate id: 23877) duplicate: 47781-imap-2944.txt (duplicate id: 23878) failed to import: 47781-imap-2945.txt (id: 4000000055f6da68259a26ec00f150f47e55) error importing '47781-imap-2945.txt' failed to import: 47781-imap-2946.txt (id: 4000000055f6da691e1c5dcc00175ff1c41a) error importing '47781-imap-2946.txt' failed to import: 47781-imap-2947.txt (id: 4000000055f6da693335004c007f7cfff2f2) error importing '47781-imap-2947.txt' Processed: 2948 [ 54%]
Running the same import command with -D option works without any problem.
Can you please help me?
TIA, Cristiano
Comments (9)
-
-
repo owner Try copying that email to the archive as an rfc822 formatted eml file, and run pilertest against it, let's see if the parser can process it.
-
pilertest doesn't report errors, I tried to delete the first not imported and the last successfully imported emails but the import has the same problem at the same time.
-
I did some more tests and I found the email with the problem (or I hope). The email was not the first not imported but the last imported, I've just deleted from the imap server one email by one from the last imported back, and found the problematic one. I've tested it with pilertest and there are no errors.
what happened? Thanks, CM
-
repo owner Not sure, try to import it, eg. pilerimport -e /path/to/eml
-
email has been imported successfully. Is there a log to see infos from last imported email or something to easly find the email with error? maybe a log with the email ID or email's date and subject...
-
repo owner pilerimport doesn't log, it print any errors it stumbles to stdout. Probably a verbose mode could be useful to display these tidbits you mentioned. I'll add it to the todo list.
-
great thanks!
-
repo owner - changed status to resolved
- Log in to comment
Just to let you know the version I'm using root@piler:~# piler -v 1.2.0-master build 919