New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

warning/error message if "--sep2 /" is used #32

Closed
mikosh75 opened this Issue Jun 5, 2015 · 5 comments

Comments

Projects
None yet
4 participants
@mikosh75

mikosh75 commented Jun 5, 2015

Hello
first of all thanks for this great piece of software!
We already migrated a lot of mailboxes from zimbra to O365 without any problem, also with admin delegated access.

After checking login infos, it usually says:

Host1: separator given by NAMESPACE: [/]
Host2: separator given by NAMESPACE: [/]
Host1: prefix given by NAMESPACE: []
Host2: prefix given by NAMESPACE: []
Host1 separator and prefix: [/][]
Host2 separator and prefix: [/][]

These days, only on certain domains, it started saying this:

Host1: separator given by NAMESPACE: [/]
Host2: NAMESPACE request failed for outlook.office365.com: * BYE Connection closed. 14; 11 BAD User is authenticated but not connected.
Give the separator character with the --sep2 option,
the folowing listing of folders may help you to find it:
Most of the time it is character . or /
so try --sep2 . or --sep2 /

Said that I have no idea of the cause of that message about NAMESPACE on host2 (O365), we tried option "--sep2 /" as imapsync suggests.
It seems to work about NAMESPACE, but it gives these warnings

Use of uninitialized value $h2_prefix in string eq at /root/imapsync/imapsync line 3091.
Use of uninitialized value $h2_prefix in concatenation (.) or string at /root/imapsync/imapsync line 3091.

Please find below the full output (domains and email are masked)

Transfer started at Fri Jun  5 12:55:33 2015
PID is 22378
Log file is LOG_imapsync/2015_06_05_12_55_33_email@domain.com.txt  ( to change it, use --logfile filepath ; or use --nolog to turn off logging )
$RCSfile: imapsync,v $ $Revision: 1.637 $ $Date: 2015/04/01 01:36:37 $
Here is a [linux] system (Linux zmta01.domain.com 2.6.32-74-server #142-Ubuntu SMP Tue Apr 28 10:12:19 UTC 2015 x86_64)
With perl 5.10.1 Mail::IMAPClient  3.35
Command line used:
imapsync/imapsync --dry --justfolders --nofoldersizes --buffersize 8192000 --nosyncacls --syncinternaldates --exclude Chats|Contacts|Emailed Contacts|Junk|Problemi di sincronizzazione|Trash|^Rubrica --useheader Message-Id --noauthmd5 --skipsize --host1 posta.domain.com --user1 name@domain.com --authuser1 admin@puntoitservizi.com --password1 MASKED --authmech1 PLAIN --host2 outlook.office365.com --user2 name@domain.com --authuser2 admin@domain.onmicrosoft.com --password2 MASKED --ssl2 --port2 993 --regextrans2 s#Sent#Posta inviata# --regextrans2 s#Drafts#Bozze# --sep2 /
Temp directory is /tmp  ( to change it use --tmpdir dirpath )
PID file is /tmp/imapsync.pid ( to change it use --pidfile filepath ; to avoid it use --pidfile "" )
Modules version list:
Mail::IMAPClient     3.35
IO::Socket           1.31
IO::Socket::IP       ?
IO::Socket::INET     1.31
IO::Socket::SSL      1.31
Net::SSLeay          1.35
Compress::Zlib       2.02
Digest::MD5          2.39
Digest::HMAC_MD5     1.01
Digest::HMAC_SHA1    1.01
Term::ReadKey        2.30
File::Spec           3.3
Time::HiRes          1.9719
Unicode::String      2.09
IO::Tee              0.64
File::Copy::Recursive 0.38
Authen::NTLM         ?
URI::Escape          3.29
Data::Uniqid         ?
( use --no-modules_version to turn off printing this Perl modules list )
Info: turned ON syncinternaldates, will set the internal dates (arrival dates) on host2 same as host1.
Info: will try to use PLAIN authentication on host1
Info: will try to use PLAIN authentication on host2
Info: imap connexions timeout is 120 seconds
Host1: IMAP server [posta.domain.com] port [143] user [name@domain.com]
Host2: IMAP server [outlook.office365.com] port [993] user [name@domain.com]
Host1: * OK IMAP4 ready
Host1: posta.domain.com says it has CAPABILITY for AUTHENTICATE PLAIN
Host1: success login on [posta.domain.com] with user [name@domain.com] auth [PLAIN]
Host2: * OK The Microsoft Exchange IMAP4 service is ready. [VgBJADEAUABSADAAOQBDAEEAMAAwADQAMQAuAGUAdQByAHAAcgBkADAAOQAuAHAAcgBvAGQALgBvAHUAdABsAG8AbwBrAC4AYwBvAG0A]
Host2: outlook.office365.com says it has CAPABILITY for AUTHENTICATE PLAIN
Host2: success login on [outlook.office365.com] with user [name@domain.com] auth [PLAIN]
Host1: state Authenticated
Host2: state Authenticated
Host1 capability: IMAP4rev1 ACL BINARY CATENATE CHILDREN CONDSTORE ENABLE ESEARCH ESORT I18NLEVEL=1 ID IDLE LIST-EXTENDED LIST-STATUS LITERAL+ LOGIN-REFERRALS MULTIAPPEND NAMESPACE QRESYNC QUOTA RIGHTS=ektx SASL-IR SEARCHRES SORT THREAD=ORDEREDSUBJECT UIDPLUS UNSELECT WITHIN XLIST
Host2 capability: IMAP4 IMAP4rev1 AUTH=PLAIN AUTH=XOAUTH2 SASL-IR UIDPLUS MOVE ID UNSELECT CLIENTACCESSRULES CHILDREN IDLE NAMESPACE LITERAL+
Excluding folders matching pattern Chats|Contacts|Emailed Contacts|Junk|Problemi di sincronizzazione|Trash|^Rubrica
[Chats]
[Contacts]
[Emailed Contacts]
[Junk]
[Trash]

Host1: separator given by NAMESPACE: [/]
Host2: NAMESPACE request failed but using [/] given by --sep2
Host1: prefix given by NAMESPACE: []
Use of uninitialized value $prefix_out in concatenation (.) or string at imapsync/imapsync line 3120.
Host2: prefix given by NAMESPACE: []
Host1 separator and prefix: [/][]
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 1283.
Host2 separator and prefix: [/][]
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.

++++ Listing folders
All foldernames are presented between brackets like [X] where X is the foldername.
When a foldername contains non-ASCII characters it is presented in the form
[X] = [Y] where
X is the imap foldername you have to use in command line options and
Y is the uft8 output just printed for convenience, to recognize it.

Host1 folders list:
[Chats]
[Contacts]
[Drafts]
[Emailed Contacts]
[INBOX]
[Junk]
[Posta eliminata]
[Posta indesiderata]
[Posta inviata]
[Sent]
[Trash]

Host2 folders list:

++++ Looping on each folder
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
[Drafts]                            -> [Bozze]
Creating folder [Bozze] on host2
Created  folder [Bozze] on host2        (not really since --dry mode)
Since --dry mode is on and folder [Bozze] on host2 does not exist yet, syncing messges will not be simulated.
To simulate message syncing, use --justfolders without --dry to first create the missing folders then rerun the --dry sync.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
[INBOX]                             -> [INBOX]
Creating folder [INBOX] on host2
Created  folder [INBOX] on host2        (not really since --dry mode)
Since --dry mode is on and folder [INBOX] on host2 does not exist yet, syncing messges will not be simulated.
To simulate message syncing, use --justfolders without --dry to first create the missing folders then rerun the --dry sync.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
[Posta eliminata]                   -> [Posta eliminata]
Creating folder [Posta eliminata] on host2
Created  folder [Posta eliminata] on host2      (not really since --dry mode)
Since --dry mode is on and folder [Posta eliminata] on host2 does not exist yet, syncing messges will not be simulated.
To simulate message syncing, use --justfolders without --dry to first create the missing folders then rerun the --dry sync.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
[Posta indesiderata]                -> [Posta indesiderata]
Creating folder [Posta indesiderata] on host2
Created  folder [Posta indesiderata] on host2   (not really since --dry mode)
Since --dry mode is on and folder [Posta indesiderata] on host2 does not exist yet, syncing messges will not be simulated.
To simulate message syncing, use --justfolders without --dry to first create the missing folders then rerun the --dry sync.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
[Posta inviata]                     -> [Posta inviata]
Creating folder [Posta inviata] on host2
Created  folder [Posta inviata] on host2        (not really since --dry mode)
Since --dry mode is on and folder [Posta inviata] on host2 does not exist yet, syncing messges will not be simulated.
To simulate message syncing, use --justfolders without --dry to first create the missing folders then rerun the --dry sync.
Use of uninitialized value $h2_prefix in string eq at imapsync/imapsync line 3349.
Use of uninitialized value $h2_prefix in concatenation (.) or string at imapsync/imapsync line 3349.
[Sent]                              -> [Posta inviata]
Creating folder [Posta inviata] on host2
Created  folder [Posta inviata] on host2        (not really since --dry mode)
Since --dry mode is on and folder [Posta inviata] on host2 does not exist yet, syncing messges will not be simulated.
To simulate message syncing, use --justfolders without --dry to first create the missing folders then rerun the --dry sync.
++++ End looping on each folder
++++ Statistics
Transfer started on               : Fri Jun  5 12:55:33 2015
Transfer ended on                 : Fri Jun  5 12:55:43 2015
Transfer time                     : 10.2 sec
Messages transferred              : 0 (could be 0 without dry mode)
Messages skipped                  : 0
Messages found duplicate on host1 : 0
Messages found duplicate on host2 : 0
Messages void (noheader) on host1 : 0
Messages void (noheader) on host2 : 0
Messages deleted on host1         : 0
Messages deleted on host2         : 0
Total bytes transferred           : 0 (0.000 KiB)
Total bytes duplicate host1       : 0 (0.000 KiB)
Total bytes duplicate host2       : 0 (0.000 KiB)
Total bytes skipped               : 0 (0.000 KiB)
Total bytes error                 : 0 (0.000 KiB)
Message rate                      : 0.0 messages/s
Average bandwidth rate            : 0.0 KiB/s
Reconnections to host1            : 0
Reconnections to host2            : 0
Memory consumption                : 99.6 MiB
Biggest message                   : 0 bytes
Detected 0 errors


Homepage: http://imapsync.lamiral.info/
Log file is LOG_imapsync/2015_06_05_12_55_33_name@domain.com.txt  ( to change it, use --logfile filepath ; or use --nolog to turn off logging )
@gilleslamiral

This comment has been minimized.

Show comment
Hide comment
@gilleslamiral

gilleslamiral Jun 5, 2015

Member

Hi,

Strange.

Add --prefix2 ""

imapsync ... --prefix2 ""

Le 05/06/2015 13:18, mikosh75 a écrit :

Hello
first of all thanks for this great piece of software!
We already migrated a lot of mailboxes from zimbra to O365 without any problem, also with admin delegated access.

After checking login infos, it usually says:

|Host1: separator given by NAMESPACE: [/]
Host2: separator given by NAMESPACE: [/]
Host1: prefix given by NAMESPACE: []
Host2: prefix given by NAMESPACE: []
Host1 separator and prefix: [/][]
Host2 separator and prefix: [/][]
|

These days, only on certain domains, it started saying this:

|Host1: separator given by NAMESPACE: [/]
Host2: NAMESPACE request failed for outlook.office365.com: * BYE Connection closed. 14; 11 BAD User is authenticated but not connected.
Give the separator character with the --sep2 option,
the folowing listing of folders may help you to find it:
Most of the time it is character . or /
so try --sep2 . or --sep2 /
|

Said that I have no idea of the cause of that message about NAMESPACE on host2 (O365), we tried option "--sep2 /" as imapsync suggests.
It seems to work about NAMESPACE, but it gives these warnings

|Use of uninitialized value $h2_prefix in string eq at /root/imapsync/imapsync line 3091.


Reply to this email directly or view it on GitHub #32.

Au revoir, 09 51 84 42 42
Gilles Lamiral. France, Baulon (35580) 06 20 79 76 06

Member

gilleslamiral commented Jun 5, 2015

Hi,

Strange.

Add --prefix2 ""

imapsync ... --prefix2 ""

Le 05/06/2015 13:18, mikosh75 a écrit :

Hello
first of all thanks for this great piece of software!
We already migrated a lot of mailboxes from zimbra to O365 without any problem, also with admin delegated access.

After checking login infos, it usually says:

|Host1: separator given by NAMESPACE: [/]
Host2: separator given by NAMESPACE: [/]
Host1: prefix given by NAMESPACE: []
Host2: prefix given by NAMESPACE: []
Host1 separator and prefix: [/][]
Host2 separator and prefix: [/][]
|

These days, only on certain domains, it started saying this:

|Host1: separator given by NAMESPACE: [/]
Host2: NAMESPACE request failed for outlook.office365.com: * BYE Connection closed. 14; 11 BAD User is authenticated but not connected.
Give the separator character with the --sep2 option,
the folowing listing of folders may help you to find it:
Most of the time it is character . or /
so try --sep2 . or --sep2 /
|

Said that I have no idea of the cause of that message about NAMESPACE on host2 (O365), we tried option "--sep2 /" as imapsync suggests.
It seems to work about NAMESPACE, but it gives these warnings

|Use of uninitialized value $h2_prefix in string eq at /root/imapsync/imapsync line 3091.


Reply to this email directly or view it on GitHub #32.

Au revoir, 09 51 84 42 42
Gilles Lamiral. France, Baulon (35580) 06 20 79 76 06

@jamesabbottsmith

This comment has been minimized.

Show comment
Hide comment
@jamesabbottsmith

jamesabbottsmith Nov 4, 2015

The "User is authenticated but not connected" message appears to be due to a failed password login on the Exchange side.

It's a generally unhelpful message.

See: http://unix.stackexchange.com/questions/164823/user-is-authenticated-but-not-connected-after-changing-my-exchange-password

jamesabbottsmith commented Nov 4, 2015

The "User is authenticated but not connected" message appears to be due to a failed password login on the Exchange side.

It's a generally unhelpful message.

See: http://unix.stackexchange.com/questions/164823/user-is-authenticated-but-not-connected-after-changing-my-exchange-password

@gilleslamiral

This comment has been minimized.

Show comment
Hide comment
@gilleslamiral

gilleslamiral Nov 9, 2015

Member

Hi James,

Thanks for this explanation. I've added it in the Exchange FAQ at
http://imapsync.lamiral.info/FAQ.d/FAQ.Exchange.txt

On 04/11/2015 04:36, James Abbottsmith wrote:

The "User is authenticated but not connected" message appears to be due to a failed password login on the Exchange side.

It's a generally unhelpful message.

See: http://unix.stackexchange.com/questions/164823/user-is-authenticated-but-not-connected-after-changing-my-exchange-password


Reply to this email directly or view it on GitHub #32 (comment).

Au revoir, 09 51 84 42 42
Gilles Lamiral. France, Baulon (35580) 06 20 79 76 06

Member

gilleslamiral commented Nov 9, 2015

Hi James,

Thanks for this explanation. I've added it in the Exchange FAQ at
http://imapsync.lamiral.info/FAQ.d/FAQ.Exchange.txt

On 04/11/2015 04:36, James Abbottsmith wrote:

The "User is authenticated but not connected" message appears to be due to a failed password login on the Exchange side.

It's a generally unhelpful message.

See: http://unix.stackexchange.com/questions/164823/user-is-authenticated-but-not-connected-after-changing-my-exchange-password


Reply to this email directly or view it on GitHub #32 (comment).

Au revoir, 09 51 84 42 42
Gilles Lamiral. France, Baulon (35580) 06 20 79 76 06

@klonos

This comment has been minimized.

Show comment
Hide comment
@klonos

klonos Nov 9, 2015

The message part is shown as “User is authenticated but not connected�. Some odd chars creeped there. I guess from copy-pasting.

klonos commented Nov 9, 2015

The message part is shown as “User is authenticated but not connected�. Some odd chars creeped there. I guess from copy-pasting.

@gilleslamiral

This comment has been minimized.

Show comment
Hide comment
@gilleslamiral

gilleslamiral Dec 20, 2015

Member

As explained, it means "valid user name but an invalid password" and it's an Exchange bug.
http://imapsync.lamiral.info/FAQ.d/FAQ.Exchange.txt

Member

gilleslamiral commented Dec 20, 2015

As explained, it means "valid user name but an invalid password" and it's an Exchange bug.
http://imapsync.lamiral.info/FAQ.d/FAQ.Exchange.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment