mailsync-list — discussion about development, config, bugs etc.

[Mailsync-list] uid vs msgid

[Ganesan R <rga...@de...>]

Hi,

Is there any plans to get mailsync to use uids instead of msg nos. I plan
to use mailsync to periodically (every 10 minutes) sync between two IMAP
servers. I am worried that any changes that happen to the mailbox while the
sync is happening can mess up the sync.

Ganesan

[Mailsync-list] imapclient keeps asking for password for every folder

[Ganesan R <rga...@de...>]

Hi,

I am facing the same problem as the one mentioned in the debian bug CC'd
above. mailsync keeps asking for a password for each folder when no password
is configured. Even if I enter a password in the .mailsync mailsync keeps
closing the connection and opening a new one for every folder.

Tomas Pospisek wrote:
>                               I probably won't have the time to fix this
> before holidays [10.6-10.7]. My hypothesis is, that den connection is
> being closed when a mailbox is finished. If anybody wants to have a look
> at it, please do so.

Access to my imap server is rather slow, so I tried to dig into the problem.
The problem appears to be caused by this code starting line 213 in channel.cc

============
  // strangely enough, following Mark Crispin, if you write into
  // an open stream then it'll mark new messages as seen.
  //
  // So if we want to write to a remote mailbox we have to
  // HALF_OPEN the stream and if we're working on a local
  // mailbox then we have to use a NIL stream.
  if (store_to.isremote) {
    if(! store_to.store_open( OP_HALFOPEN) ) {
      fprintf( stderr, "Error: Couldn't open store %s\n",
		       store_to.name.c_str());
      return 0;
    }
  } else { ...
==========

Inside the debugger, I notice that store_to.store_open() calles mail_open(),
mail_open() closes the stream! I looked into c-client sources, and I find
that mail.c closes the old stream if you pass the OP_HALFOPEN flag and the
old stream is not half-opened. May be some one can dig around deeper. Please
Cc me because I am not subscribed to this list.

Ganesan
      

[Mailsync-list] Welcome to www.dumpsmarket.ws

[<dn...@jo...>]

Welcome to www.dumpsmarket.ws
Here you can buy stolen passports, counterfeit dollars and all other things you are in want of. If you need, we would provide you with the info about the bank account of a person who you are interested in. Also there are credit cards dumps of US and Europe residents. Your faithfully,panther aka Graph.

Re: [Mailsync-list] Migrating cyrus imap Suse Emailserver 3 to Debian/testing

[Sascha W. <bi...@ki...>]

On Sat, Sep 11, 2004 at 10:54:07PM +0200 or thereabouts, Sascha Wuestemann wrote:
> Hi mailsync-list members,
> 
> I am to migrate a running emailserver "Suse Emailserver 3" shipped with
> cyrus-imapd v2.0.16 to an up-to-date debian/testing with cyrus21-*
> v2.1.16. The new system shall replace the old and shall have all
> mailboxes containing full content and also all shared folders with full
> content - seen-information shall be original of all content, too. The
> emailusers shall notice no difference in use to the change.

Hi,

Thanks for you answers. Meanwhile, having slept over it, I look to that
a lot more cooler.
I think, the fastest way is, if I have file access doing it directly at
the file level rather than using additional services like IMAP or SMTP
and IMAP.

If I find a tool, I'll give it a try, if not, I will use my perl
capabilities to create my own.

I will keep this ML informed.

cu
Sascha

Re: [Mailsync-list] Migrating cyrus imap Suse Emailserver 3 to Debian/testing

[Tomas P. <tp...@so...>]

First: if you're in hurry, you have a good chance to shoot your user's 
mailboxes in their feet. So take a step back look at the options, test 
first and transfer after. Especially: test whether seen flags will be 
preserved, since with c-client that is a bit problematic.

On Sat, 11 Sep 2004, Sascha Wuestemann wrote:

> I am to migrate a running emailserver "Suse Emailserver 3" shipped with
> cyrus-imapd v2.0.16 to an up-to-date debian/testing with cyrus21-*
> v2.1.16. The new system shall replace the old and shall have all
> mailboxes containing full content and also all shared folders with full
> content - seen-information shall be original of all content, too. The
> emailusers shall notice no difference in use to the change.

Last time I looked, cyrus had a user-mail export script. At least cyrus 
from debian. So theoretically you can:

 	for u in users; do cyrus-mail-export $u; done

> The new debian emailserver is ready tested to take the old messages.
>
> I have access to both email servers and backupserver filesystems, and I
> am ordered not to stress the running server. So I'd like to use mailsync
> migrating from a local directory containing the old emailservers
> files.
>
> My worries are, that the folder structure of old and new cyrus are so
> different.
> - Does mailsync care for it and places everything to the right
>  _new_version_ place? See downwards for a description.

Yes it should.

> I have not yet read the mailsync documentation carefully, because I am
> in a hurry and very limited with time. Testing is complicated because of
> limited bandwith and huge amount of data, so I'd like to ask you more
> questions:
>
> Assuming above answer of my question is yes:
> - If I use a complete backup of all data to migrate residing in a local
>  directory, can I use mailsync to sync /old-directory to the current
>  system regarding all mailboxes, shared folders and seen information
>  with one single command?

Not with a single command. You'll have to find out first how to access all 
the mailfolders. And then you'll have to at least transfer once for every 
user his inbox and then all the rest.

> - I want to test the result of mailsync with a not up-to-date snapshot
>  just to make shure that everything will be alright and step back
>  afterwards and use the current data if I trust it. I assume just
>  deleting the corresponding directories of cyrus ( /var/spool/cyrus,
>  /var/lib/cyrus) and restoring from a local backup of the situation
>  before would be sufficient, right? mailsync does not touch /etc or so,
>  does it?

I don't know what and how cyrus stores where. mailsync is only concerned 
with accessing a mailbox through whatever means available (in your case 
that would be through IMAP). So no, mailsync will not touch /etc.

> - Which directories of the old data must be in place if using from a
>  local directory?

None. You access them through IMAP.

> Let me list information about the folder structure of old and new cyrus:
>
> old:
> /var/spool/imap contains a lot shared folders, user and stage.
> /var/spool/imap/user contains folders with the mailusers name but no
> single letter directories - the mailusers name folders are the mailboxes
> /var/imap contains the working directory of cyrus, e.g mailboxes-db
>
> new:
> /var/spool/cyrus/mail contains directories from a-z and stage.
> At the single letter directories you find user/ and mailusers name
> folders therein, e.g.
> /var/spool/cyrus/mail/s/user/sascha - this is the testuser's mailbox
> /var/lib/cyrus is cyrus' working directory

This does not matter to mailsync, see above.

> ...if mailsync is not capable to do what I am expected to get ready -
> does anybody know a source of tools which can migrate the structure of
> cyrus v2.0.16 to v2.1.16?

Check /var/lib/dpkg/info/cyrus*.list. There was one a mail export/import 
tool and or read /usr/share/doc/cyrus*/*

*t

--
--------------------------------------------------------
   Tomas Pospisek
   http://sourcepole.com -  Linux & Open Source Solutions
--------------------------------------------------------

Re: [Mailsync-list] Migrating cyrus imap Suse Emailserver 3 to Debian/testing

[Michael 'h. K. <mai...@zz...>]

I can't tell you much about cyrus imapd as such and suse/debian
installations in particular, but here are some notes.

Mailsync doesn't really care much about the physical storage behind the
imap daemon, since it just accesses mailboxen via network.

Mailsync is not meant to transfer many mailboxen, although, provided you
have a list of them with password with some effort you can make it do
the trick.

This is not what mailsync was intended to accomplish in the first place
and I do not think that it's a good idea to employ mailsync here.

As I already mentioned I have no idea about cyrus imapd and its
implementation of physical storage, but I think the optimal solution
here is to do the migration on filesystem level using rsync or similar
approach (maybe tarring and untarring the mail store, it depends). I do
not think imap daemon should care much about the locations and,
hopefully, it maintains some compatibility across versions. But this is
just a guess (in case I forgot to mention I have no idea about cyrus
imap daemon).

And even if the directory structure is not compatible, I'm pretty sure
it should be easily adjustable on filesystem level, anyway.

Love,
H

On Sat, Sep 11, 2004 at 10:54:07PM +0200, Sascha Wuestemann wrote:
> Hi mailsync-list members,
> 
> I am to migrate a running emailserver "Suse Emailserver 3" shipped with
> cyrus-imapd v2.0.16 to an up-to-date debian/testing with cyrus21-*
> v2.1.16. The new system shall replace the old and shall have all
> mailboxes containing full content and also all shared folders with full
> content - seen-information shall be original of all content, too. The
> emailusers shall notice no difference in use to the change.
> 
> The new debian emailserver is ready tested to take the old messages.
> 
> I have access to both email servers and backupserver filesystems, and I 
> am ordered not to stress the running server. So I'd like to use mailsync
> migrating from a local directory containing the old emailservers
> files.
> 
> My worries are, that the folder structure of old and new cyrus are so
> different.
> - Does mailsync care for it and places everything to the right
>   _new_version_ place? See downwards for a description.
> 
> I have not yet read the mailsync documentation carefully, because I am
> in a hurry and very limited with time. Testing is complicated because of
> limited bandwith and huge amount of data, so I'd like to ask you more
> questions:
> 
> Assuming above answer of my question is yes:
> - If I use a complete backup of all data to migrate residing in a local
>   directory, can I use mailsync to sync /old-directory to the current
>   system regarding all mailboxes, shared folders and seen information
>   with one single command?
> - I want to test the result of mailsync with a not up-to-date snapshot
>   just to make shure that everything will be alright and step back
>   afterwards and use the current data if I trust it. I assume just
>   deleting the corresponding directories of cyrus ( /var/spool/cyrus, 
>   /var/lib/cyrus) and restoring from a local backup of the situation
>   before would be sufficient, right? mailsync does not touch /etc or so,
>   does it?
> - Which directories of the old data must be in place if using from a
>   local directory?
> 
> Let me list information about the folder structure of old and new cyrus:
> 
> old:
> /var/spool/imap contains a lot shared folders, user and stage.
> /var/spool/imap/user contains folders with the mailusers name but no
> single letter directories - the mailusers name folders are the mailboxes
> /var/imap contains the working directory of cyrus, e.g mailboxes-db
> 
> new:
> /var/spool/cyrus/mail contains directories from a-z and stage.
> At the single letter directories you find user/ and mailusers name
> folders therein, e.g.
> /var/spool/cyrus/mail/s/user/sascha - this is the testuser's mailbox
> /var/lib/cyrus is cyrus' working directory
> 
> ...if mailsync is not capable to do what I am expected to get ready -
> does anybody know a source of tools which can migrate the structure of
> cyrus v2.0.16 to v2.1.16?
> 
> Thanks so far for reading.
> 
> greetings,
> Sascha
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
> Project Admins to receive an Apple iPod Mini FREE for your judgement on
> who ports your project to Linux PPC the best. Sponsored by IBM. 
> Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
> _______________________________________________
> Mailsync-list mailing list
> Mai...@li...
> https://lists.sourceforge.net/lists/listinfo/mailsync-list
> 

[Mailsync-list] Migrating cyrus imap Suse Emailserver 3 to Debian/testing

[Sascha W. <bi...@ki...>]

Hi mailsync-list members,

I am to migrate a running emailserver "Suse Emailserver 3" shipped with
cyrus-imapd v2.0.16 to an up-to-date debian/testing with cyrus21-*
v2.1.16. The new system shall replace the old and shall have all
mailboxes containing full content and also all shared folders with full
content - seen-information shall be original of all content, too. The
emailusers shall notice no difference in use to the change.

The new debian emailserver is ready tested to take the old messages.

I have access to both email servers and backupserver filesystems, and I 
am ordered not to stress the running server. So I'd like to use mailsync
migrating from a local directory containing the old emailservers
files.

My worries are, that the folder structure of old and new cyrus are so
different.
- Does mailsync care for it and places everything to the right
  _new_version_ place? See downwards for a description.

I have not yet read the mailsync documentation carefully, because I am
in a hurry and very limited with time. Testing is complicated because of
limited bandwith and huge amount of data, so I'd like to ask you more
questions:

Assuming above answer of my question is yes:
- If I use a complete backup of all data to migrate residing in a local
  directory, can I use mailsync to sync /old-directory to the current
  system regarding all mailboxes, shared folders and seen information
  with one single command?
- I want to test the result of mailsync with a not up-to-date snapshot
  just to make shure that everything will be alright and step back
  afterwards and use the current data if I trust it. I assume just
  deleting the corresponding directories of cyrus ( /var/spool/cyrus, 
  /var/lib/cyrus) and restoring from a local backup of the situation
  before would be sufficient, right? mailsync does not touch /etc or so,
  does it?
- Which directories of the old data must be in place if using from a
  local directory?

Let me list information about the folder structure of old and new cyrus:

old:
/var/spool/imap contains a lot shared folders, user and stage.
/var/spool/imap/user contains folders with the mailusers name but no
single letter directories - the mailusers name folders are the mailboxes
/var/imap contains the working directory of cyrus, e.g mailboxes-db

new:
/var/spool/cyrus/mail contains directories from a-z and stage.
At the single letter directories you find user/ and mailusers name
folders therein, e.g.
/var/spool/cyrus/mail/s/user/sascha - this is the testuser's mailbox
/var/lib/cyrus is cyrus' working directory

...if mailsync is not capable to do what I am expected to get ready -
does anybody know a source of tools which can migrate the structure of
cyrus v2.0.16 to v2.1.16?

Thanks so far for reading.

greetings,
Sascha

[Mailsync-list] Re: Bug/Feature requests for mailsync

[Tomas P. <tp...@so...>]

(replying late, but...oh well)

On Fri, 9 Jul 2004, Christian Schrader wrote:

> while migrating a mailserver I found two Bugs/missing features:
>
> 1. It is not possible to specify mailboxes with spaces in the name
>   for pat in the config file.

OK, as Michael said, you can use backslashes to do that, but quoting seems 
nicer - but:

> I tweaked the config parser that I can
>   use quotes. Well, I cannot program so this is just a hack to get my
>   work done.
>
> (patch against mailsync-5.2.1)
> ------------------------ snip ----------------------------
> --- configuration.cc.orig       2004-06-14 13:34:04.000000000 +0200
> +++ configuration.cc    2004-07-09 11:00:18.000000000 +0200
> @@ -66,6 +66,7 @@
> //////////////////////////////////////////////////////////////////////////
> {
>   int c;
> +  int inq = 0;
>   t->buf = "";
>   t->eof = 0;
>   while (1) {
> @@ -93,7 +94,10 @@
>
>     // We've reached a token boundary
>     }
> -    else if (isspace(c)) {
> +    else if (c=='"') {
> +      inq = !inq;
> +    }
> +    else if (isspace(c)  && !inq) {
>       // The token is non empty so we've acquired something and can
>       // return
>       if (t->buf.size()) {
>         break;

... could you provide me with a patch that also allows quotes in names?

> 2. It should be possible to disable the use of SSL via commandline
>   switch or config option. Now it is only possible to enable it.
>   The mailsync on Debian/Sarge tried to use SSL per default and I got
>   an SSL-Error with an old uw-imapd on the other side. I had to rebuild
>   libc-client and mailsync without SSL support.

As Michael said as well, this is a libc-client issue. Can you talk to Mark 
Crispin about this?

*t

--
--------------------------------------------------------
   Tomas Pospisek
   http://sourcepole.com -  Linux & Open Source Solutions
--------------------------------------------------------

Re: [Mailsync-list] capabilities (ACL)

[Tomas P. <tp...@so...>]

On Mon, 30 Aug 2004, W-Mark Kubacki wrote:

> Does mailsync sync mail's flags and mailboxes ACLs?

No (hasn't been done yet).
*t

--
--------------------------------------------------------
   Tomas Pospisek
   http://sourcepole.com -  Linux & Open Source Solutions
--------------------------------------------------------

[Mailsync-list] capabilities (ACL)

[W-Mark K. <wm...@hu...>]

Hello!

Does mailsync sync mail's flags and mailboxes ACLs?
For example: Will the "answered"-flag be synced? Will my folder "INBOX.x.y" 
still have rights XYZ for the user A and DEF for user B?

Thanks four you help and answer,

Mark

Re: [Mailsync-list] gentoo ebuild.

[Michael 'h. K. <mai...@zz...>]

On Mon, Aug 23, 2004 at 09:25:53AM +0200, Tomas Pospisek wrote:
> On Fri, 20 Aug 2004, Michael 'hacker' Krelin wrote:
> 
> > Oops, while I was going to submit ebuild, I found out that it is already
> > submitted, but not in the distribution, yet.
> >
> > http://bugs.gentoo.org/show_bug.cgi?id=53469
> >
> > Strangely enough, there are gcc 3.4 patches. Isn't the latest release
> > gcc3.4 enabled?
> 
> Ouhm - the patch consists in replacing all the c-client.h includes with
> c-client-wrapper.h. Maybe the person who submitted this was using a
> pre-5.2.1 release as a base and added the c-client-wrapper after?
> 
> I'm Bcc:-ing the person, so maybe he'll comment. (Bcc: since maybe he
> doesn't want to get involved)

Yes... It's a 5.1.2 based. I overlooked similar-looking numbers :)

> > The ebuild proposed there also makes use of krb,ssl, etc. options. Would
> > you people using it with options and without tell me if these are really
> > mailsync features or mailsync depends on the c-client configuration and
> > we just have to figure out options to make it compile?
> 
> It's the later.

Yes, I checked that already through the autoconf script.

> > Anyway, Tomas, I think you may wish to take a look at the ebuild. I
> > liked mine better -- it's short :)
> 
> ;-). I guess the gentoo people get to decide :-).

True. Anyway, the latest comment on the bug page is mine and I've
attached my ebuild. I think the rest is up to gentoo people.

Love,
H

Re: [Mailsync-list] gentoo ebuild.

[Tomas P. <tp...@so...>]

On Fri, 20 Aug 2004, Michael 'hacker' Krelin wrote:

> Oops, while I was going to submit ebuild, I found out that it is already
> submitted, but not in the distribution, yet.
>
> http://bugs.gentoo.org/show_bug.cgi?id=53469
>
> Strangely enough, there are gcc 3.4 patches. Isn't the latest release
> gcc3.4 enabled?

Ouhm - the patch consists in replacing all the c-client.h includes with
c-client-wrapper.h. Maybe the person who submitted this was using a
pre-5.2.1 release as a base and added the c-client-wrapper after?

I'm Bcc:-ing the person, so maybe he'll comment. (Bcc: since maybe he
doesn't want to get involved)

> The ebuild proposed there also makes use of krb,ssl, etc. options. Would
> you people using it with options and without tell me if these are really
> mailsync features or mailsync depends on the c-client configuration and
> we just have to figure out options to make it compile?

It's the later.

> Anyway, Tomas, I think you may wish to take a look at the ebuild. I
> liked mine better -- it's short :)

;-). I guess the gentoo people get to decide :-).
*t

--
--------------------------------------------------------
  Tomas Pospisek
  http://sourcepole.com -  Linux & Open Source Solutions
--------------------------------------------------------

[Mailsync-list] gentoo ebuild.

[Michael 'h. K. <mai...@zz...>]

Oops, while I was going to submit ebuild, I found out that it is already
submitted, but not in the distribution, yet.

http://bugs.gentoo.org/show_bug.cgi?id=53469

Strangely enough, there are gcc 3.4 patches. Isn't the latest release
gcc3.4 enabled?

The ebuild proposed there also makes use of krb,ssl, etc. options. Would
you people using it with options and without tell me if these are really
mailsync features or mailsync depends on the c-client configuration and
we just have to figure out options to make it compile?

Anyway, Tomas, I think you may wish to take a look at the ebuild. I
liked mine better -- it's short :)

Love,
H

Re: [Mailsync-list] gentoo ebuild

[Michael 'h. K. <mai...@zz...>]

On the other hand, I think I'll proceed with submit as is. After all
there's nearly nothing to be possibly troublesome. Still, if any gentoo
users are around, I'd appreciate any feedback.

Love,
H
> 
> If there's anyone willing to test out mailsync ebuild for gentoo, you're
> welcome to try the file attached (I keep it in
> /usr/local/portage/mail-client/mailsync/ on my system).
> 
> Love,
> H

> # Copyright 1999-2004 Gentoo Foundation
> # Distributed under the terms of the GNU General Public License v2
> # $Header: $
> 
> DESCRIPTION="A mailbox synchronizer"
> HOMEPAGE="http://mailsync.sourceforge.net/"
> SRC_URI="mirror://sourceforge/${PN}/${PN}_${PV}.orig.tar.gz"
> LICENSE="GPL-2"
> SLOT="0"
> KEYWORDS="~x86"
> 
> IUSE=""
> 
> DEPEND="net-libs/c-client"
> 
> src_compile() {
> 	econf || die
> 	emake || die
> }
> 
> src_install() {
> 	make DESTDIR=${D} install pkgdocdir=/usr/share/doc/${P} || die
> }

[Mailsync-list] gentoo ebuild

[Michael 'h. K. <mai...@zz...>]

If there's anyone willing to test out mailsync ebuild for gentoo, you're
welcome to try the file attached (I keep it in
/usr/local/portage/mail-client/mailsync/ on my system).

Love,
H

Re: [Mailsync-list] mailsync on gentoo

[Michael 'h. K. <mai...@zz...>]

On Fri, Aug 20, 2004 at 10:13:19AM +0200, Tomas Pospisek wrote:
> On Thu, 19 Aug 2004, Michael 'hacker' Krelin wrote:
> 
> > Hello there,
> >
> > I have recently installed gentoo linux on my laptop and,
> 
> grin, no more a hard-core self made system? ;-)

What do you mean "no more"? Do you think I'm going to trash my desktop?
The reason for homebrewing was lack of flexibility of other
distributions. I was told gentoo is much better. It IS better, although
I haven't decided whether I want to stay with gentoo or fallback to
homebrewing. And, anyway, I don't have a time for yet another redo of
system (have a 15 days old daughter on my hands).

> > Should we suggest an ebuild to gentoo people? (I can prepare one)
> 
> Sure. I can add whatever infrastructure is needed to the archive.

Ok, I will take care of it. Any gentoo users around willing to put
an ebuild into /usr/local/portage?

Love,
H

Re: [Mailsync-list] mailsync on gentoo

[Tomas P. <tp...@so...>]

On Thu, 19 Aug 2004, Michael 'hacker' Krelin wrote:

> Hello there,
>
> I have recently installed gentoo linux on my laptop and,

grin, no more a hard-core self made system? ;-)

> of course,
> compiled mailync on the system. Well, it compiles with almost no
> problem, but the patch below makes the compile (and cvs update
> operation) smoother.
>
> Basically, it adds the file generated by the installed autotools version
> to .cvsignore and requests a proper automake version by exporting
> environment variable. That simple.

Committed.

> Should we suggest an ebuild to gentoo people? (I can prepare one)

Sure. I can add whatever infrastructure is needed to the archive.
*t

--
--------------------------------------------------------
  Tomas Pospisek
  http://sourcepole.com -  Linux & Open Source Solutions
--------------------------------------------------------

[Mailsync-list] mailsync on gentoo

[Michael 'h. K. <mai...@zz...>]

Hello there,

I have recently installed gentoo linux on my laptop and, of course,
compiled mailync on the system. Well, it compiles with almost no
problem, but the patch below makes the compile (and cvs update
operation) smoother.

Basically, it adds the file generated by the installed autotools version
to .cvsignore and requests a proper automake version by exporting
environment variable. That simple.

Should we suggest an ebuild to gentoo people? (I can prepare one)

Love,
H

Index: .cvsignore
===================================================================
RCS file: /cvsroot/mailsync/mailsync/.cvsignore,v
retrieving revision 1.5
diff -u -r1.5 .cvsignore
--- .cvsignore	28 Jan 2003 09:53:30 -0000	1.5
+++ .cvsignore	19 Aug 2004 20:48:31 -0000
@@ -9,5 +9,5 @@
 Makefile Makefile.in
 missing
 mkinstalldirs
-stamp-h1
+stamp-h1 stamp-h.in
 
Index: autogen.sh
===================================================================
RCS file: /cvsroot/mailsync/mailsync/autogen.sh,v
retrieving revision 1.3
diff -u -r1.3 autogen.sh
--- autogen.sh	1 Jun 2004 08:53:32 -0000	1.3
+++ autogen.sh	19 Aug 2004 20:48:31 -0000
@@ -1,5 +1,7 @@
 #!/bin/sh
-( automake --version | head -1 | grep -q ' 1\.[678]') || (echo "automake 1.6 or above is required"; exit 1)
+WANT_AUTOMAKE=1.8
+export WANT_AUTOMAKE
+( automake --version | head -n 1 | grep -q ' 1\.[678]') || (echo "automake 1.6 or above is required"; exit 1)
 aclocal -I acinclude     && \
 autoheader               && \
 automake -a              && \

[Mailsync-list] =?ISO-8859-1?B?p0G6obdOsnumYqq6pqykSrbcoUg=?=

<html>

<head>
<meta name="GENERATOR" content="Microsoft FrontPage 4.0">
<meta name="ProgId" content="FrontPage.Editor.Document">
<meta http-equiv="Content-Type" content="text/html; charset=big5">
<title>¤@­Ó­È±o¤F¸Ñªº¨Æ·~&nbsp; ¬°¤°»ò¤@­Ó¦]¤E¤G¤@¨ü¨a¦Ó°h¥îªº¦~»´¤H</title>
<style>
<!--
p
	{margin-right:0cm;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Arial Unicode MS";
	color:black}
div.Section1
	{page:Section1;}
p.MsoNormal
	{mso-style-parent:"";
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";
	color:windowtext;
	margin-left:0cm; margin-right:0cm; margin-top:0cm}
-->
</style>
</head>

<body>

<div class="Section1" style="layout-grid: 18pt none">
  <p align="center">
  <b><span style="font-size: 22pt; color: #3366ff; font-family: ¼Ð·¢Åé">
  <a href="http://98.to/kosu139">¤@­Ó­È±o¤F¸Ñªº¨Æ·~</a></span></b><span lang="EN-US" style="font-size: 10pt; font-family: Dollar"><br>
  </span><span lang="EN-US" style="font-size: 10pt"><br>
  </span><span style="font-size: 16pt">¬°¤°»ò¤@­Ó¦]</span><span style="font-size: 16pt; color: red; font-family: ¤å¹©·sÃÀÅé">¤E¤G¤@¨ü¨a¦Ó°h¥îªº¦~»´¤H</span><span style="font-size: 16pt">¡A¥L¨S¦³¯S§Oªº®a«Ç­I´º¡A</span></p>
  <p align="center"><span style="font-size: 16pt">¨S¦³¶¯«pªº¸ê¥»¡A§ó¨S¦³°ª¤H¤@µ¥ªº¾Ç¾ú¡C¦Ó¥L«o¯à¦b</span><span lang="EN-US" style="font-size: 20pt; color: red; font-family: ¤å¹©·sÃÀÅé">2¦~¤º</span><span style="font-size: 16pt">¡A</span></p>
  <p align="center"><span style="font-size: 16pt">§â</span><span style="font-size: 22pt; color: red; font-family: ¤å¹©·sÃÀÅé">¤ë¦¬¤J±q<span lang="EN-US">3¸UÅܦ¨60¸U¡C</span></span></p>
  <p style="line-height: 21pt" align="center">
  <span style="font-size: 16pt">¶Ç²Î¤u§@¾aÀV³¡¥H¤UÁÈ¿úµù©w¬¡¨ì¦Ñ¡A°µ¨ì¦Ñ¡A  
  ·Q¶U´Ú§ë¸ê¶}¤½¥q¥¢±Ñ¤@¦¸´N½¤£¤F¨­¡A¦ý¦¬¤J¦pªG¤@½ú¤lªº¦¬¤J¥u¬O<span lang="EN-US">3¸U5¸U¡A</span></span></p>
  <p style="line-height: 21pt" align="center">
  <span lang="EN-US" style="font-size: 16pt">°£¤F¹L¥Í¬¡¡A§Ú­ÌÁٯ঳¹Ú·Q¶Ü??<br>
  </span><span lang="EN-US" style="font-size: 14pt; font-family: ¤å¹©°É«F¬y">
  <a target="_blank" style="color: blue; text-decoration: underline; text-underline: single; font-weight: 700" href="http://98.to/jacky03/">¤F¸Ñ¤£¦YÁ«¡A§@¹Ú¤£½Òµ|¡Aµ¹¦Û¤v¤@­Ó¾÷·|¡A¤U¤@­Ó¥¿½T¨M©w!!</a></span></p>
  <p class="MsoNormal" align="center"><span lang="EN-US">&nbsp;</span><b><span style="COLOR: navy; FONT-FAMILY: ¼Ð·¢Åé"><font size="3">¦]¨Ï¥Î¯S®íµo«H¨t²Î¶Ç»¼</font><span lang="EN-US"><font size="3">,­Y¦³­«½Æ¦¬¨ì³y¦¨§A«H½c­t¾á¦b¦¹¦V±z»¡Án¡¨¹ï¤£°_¡¨</font></span></span></b><p style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center" align="center">
  <b><font color="#FF0000" size="3">¦pªG§A¬O·Q­n¤£³Ò¦ÓÀò©Î°½Ãi¨ú¥©¥ç©Î¬O¤£¯à±µ¨ü¬°¤F¦¨¥\¦Ó§ïÅܦۤvªºÃa²ßºDªº¤H¡A</font></b></p>
  <p style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center" align="center"><b>
  <font color="#FF0000" size="3">½Ð¤£­n¯d¤U¸ê®Æ¥H§K®ö¶O©¼¦¹ªº®É¶¡¡C</font></b></p>
  <p style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center" align="center"><u><i><b>
  <font face="·s²Ó©úÅé" color="#0000FF">¦p±z¤£Ä@·N¦b¦¬¨ì§Ú­Ìªº¹q¤l«H®§¡A¤]½Ð¿é¤J±zªº¹q¤l«H½c¡A§Ú­Ì±N°¨¤W¬°±z²¾°£</font></b></i></u></p>
  <p style="MARGIN: 0cm 0cm 0pt; TEXT-ALIGN: center" align="center">
  <span style="color: red; font-family: ·s²Ó©úÅé; font-weight: 700"><font size="3">
  ¦p¦³¥´ÂZ½Ð¨£½Ì</font></span></div>

</body>

</html>

Re: [Mailsync-list] synchronising Mail folders when neither machine runs imap

[Michael 'h. K. <mai...@zz...>]

> > This has probably come up lots of times, but I can't find any
> > reference to it in the lists (?), so I'll ask again...
> > I have two machines, and I want to be able to use either to send and
> > receive email.
> > But both are have  to collect from the POP3 server, and I want to see
> > the 'sent' emails from both of them on both machines.
> > And I can't guarantee that both will be on at the same time.
> > So intermittently syncing the mail folders looks like the best bet.
> > Can this be done with mailsync (and - say - ssh), or with mailsync and
> > rsync?
> > Or something?
> 
> How do you want to get the sent mails on the POP3 server? Pop is read &
> delete only...

You don't have to send mail via pop3 server to be able to synchronize
send-mail folders on two machines :)

Love,
H

Re: [Mailsync-list] synchronising Mail folders when neither machine runs imap

[Tomas P. <tp...@so...>]

On Tue, 13 Jul 2004, Anthony Winter wrote:

> This has probably come up lots of times, but I can't find any
> reference to it in the lists (?), so I'll ask again...
> I have two machines, and I want to be able to use either to send and
> receive email.
> But both are have  to collect from the POP3 server, and I want to see
> the 'sent' emails from both of them on both machines.
> And I can't guarantee that both will be on at the same time.
> So intermittently syncing the mail folders looks like the best bet.
> Can this be done with mailsync (and - say - ssh), or with mailsync and
> rsync?
> Or something?

How do you want to get the sent mails on the POP3 server? Pop is read &
delete only...
*t

--
--------------------------------------------------------
  Tomas Pospisek
  http://sourcepole.com -  Linux & Open Source Solutions
--------------------------------------------------------

Re: [Mailsync-list] synchronising Mail folders when neither machine runs imap

[Michael 'h. K. <mai...@zz...>]

On Tue, Jul 13, 2004 at 05:06:05PM +1200, Anthony Winter wrote:
> This has probably come up lots of times, but I can't find any 
> reference to it in the lists (?), so I'll ask again...
> I have two machines, and I want to be able to use either to send and 
> receive email.
> But both are have  to collect from the POP3 server, and I want to see 
> the 'sent' emails from both of them on both machines.
> And I can't guarantee that both will be on at the same time.
> So intermittently syncing the mail folders looks like the best bet.
> Can this be done with mailsync (and - say - ssh), or with mailsync and 
> rsync?
> Or something?

I believe this can be done with mailsync, ssh and imap. You don't have
to run imap server, but you'll have to have rimapd executable configured
so that c-client can run it over ssh. Not that I can provide any further
assistance in setting up imapd with c-client.

Love,
H

[Mailsync-list] synchronising Mail folders when neither machine runs imap

[Anthony W. <awm...@sa...>]

This has probably come up lots of times, but I can't find any 
reference to it in the lists (?), so I'll ask again...
I have two machines, and I want to be able to use either to send and 
receive email.
But both are have  to collect from the POP3 server, and I want to see 
the 'sent' emails from both of them on both machines.
And I can't guarantee that both will be on at the same time.
So intermittently syncing the mail folders looks like the best bet.
Can this be done with mailsync (and - say - ssh), or with mailsync and 
rsync?
Or something?

-- 
anthony winter

[Mailsync-list] Re: Bug/Feature requests for mailsync

[Tomas P. <tp...@so...>]

On Fri, 9 Jul 2004, Christian Schrader wrote:

> 2. It should be possible to disable the use of SSL via commandline
>    switch or config option. Now it is only possible to enable it.
>    The mailsync on Debian/Sarge tried to use SSL per default and I got
>    an SSL-Error with an old uw-imapd on the other side. I had to rebuild
>    libc-client and mailsync without SSL support.

I'm just reading on the c-client mailing list, that SSL is only enabled
when you connect to the SSL port - that means IMAPS aka port 993 instead
of IMAP2 aka port 143.

Would you mind verifying this?

*If* the above is correct then your setup is wrong - you're connecting to
an SSL port and expecting a non-ssl communication mode...
*t

--
--------------------------------------------------------
  Tomas Pospisek
  http://sourcepole.com -  Linux & Open Source Solutions
--------------------------------------------------------

Re: [Mailsync-list] Re: Bug/Feature requests for mailsync

[Michael 'h. K. <mai...@zz...>]

On Fri, Jul 09, 2004 at 06:06:25PM +0200, Christian Schrader wrote:
> Michael 'hacker' Krelin wrote:
> > A long before I ever looked up the code of mailsync I got a feeling that
> > one can use \ to escape characters (I had to use it to allow synchronize
> > #mh/ mailboxen). I believe that should do for spaces as well (Haven't
> > checked the code or tested, though).
> 
> Ohh, shame on me! In the machine where I wrote the scripts there is
> mailsync 4.5.3 installed. There is no escape example in
> examples/mailsync.gz but in the file of the new version is. I didn't see
> this, sorry. 

No problem, I think quoting may make sense, anyway, although the
priority of the task is much lower.

And, I believe, the said example comes from my aforementioned attempts
;-)

Love,
H