1.171

ChangeLog

@@ -1,15 +1,28 @@
 
 RCS file: RCS/imapsync,v
 Working file: imapsync
-head: 1.169
+head: 1.171
 branch:
 locks: strict
 access list:
 symbolic names:
 keyword substitution: kv
-total revisions: 169;	selected revisions: 169
+total revisions: 171;	selected revisions: 171
 description:
 ----------------------------
+revision 1.171
+date: 2006/04/27 08:25:04;  author: gilles;  state: Exp;  lines: +21 -13
+Added more information with --justconnect
+ - OS system.
+ - kernel (uname -a)
+ - perl version
+----------------------------
+revision 1.170
+date: 2006/04/27 06:58:37;  author: gilles;  state: Exp;  lines: +21 -30
+Move "Multiple copies" bug in the FAQ.
+Removed "Flag bug in first sync".
+Added how to report bug.
+----------------------------
 revision 1.169
 date: 2006/04/13 21:36:15;  author: gilles;  state: Exp;  lines: +7 -6
 Added Zimbra IMAP success.

FAQ

@@ -7,7 +7,13 @@
 Q. We have found that the sent time and date have been changed to the 
    time at which the file was synchronised. 
 
-R. I guess this is the case with Eudora but not with Mutt, no ?
+R. This is the case with:
+   - Eudora
+   - Zimbra
+   but not with 
+   - Mutt
+   - Thunderbird
+
 Eurora shows by default the time the imap server received the email.
 I think it is quite a strong behavior since the messages can
 have travelled some time before the reception.
@@ -59,6 +65,31 @@ b) or use stunnel :
 c) or use stunnel on inetd
    imaps stream  tcp nowait cyrus /usr/sbin/stunnel -s cyrus -p /etc/ssl/certs/imapd.pem -r localhost:imap2
 
+=======================================================================
+Q: Multiple copies when I run imapsync twice ore more.
+
+R. Multiple copies of the emails on the destination
+server. Some IMAP servers (Domino for example) add some
+headers for each message transfered. The message is
+transfered again and again each time you run imapsync. This
+is bad of course. The explanation is that imapsync considers
+the message is not the same since headers have changed (one
+line added) and size too (the header part). You can look at
+the headers found by imapsync by using the --debug option
+(and search for the message on both part). The way to avoid
+this problem is by using options --skipheader and
+--skipsize, like this (avoid headers beginning whith the
+string "X-"):
+
+ imapsync ... --skipheader '^X-' --skipsize
+
+You can use --skipheader only one time; if you need to skip
+several different headers use the "or" perl regex caracter
+which is "|". Example:
+
+ imapsync ... --skipheader '^X-|^Status|^Bcc'
+
+
 ======================================================================
 Q. I want the --folder 'MyFolder' option be recurse.
 

README

@@ -2,7 +2,7 @@ NAME
     imapsync - IMAP synchronization, copy or migration tool. Synchronize
     mailboxes between two imap servers. Good at IMAP migration.
 
-    $Revision: 1.169 $
+    $Revision: 1.171 $
 
 INSTALL
      imapsync works fine under any Unix OS.
@@ -157,33 +157,27 @@ LICENSE
     the web site http://www.gnu.org/licenses/licenses.html
 
 BUGS
-    No known serious bug.
+    No known serious bug. Report any bug to the author. Before reporting
+    bugs, read the FAQ, this README and the TODO files.
 
-    Multiple copies: Multiple copies of the emails on the destination
+    In your report, please include:
-    server. Some IMAP servers (Domino for example) add some headers for each
-    message transfered. The message is transfered again and again each time
-    you run imapsync. This is bad of course. The explanation is that
-    imapsync considers the message is not the same since headers have
-    changed (one line added) and size too (the header part). You can look at
-    the headers found by imapsync by using the --debug option (and search
-    for the message on both part). The way to avoid this problem is by using
-    options --skipheader and --skipsize, like this (avoid headers beginning
-    whith X-):
 
-     imapsync ... --skipheader '^X-' --skipsize
+     - imapsync version.
+     - IMAPClient.pm version.
+     - perl version.
+     - operating system running imapsync.
+     - imap servers softwares on both side and their version.
 
-    You can use --skipheader only one time; if you need to skip several
+     Those values can be found with the command line
-    different headers use the "or" perl regex caracter which is "|".
-    Example:
 
-     imapsync ... --skipheader '^X-|^Status|^Bcc'
+     imapsync --host1 imap.host1.net  --host2 imap.host2.org  --justconnect
 
-    Flags : with some IMAP servers the flags are not very well copied the
+     And also, if it can help :
-    first time. Run imapsync twice if you want the flags set correctly.
-    (fixed since 1.28 release but wait for a time before removing those
-    lines)
 
-    Report any bugs to the author.
+     - operating systems on both sides.
+     - imapsync with all the options you use,  the full command line
+       you use (except the passwords of course)
+     - output given with --debug --debugimap near the failure point.
 
 IMAP SERVERS
     Failure stories reported with the following imap servers :
@@ -290,5 +284,5 @@ AUTHOR
     teaching free open and gratis softwares. Don't hesitate to pay him for
     that services.
 
-    $Id: imapsync,v 1.169 2006/04/13 21:36:15 gilles Exp $
+    $Id: imapsync,v 1.171 2006/04/27 08:25:04 gilles Exp $
 

VERSION

@@ -1 +1 @@
-1.169
+1.171

freshmeat_submition

@@ -1,5 +1,5 @@
 Project: imapsync
-Version: 1.168
+Version: 1.169
 Release-Focus: Major bugfixes
 Hide: Y
 Home-Page-URL: http://www.linux-france.org/prj/imapsync/

imapsync

@@ -6,7 +6,7 @@ imapsync - IMAP synchronization, copy or migration
 tool. Synchronize mailboxes between two imap servers. Good
 at IMAP migration.
 
-$Revision: 1.169 $
+$Revision: 1.171 $
 
 =head1 INSTALL
 
@@ -184,34 +184,28 @@ http://www.gnu.org/licenses/licenses.html
 
 =head1 BUGS
 
-No known serious bug.
+No known serious bug.  Report any bug to the author.
+Before reporting bugs, read the FAQ, this README and the
+TODO files.
 
-Multiple copies: Multiple copies of the emails on the
+In your report, please include:
-destination server. Some IMAP servers (Domino for example)
-add some headers for each message transfered. The message is
-transfered again and again each time you run imapsync. This
-is bad of course. The explanation is that imapsync considers
-the message is not the same since headers have changed (one
-line added) and size too (the header part). You can look at
-the headers found by imapsync by using the --debug option
-(and search for the message on both part). The way to avoid
-this problem is by using options --skipheader and
---skipsize, like this (avoid headers beginning whith X-):
 
- imapsync ... --skipheader '^X-' --skipsize
+ - imapsync version.
+ - IMAPClient.pm version.
+ - perl version.
+ - operating system running imapsync.
+ - imap servers softwares on both side and their version.
 
-You can use --skipheader only one time; if you need to skip
+ Those values can be found with the command line
-several different headers use the "or" perl regex caracter
-which is "|". Example:
 
- imapsync ... --skipheader '^X-|^Status|^Bcc'
+ imapsync --host1 imap.host1.net  --host2 imap.host2.org  --justconnect
 
-Flags : with some IMAP servers the flags are not very well
+ And also, if it can help :
-copied the first time.  Run imapsync twice if you want the
-flags set correctly.  (fixed since 1.28 release but wait for
-a time before removing those lines)
 
-Report any bugs to the author.
+ - operating systems on both sides.
+ - imapsync with all the options you use,  the full command line
+   you use (except the passwords of course)
+ - output given with --debug --debugimap near the failure point.
 
 =head1 IMAP SERVERS
 
@@ -340,7 +334,7 @@ Gilles LAMIRAL earn his living writing, installing,
 configuring and teaching free open and gratis
 softwares. Don't hesitate to pay him for that services.
 
-$Id: imapsync,v 1.169 2006/04/13 21:36:15 gilles Exp $
+$Id: imapsync,v 1.171 2006/04/27 08:25:04 gilles Exp $
 
 =cut
 
@@ -354,7 +348,8 @@ use Term::ReadKey;
 #use Digest::HMAC_MD5;
 use IO::Socket::SSL;
 use MIME::Base64;
-
+use English;
+use POSIX qw(uname);
 
 eval { require 'usr/include/sysexits.ph' };
 
@@ -396,7 +391,7 @@ my(
 use vars qw ($opt_G); # missing code for this will be option.
 
 
-$rcs = ' $Id: imapsync,v 1.169 2006/04/13 21:36:15 gilles Exp $ ';
+$rcs = ' $Id: imapsync,v 1.171 2006/04/27 08:25:04 gilles Exp $ ';
 $rcs =~ m/,v (\d+\.\d+)/;
 $VERSION = ($1) ? $1 : "UNKNOWN";
 
@@ -433,8 +428,8 @@ $error=0;
 
 my $banner = join("", 
 		  '$RCSfile: imapsync,v $ ',
-		  '$Revision: 1.169 $ ',
+		  '$Revision: 1.171 $ ',
-		  '$Date: 2006/04/13 21:36:15 $ ',
+		  '$Date: 2006/04/27 08:25:04 $ ',
 		  "\n",
 		  "Mail::IMAPClient version used here is ",
 		  $VERSION_IMAPClient,"\n"
@@ -475,9 +470,13 @@ if ($justconnect) {
 	my $from = ();
 	my $to = ();
 	
+
+	print "Here is a $OSNAME system (",
+	  join(" ", uname()), 
+	  ")\nwith perl ", 
+	  sprintf("%vd", $PERL_VERSION), "\n";
+	
 	$from = connect_imap($host1, $port1);
-
-
 	print "From software : ", server_banner($from);
 	print "From capability : ", join(" ", $from->capability()), "\n";
 	$to   = connect_imap($host2, $port2);