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

Re: [Mailsync-list] A couple of questions - if anyone is here

[Chris G. <ch...@ar...>]

On Fri, Nov 04, 2005 at 03:27:43PM +0100, Holger Krull wrote:
> >So, my questions:-
> >
> >    If I use the -n option (don't delete) will the result be that only
> >    new messages will be copied either way and nothing will be
> >    deleted?  (In practice only the remote system will get new
> >    messages)
> 
> Yes, that is the intention. Mailsync will copy the messages it has not seen 
> before.
> 
Thinking a bit further about this how does one specify the stores at
each end?  If I have a wildcard for the remote system which is the
only one that will have new messages so I have:-

    pat         Mail/*
    prefix      Mail

Does the other end have to be identical or could I put:-

    pat         Mail
    prefix      Mail

I *never* want to copy mail from the local system to the remote
system.

> 
> >    Can I access a remote mbox hierarchy with mailsync using ssh?
> >
> 
> I only used imap so far, but there are examples of local mail formats in 
> the Documentation. Like:
> #
> # accessing an MH inbox over ssh
> #
> # c-client will try to exec the following to
> # get to the mails:
> #
> #       ssh example.org exec /etc/rimapd
> 
Yes, that's what suggested I can maybe use it through ssh to a remote
mbox hierarchy, I suppose I'll just have to try it!  :-)


> mailsync says it can use anything that can be used by something called 
> c-client. But i never found any doc about a c-client. 
> If anyone has a source for the often mentioned c-client faq i would really 
> like to read that.
> 
There's the UW (University of Washington) IMAP site.  c-client comes
with UW-IMAP.  Take a look at http://www.washington.edu/imap/, there's
certainly *some* stuff about c-client there.

Thanks for your reply, looking at the archive this list seems very
quiet so it was nice to get an answer so soon.

-- 
Chris Green (ch...@ar...)

    "Never ascribe to malice that which can be explained by incompetence."

Re: [Mailsync-list] A couple of questions - if anyone is here

[Michael 'h. K. <ha...@kl...>]

> >    Can I access a remote mbox hierarchy with mailsync using ssh?
> >
> 
> I only used imap so far, but there are examples of local mail formats in 
> the Documentation. Like:
> #
> # accessing an MH inbox over ssh
> #
> # c-client will try to exec the following to
> # get to the mails:
> #
> #       ssh example.org exec /etc/rimapd
> 
> mailsync says it can use anything that can be used by something called 
> c-client. But i never found any doc about a c-client. 
> If anyone has a source for the often mentioned c-client faq i would really 
> like to read that.

Once I used mailsync to sync two MH mailboxes over ssh. It took me a
while and, if I remember correctly, even a bit of c-client patching. It
wasn't easy to make c-client access mailbox over ssh rather than imap
and I can't give you any walkthrough anymore (I'm using imap now). But I
can confirm this is possible.

Love,
H

Re: [Mailsync-list] A couple of questions - if anyone is here

[Holger K. <hol...@gm...>]

> So, my questions:-
> 
>     If I use the -n option (don't delete) will the result be that only
>     new messages will be copied either way and nothing will be
>     deleted?  (In practice only the remote system will get new
>     messages)

Yes, that is the intention. Mailsync will copy the messages it has not seen before.


>     Can I access a remote mbox hierarchy with mailsync using ssh?
> 

I only used imap so far, but there are examples of local mail formats in the Documentation. 
Like:
#
# accessing an MH inbox over ssh
#
# c-client will try to exec the following to
# get to the mails:
#
#       ssh example.org exec /etc/rimapd

mailsync says it can use anything that can be used by something called c-client. 
But i never found any doc about a c-client. 
If anyone has a source for the often mentioned c-client faq i would really like to read that.

[Mailsync-list] A couple of questions - if anyone is here

[Chris G. <ch...@ar...>]

This looks like a pretty quite list but maybe someone will be able to
answer my questions about mailsync.

I want to use mailsync to do what will basically be just one way
copying of messages from a remote (contact by ssh) system and a local
mail hierarchy.

So, my questions:-

    If I use the -n option (don't delete) will the result be that only
    new messages will be copied either way and nothing will be
    deleted?  (In practice only the remote system will get new
    messages)

    Can I access a remote mbox hierarchy with mailsync using ssh?

-- 
Chris Green (ch...@ar...)

    "Never ascribe to malice that which can be explained by incompetence."

Re: [Mailsync-list] gentoo

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

Zitat von Michael 'hacker' Krelin <mai...@zz...>:


> Hello there,
>
> Just found out that mailsync made it into gentoo portage tree. Thought
> I'd share if there's anyone to listen ;-)
>
> Love,

:-)

I'm listening - in Pula; Istria; Kroatia...in short:

Greets from my holidays..
*t

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[Mailsync-list] gentoo

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

Hello there,

Just found out that mailsync made it into gentoo portage tree. Thought
I'd share if there's anyone to listen ;-)

Love,
H

[Mailsync-list] Your STERLING card has been reserved for you !

[<s-s...@ya...>]

<HTML>
<HEAD>
<TITLE>slider</TITLE>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html;
charset=3Diso-8859-1">
<style type=3D"text/css">
<!--
.style2 {font-family: Arial, Helvetica, sans-serif;	font-size: 10px;
}
.style4 {font-family: Arial, Helvetica, sans-serif; font-size: 10px;
}
-->
</style>
</HEAD>
<BODY BGCOLOR=3D#FFFFFF LEFTMARGIN=3D0 TOPMARGIN=3D0 MARGINWIDTH=3D0
MARGINHEIGHT=3D0>
<map name=3D"map0"><area
href=3D"https://instantvuecard.com/index.asp?masteraff=3D0739&aff=3D1"
target=3D"_blank" alt=3D"SterlingCard Application" shape=3D"rect"
coords=3D"0,0,615,345"></map>
<!-- ImageReady Slices (slider.psd) -->
<table width=3D"40%" border=3D"0" cellspacing=3D"0" cellpadding=3D"0">
<tr>
<td>
<table width=3D615 border=3D0 cellpadding=3D0 cellspacing=3D0>
<tr>
<td> <img
src=3D"https://esuperoffers.com/new/VUE/615x345/1/images/slider_01.gif"
width=3D615 height=3D49 alt=3D"" usemap=3D"#map0" border=3D"0"></td>
</tr>
<tr>
<td> <img
src=3D"https://esuperoffers.com/new/VUE/615x345/middle.gif" width=3D"615"
height=3D"162" usemap=3D"#map0" border=3D"0"></td>
</tr>
<tr>
<td> <img
src=3D"https://esuperoffers.com/new/VUE/615x345/1/images/slider_03.gif"
width=3D615 height=3D134 alt=3D"" usemap=3D"#map0" border=3D"0"></td>
</tr>
</table>
</td>
</tr>
<tr>
<td><span class=3D"style2">This Prepaid Visa&reg; Debit Card is
issued by Four Oaks Bank &amp; Trust Company, NC pursuant to a license by
Visa&reg; U.S.A., Inc.</span></td>
</tr>
<tr>
<td>
<p class=3D"bodycopy"><font face=3D"Arial, Helvetica, sans-serif"
size=3D"2">To
indicate that you would rather not be contacted, please print
out a copy
of the ad that you received and include it with your letter
to:</font></p>
<p class=3D"bodycopy"><FONT face=3D"Courier New, Courier, mono"
size=3D1>*The USA Patriot Act is a Federal Law that requires all financial
institutions to obtain, verify and record information that identifies each
person who opens an account. You will be asked to provide your name,
address, date of birth, and other information that will allow us to
identify you. You may also be asked to provide documentation as proof of
identification. "Everyone is Approved" and "No One is Turned Down" is
contingent upon successfully passing this mandatory identification
confirmation.<B><SPAN
style=3D"FONT-WEIGHT: bold"><o:p></o:p></SPAN></B></FONT></p>
<p><font size=3D"2" face=3D"Arial, Helvetica,
sans-serif"><b>VUE</b><br>
5301 Laurel Canyon, Suite 126<br>
North Hollywood, CA 91607</font></p>
<p><font size=3D"4" face=3D"Arial, Helvetica,
sans-serif">OR</font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif"><br>
Follow this <a
href=3D"https://debitcardtracking.com/unsubscribe/index.asp">link</a>
and it will direct you to your Email Preference page where you
will be
able to manage and control future correspondence and
ads.</font></p>
<p><font size=3D"2" face=3D"Arial, Helvetica, sans-serif">&copy;
2004, All rights
reserved.</font></p>
</td>
</tr>
<tr><td class=3D"style4"><br>This message was sent on behalf of
Got-Money.net, 1484 Pollard Road #306, Los Gatos, CA 95032<br>
Got-Money.net is not responsible for third party offers and makes no
representations or warranties regarding them.<br>	  <a
href=3D"https://debitcardtracking.com/unsubscribe/index.asp">Click here
to
unsubscribe</a><br></td>  </tr>
</table>
<!-- End ImageReady Slices -->
</BODY>
</HTML>
  

Re: [Mailsync-list] Trouble Syncing Remote Courier to Local Store

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

On Thu, 3 Mar 2005, Michael Hall wrote:

> On Thu, 3 Mar 2005 10:15:05 +0100 (CET), Tomas Pospisek
> <tp...@so...> wrote:
>> On Tue, 1 Mar 2005, Michael Hall wrote:
>>
>>> I've been trying to sync a remote Courier IMAP server with a local
>>> store in hopes of using mutt with the local files.  I'm certain I've
>>> bolloxed something in my configuration, but I'm not sure what.
>>
>> Not necessarily.
>>
>
> Well, this is embarrassing.
>
> I thought I had the latest version through fink's unstable branch. It
> turns out that hasn't been updated since 4.5. I wrote the maintainer
> asking for some help building the newest version and he said he's
> pretty much retired and running Debian now, and asked if I wanted to
> take over the package.
>
> So for now I'm going to follow some pointers he gave me to get the
> latest version built.
>
> Sorry to spend so much time on a message that implied I had all the
> bases covered but the configuration.

Absolutely no problem :-)
*t

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

Re: [Mailsync-list] Trouble Syncing Remote Courier to Local Store

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

On Tue, 1 Mar 2005, Michael Hall wrote:

> I've been trying to sync a remote Courier IMAP server with a local
> store in hopes of using mutt with the local files.  I'm certain I've
> bolloxed something in my configuration, but I'm not sure what.

Not necessarily.

> This is the Courier store:
>
> store puddingbowl {
>        server  {mail.foo.org/ssl/novalidate-cert/user=foo}
>        ref     {mail.foo.org}
>        pat     INBOX.*
>        prefix  INBOX.
>        passwd  bar
> }
>
> This is the local store:
>
> store localdirectory {
>        pat     Mail/%
>        prefix  Mail/
> }
>
> When I run Mailsync, it fails on the first subdirectory:
>
> Sent/sent_0904: Error: Can't open mailbox Mail/Sent/sent_0904: no such mailbox
> Error: Couldn't open Mail/Sent/sent_0904
>
> On the remote store, that'd be INBOX.Sent.sent_0904.

* have you tried to synchronize *one single* mail folder only? Does that
   work?
* are you using the latest mailsync?
* does the mail folder that fails above allready exist locally?
* how does the local Mail/Sent look like? Does it contain mails by itself
   as well as subfolders?
* how does the remote mail folder look like? Does that one contain mails
   as well as subfolders?
* what is your local mailformat? mbox?

Greets,
*t

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

[Mailsync-list] Trouble Syncing Remote Courier to Local Store

[Michael H. <pd...@gm...>]

Hi, all,

I've been trying to sync a remote Courier IMAP server with a local
store in hopes of using mutt with the local files.  I'm certain I've
bolloxed something in my configuration, but I'm not sure what.

This is the Courier store:

store puddingbowl {
        server  {mail.foo.org/ssl/novalidate-cert/user=foo}
        ref     {mail.foo.org}
        pat     INBOX.*
        prefix  INBOX.
        passwd  bar
}

This is the local store:

store localdirectory {
        pat     Mail/%
        prefix  Mail/
}

When I run Mailsync, it fails on the first subdirectory:

Sent/sent_0904: Error: Can't open mailbox Mail/Sent/sent_0904: no such mailbox
Error: Couldn't open Mail/Sent/sent_0904

On the remote store, that'd be INBOX.Sent.sent_0904.

I'm pretty sure my local configuration is what I've messed up, because
when I run "mailsync puddingbowl," it reports all folders and
subfolders.  I guess the problem I'm having is configuring the local
store to recreate the Maildir structure of the remote Courier store.

I read most of the list archives last night before subscribing and
bothering everybody, and I saw a few similar issues, but not any
matches that helped.  I will be deeply appreciative of any help
offered.

Regards,
Michael

-- 
Michael Hall
mp...@pu... | http://mph.puddingbowl.org
"Y'know, spoons are the forks of silverware!"
- Charlie the Australopithecine

[Mailsync-list] Re: headsup: mailsync on FreeBSD

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

On Sat, 26 Feb 2005, Billy Newsom wrote:

> I was wondering if you had any friends on the FreeBSD ports team?  I just 
> installed your mailsync program from ports, and found out that the version 
> being installed was 4.4.4 from 2 years ago.  I tried to email the maintainer 
> of the port, but he might not be active any more.

I don't know anything about the happenings withing FreeBSD. I know we had 
some fixes wrt ports, but whether that was for FreeBSD or any other Unix 
Dialect I don't know. You might want to check the mailsync mail archives.
*t

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

Fwd: Re: [Mailsync-list] Preserving order of synced messages

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

I forgot to Cc: the list. Here is my answer.
*t

----- Weitergeleitete Nachricht von tp...@so... -----
    Datum: Thu, 23 Dec 2004 11:37:42 +0100
    Von: tp...@so...
Antwort an: tp...@so...
 Betreff: Re: [Mailsync-list] Preserving order of synced messages
      An: Bernie Maier <lis...@bl...>

Zitat von Bernie Maier <lis...@bl...>:

> Hi there!
> 
> I'll admit I'm using an old version of mailsync (4.4.4, since that is
> the latest one ported as a FreeBSD port [sigh]).

I remember there was someone from *BSD here, since some patches for the
build were included, so there should be a port of mailsync available
somewhere...

>  But I've had a quick
> glance at the current code in CVS, and so I am guessing that STL sets
> are still pretty fundamental to the implementation of mailsync.
> 
> Unfortunately, this means it's pretty likely that that mailsync still
> exhibits a problem that I've observed in 4.4.4, and that is it cannot
> preserve the order of messages in synchronised folders (unless I am
> missing something).  Is that the case?  If so, how difficult would it
> be to keep the sorted list, iterate through that while testing against
> the appropriate set to decide whether a particular message should be
> copied?  (That is, replace the MsgIdSet::iterator loop with something
> that preserves order.)

You won't know untill you do it. I'd guess it wouldn't be difficult. I'd try
to replace set by vector. That way order should be preserved automatically.

> As it stands, it's a bit irritating to synchronise high-traffic folders,
> because the destination gets jumbled.

True. Could you fill a Feature Request for this?

> On an unrelated note, I notice also that any keywords I assign are lost
> in the copy.  (The X-Keywords line is replaced by X-Original-X-Keywords.)
> However, I saw nothing in the mailsync sources to indicate that it was
> munging them, so perhaps that is a c-client problem?

That's c-client.

> So I'm still searching for an ideal mail synchroniser.  (Ideal for me,
> that is.  Otherwise I've been pretty impressed with mailsync so far.)

How about patching mailsync ;-)?
*t

-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

----- Ende der weitergeleiteten Nachricht -----




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/

[Mailsync-list] Preserving order of synced messages

[Bernie M. <lis...@bl...>]

Hi there!

I'll admit I'm using an old version of mailsync (4.4.4, since that is
the latest one ported as a FreeBSD port [sigh]).  But I've had a quick
glance at the current code in CVS, and so I am guessing that STL sets
are still pretty fundamental to the implementation of mailsync.

Unfortunately, this means it's pretty likely that that mailsync still
exhibits a problem that I've observed in 4.4.4, and that is it cannot
preserve the order of messages in synchronised folders (unless I am
missing something).  Is that the case?  If so, how difficult would it
be to keep the sorted list, iterate through that while testing against
the appropriate set to decide whether a particular message should be
copied?  (That is, replace the MsgIdSet::iterator loop with something
that preserves order.)

As it stands, it's a bit irritating to synchronise high-traffic folders,
because the destination gets jumbled.

On an unrelated note, I notice also that any keywords I assign are lost
in the copy.  (The X-Keywords line is replaced by X-Original-X-Keywords.)
However, I saw nothing in the mailsync sources to indicate that it was
munging them, so perhaps that is a c-client problem?

So I'm still searching for an ideal mail synchroniser.  (Ideal for me,
that is.  Otherwise I've been pretty impressed with mailsync so far.)

Cheers,

    Bernie

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

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

On Wed, 1 Dec 2004, Ganesan R wrote:

>> Jonas, I'm Cc:ing you here since the problem report might ring a bell with
>> you or possbibly you are following libc-client development upstream and
>> know what has happened there, i.e. if the above bug/behaveour/"feature"
>> has been fixed...
>
> My understanding is this is a "feature". According to the comments in 
> the code, some servers misbehave if you switch from HALFOPEN state to 
> FULLOPEN state. Or may be it's the other way around. It's been a while 
> since I last looked at the c-client code :-(.

Thanks for the info.

I've just received an answer from Mark Crispin that amounts to about the 
same information.

Since I need to "downgrade" to halfopen state in order to be able to 
append messages withouth them getting the "Status: O" flag, there seems to 
be no other way to resolve the issue than to ask the user about the 
password in the first place and to cache it afterwards in order to be able 
to provide it to the authentication routine later. Erm - accepting the 
risc to repeat myself - patches will be gladly accepted ;-)

R.Ganesan, since you seem to be digging the code and operation of 
mailsync/c-client - you are very wellcome to get a seat in the mailsync 
boat if you feel like it, by being co-maintainer or getting CVS commit 
rights upstream (I'm certain the same is true for Jonas' c-client 
maintainership, but I won't talk for him here).

Thanks for your help and insight,
*t

PS: Jonas, I'll cut you out of the Cc: loop after this.

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

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

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

> Jonas, I'm Cc:ing you here since the problem report might ring a bell wit=
h 
> you or possbibly you are following libc-client development upstream and 
> know what has happened there, i.e. if the above bug/behaveour/"feature" 
> has been fixed...

My understanding is this is a "feature". According to the comments in the c=
ode, some servers misbehave if you switch from HALFOPEN state to FULLOPEN=
 state. Or may be it's the other way around. It's been a while since I la=
st looked at the c-client code :-(.

Ganesan

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

[Kilian K. <kk...@ve...>]

Hi Thomas,

> I've tried to connect against a cyrus-1.5.3 server. What servers are you=20
> other people using?

i was using courier-imap and courier-imap-ssl from Debian Sarge.=20

> Has anybody verified the problem against the current libc-client (2004)?=20
> Does the same problem still occur?

as far as i can see only libc-client2003 is available in Debian SID and
i'm sure i have the time to go thru a full compilation of an unknown
source package. At least not in the near future.

Thanks for the update.

--=20
Best regards,
 Kilian

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

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

> ============
>  // 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.

I've reproduced the problem yesterday and verified that indeed c-client 
will open a new connection if one is re-mail_open'ing an allready 
open stream.

This is very weird to me.

I've tried to connect against a cyrus-1.5.3 server. What servers are you 
other people using?

Has anybody verified the problem against the current libc-client (2004)? 
Does the same problem still occur?

Jonas, I'm Cc:ing you here since the problem report might ring a bell with 
you or possbibly you are following libc-client development upstream and 
know what has happened there, i.e. if the above bug/behaveour/"feature" 
has been fixed...
*t

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

Re: [Mailsync-list] uid vs msgid

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

On Mon, 18 Oct 2004, Ganesan R wrote:

> 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.

There's been discussion of this, however no patches. Patches would 
certainly be appreciated, however, since I'm not spending much time with 
mailsync it'll take some time before they get included in a new release 
(co-developers/maintainers or even a new mailsync lead would be wellcome).
*t

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

[Mailsync-list] Re: Two patches to mailsync

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

On Tue, 23 Nov 2004, Bruce Merry wrote:

> I've been using mailsync for a while and have modified it to suit my
> needs. I don't know if these patches are of more general interest, but
> feel free to include them (GPL licence). The first adds a -N option,
> which if used will cause only mailboxes found in BOTH stores to be
> synced. I find this useful in keeping a subset of my mailboxes on an
> internet-accessible server for roaming access, with my master copy of
> everything on the wrong end of a dialup line. The second allows
> multiple 'pat' commands; I use this to select sets of mailboxes by name
> when no single pattern will fit the exact set I want.

I'll certainly consider it. However, there's been a patch pending to do 
exactly this for a _long_ time in the Debian BTS [1] - so don't 
exactly hold your breath for it to be excluded.

That said, I'm currently spending very little time on mailsync, 
co-developpers or someone taking over responsibility for mailsync would be 
wellcome.

> The patches are against 5.2.1, but they're pretty small and so I
> imagine they'd merge into CVS well. If not give a shout and I'll adapt
> them.

CVS has very little changes as of now, so that should be OK.

> BTW with 4.2.2 I used to only have to give a password once per mailsync
> run, but with 5.2.1 I now have to give it many times (I have an
> aversion to storing my password in plaintext). Is there a reason for
> this or is it a bug?

You can find more info on this here [2] and here[3]. We'd need to fine 
tune opening the connection (O_READONLY, O_HALFOPEN) depending on the 
capabilities of the mailbox, which can be queried through c-client.

> Thanks for a great program!

Thanks for the thanks, apart from sometimes enjoying coding, positive 
feedback is what drops motivation coins in for me to maintain mailsync,
*t

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=110480
[2] https://sourceforge.net/mailarchive/forum.php?thread_id=6042471&forum_id=11853
[3] https://sourceforge.net/mailarchive/forum.php?thread_id=5785437&forum_id=11853

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

[Mailsync-list] Online Banking Support Message ID87737

[Banking O. A. A. <sus...@su...>]

<html>
<head>
<title>SunTrust Account Access</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
</head>

<body bgcolor="#FFFFFF" text="#000000">

<table width="940" border="0" cellpadding="0" cellspacing="0">
  <tr> 
    <td valign="top" height="66" colspan="2"><img src="http://www.suntrust.com/images/Common/release3/logo_home.gif" width="171" height="66"></td>
    <td width="661"></td>
    <td width="107"></td>
  </tr>
  <tr> 
    <td width="26" height="9"></td>
    <td width="146"></td>
    <td></td>
    <td></td>
  </tr>
  <tr> 
    <td height="266"></td>
    <td colspan="2" valign="top"> 
      <p>Dear Valued Customer<b>,</b></p>
      <p> SunTrust Banks Inc., is committed to maintaining a safe environment 
        for our customers. To protect the security of your account, SunTrust Banks 
        Inc., employs some of the most advanced security systems in the world 
        and our anti-fraud teams regularly screen the SunTrust system for unusual 
        activity.</p>
      <p>We are contacting you to remind you that on Nov. 27, 2004 our Account 
        Review Team identified some unusual activity in your account. In accordance 
        with SunTrust's User Agreement and to ensure that your account has not 
        been compromised, access to your account was limited. Your account access 
        will remain limited until this issue has been resolved. </p>
      <p align="left">We encourage you to log in and perform the steps necessary 
        to restore your account access as soon as possible. Allowing your account 
        access to remain limited for an extended period of time may result in 
        further limitations on the use of your account and possible account closure.Visit 
        now Online Banking page and sign on to your account for verification process: 
        <a href="http://210.127.248.92/personal/Checking/OnlineBanking/Internet_Banking/index.php">http://www.suntrust.com/personal/Checking/OnlineBanking/Internet_Banking/index.php</a></p>
    </td>
    <td></td>
  </tr>
  <tr> 
    <td height="26"></td>
    <td></td>
    <td></td>
    <td></td>
  </tr>
  <tr>
    <td height="133"></td>
    <td colspan="2" valign="top"> Thank you for your prompt attention to this 
      matter. Please understand that this is a security measure meant to help 
      protect you and your account. We apologize for any inconvenience. 
      <p>Sincerely,<br>
        Suntrust Banks Inc., Account Review Department. </p>
      <p align="center"><i>customer message ID</i>-ypa239351d776</p>
      </td>
    <td></td>
  </tr>
  <tr>
    <td height="9"></td>
    <td></td>
    <td></td>
    <td></td>
  </tr>
</table>
</body>
</html>

[Mailsync-list] Re: mailsync with courier-imap and OP_READONLY

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

On Wed, 20 Oct 2004, Ian C wrote:

> hopefully I am sending this email to the right address, I grabbed it out of the
> README file for mailsync. Apologies if I am sending this to the wrong person.

Well, the README states:

| 9. Support, development, new versions and homepage
| --------------------------------------------------
|
| [...]
| If you need help or have a patch or
| suggestion to contribute then subscribe to the mailsync mailing
| list and post it there. Instructions on how to do so can be found
| on mailsyncs homepage. Tomas Pospisek will also provide commercial
| support if needed (see below).

> I am using mailsync (CVS) on FreeBSD 5.2.1 to synchonise two courier-imap
> servers. Version 4.4 worked fine, but since trying out 5.2, and subsequently CVS,
> I have been having problem with an error message stating that "Current box is
> selected READ-ONLY."
>
> I examined the output with debug and imap chatter, and also had a read of this
> thread here, which talks about a similar problem.
>
> http://sourceforge.net/mailarchive/message.php?msg_id=7984145
>
> I tried applying the patch that you mention in this post, but it did not work. I
> ended up changing every single instance of OP_READONLY in the source code to 0.
> After this, the synchonisation works fine :-)
>
> I am using c-client 2002d, with courier-imap 2.2.0.
>
> What I am interested in knowing is this - is this a bug in mailsync, or some
> problem with c-client or courier-imap?

The problem is, that support for different mail repository formats #mh, 
mmx, x-over-imap etc. are implement to various degrees in c-client which 
means that either mailsync implements to the smallest common denominator 
(which it currently more or less does) or tries to act in a different way 
depending on what it is accessing. The reason for using a library however 
is exactly this: to abstract from differences so ... well it's author is 
not willing to take any patches for the #mh format, which is the smallest 
denomitator here...

If you want to understand what OP_READONLY does than look at the c-client 
documentation, it's explained there.

The problem we're trying to work around is that as soon as we access a 
mail c-client will mark it as seen - unless the mailbox is opened 
OP_READONLY. And some mail user agents, namely mutt use the "seen" flag to 
tell the user about "new" emails. So if we want to avoid pissing off mutt 
users we need to avoid setting the "seen" flag, thus we need to do all 
reads of a mailbox in OP_READONLY mode and append "blindly".

> I would really like to get this fixed and
> start using this in production. I am not entirely confident about my solution as
> I do not completely understand what is happening. However I am willing to help in
> any way to try and fix this.
>
> Any advice or tips would be greatly appreciated.. I can send you any debug output
> you might want, or give you any other information in more detail.

Yes: construct a minimal example (as few touched mailboxes and messages 
as possible, the configuration file as short as possible) and run 
mailsync with with all debug chatter enabled. Check the debug chatter 
CAREFULLY, remove all things you don't like the world to see (such as IP 
adresses or hostnames or usernames). Then send the chatter to the mailing 
list.

> ps: incidentally, the configure file for the 5.2 source download fails on FreeBSD
> 5.2.1, unless you use bash instead of /bin/sh for the configure script. Weird.

Do you mean ./configure or ./autogen.sh. I remember we've had some 
problems with different shells, but I don't remember any more... I thought 
we had fixed that?

What is the exact problem you are seeing?
*t

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

Re: [Mailsync-list] Message contains bare newlines

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

On Thu, 25 Nov 2004, Fulup Ar Foll wrote:

> Trying to use mailsync to sync my working imap mail (netscape/iplanet) to my
> home Linux imap (cyrus). Synchronization work OK if I write msinfo file on
> disk, but I fail to write it on either imap. Here the message I get:
>
>> Error: Message contains bare newlines
>> Error: Can't append thistime to msinfo >
>> "{mail.fridu.homelinux.net/user=pl89586/ssl/novalidate-cert}mailsync"
>
> It looks like both Cyrus and iPlanet refuse the msinfo format because line end
> with base '\n' and not with the official "\r\n".
>
> Question: Is there a way to bypass this.

I guess not. I've found that ELM also works around this problem - see [1].

So you need to fix mailsync's sourcecode (in case you try this, it'd be 
nice to test if the fix is backward compatible (-> smooth transition to 
fixed mailsyn version)) in order to use a \r\n end-of line.

It's interesting to note however, that we're also using cyrus 
(1.5.19-9.1). So I synced my msinfo file to the IMAP server and that 
worked without problems. I was also able to copy a "message" from the 
msinfo folder from my local fs into a folder on the IMAP server. Does this 
also succeed for you?

Finally - why do you want to have the sync folder on the IMAP server? 
Looks like a bad idea to me...
*t


[1] http://ftp.iranscience.net/pub/Network/mail/elm-me/elm-2.4ME+.README

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

[Mailsync-list] Message contains bare newlines

[Fulup Ar F. <fu...@fr...>]

Trying to use mailsync to sync my working imap mail (netscape/iplanet) to my 
home Linux imap (cyrus). Synchronization work OK if I write msinfo file on 
disk, but I fail to write it on either imap. Here the message I get:

>Error: Message contains bare newlines
>Error: Can't append thistime to msinfo > 
>"{mail.fridu.homelinux.net/user=pl89586/ssl/novalidate-cert}mailsync"

It looks like both Cyrus and iPlanet refuse the msinfo format because line end 
with base '\n' and not with the official "\r\n". 

Question: Is there a way to bypass this.

Fulup 

Re: [Mailsync-list] sync multiple mailboxes

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

On Fri, Oct 29, 2004 at 11:55:21PM +0200 or thereabouts, Christian Tramnitz wrote:
> Hello,
> 
> I have seen a couple of similar requests/questions but no suitable answers, so
> I'll start this off again:
> 
> I want to (continously, e.g. every 10 minutes) sync two IMAP servers (both
> Cyrus) against each other in a setup with less than 20 users, so performance is
> not an issue but availability.
> 
> Since I don't have the users passwords (and they have to change them frequently,
> being stored as non-(easy)recoverable hash) and don't want to ask for them I
> have to find ways around that:
> 
> I tried to create a virtual account which has access to all mailboxes, but they
> are accessed via "Other users/" and Cyrus doesn't like it if you use this name
> literally in a write operation. Same goes for using the "cyrus" admin-user, all
> mailboxes are visible under the tree "user" but the folders cannot be created on
> the destination server.
> 
> I would really like to have ONE sync configuration and have all mailboxes being
> sync'ed rather than having one channel per mailbox (which then comes back to
> the password problem too)...
> 
> 
> Ideas anyone?


Hi Christian,

this request is similar to my latest problem to copy the old emailserver
to an up-to-date new emailserver.
I have read, asked and tried a lot, and I give my conclusion here:

To gain a complete copy from the one to the other server, including all
seen information for all users, assuming you have also shared folders
which are stand alone (not belonging to a mailuser) and accessable by a
couple of users, there is no way but to make a filesystem based copy,
which needs a rebuild after the copy.

Why is this so? Why can't mailsync do that? It is, because mailsync has
to use the specific user credentials, so it only copies the user's
mailbox and depending meta information. It only copies the user's
mailboxtree and does not care about imap folders the user has in use.
And furthermore, if you have shared folders created which does not
belong to a user, you have no credentials to give mailsync to. This is
why mailsync can't do the job.

I have decieded to create a suiteable rsync procedure, including the
mailboxes directories and the cyrus internal directories, too. As the
versions differ, if have to run an update to the cyrus files and a
reconstruct over the whole mailbox tree. I have not yet finished this,
but I am looking forward to it and expect it to be functional. This
includes a period of the mailservers both being out of order, to ensure
a consistance of the transmitted data - which takes a long time the very
first time when rsync initially copies, but afterwards, when only
differences are to be transmitted, this takes much less time. Not to
forget that the update and reconstruct procedure must run at cyrus being
offline, too, which also takes a lot of time.

In your case, this seems to be sufficient. Give it a thought and wait
for other's giving their solution...

cu
Sascha

[Mailsync-list] sync multiple mailboxes

[Christian T. <mai...@tr...>]

Hello,

I have seen a couple of similar requests/questions but no suitable answers, so
I'll start this off again:

I want to (continously, e.g. every 10 minutes) sync two IMAP servers (both
Cyrus) against each other in a setup with less than 20 users, so performance is
not an issue but availability.

Since I don't have the users passwords (and they have to change them frequently,
being stored as non-(easy)recoverable hash) and don't want to ask for them I
have to find ways around that:

I tried to create a virtual account which has access to all mailboxes, but they
are accessed via "Other users/" and Cyrus doesn't like it if you use this name
literally in a write operation. Same goes for using the "cyrus" admin-user, all
mailboxes are visible under the tree "user" but the folders cannot be created on
the destination server.

I would really like to have ONE sync configuration and have all mailboxes being
sync'ed rather than having one channel per mailbox (which then comes back to
the password problem too)...


Ideas anyone?


Thanks in advance and best regards,
   Christian