Excerpts from William Morgan's message of 2011-05-23 00:05:57 +0200:
> Reformatted excerpts from Sascha Silbe's message of 2011-05-18:
> > If heliotrope permanently erases the copies (instead of just not
> > exposing UI to access them), that would be a major step backwards.
>
> What do you suggest
Now that I have GMail to Heliotrope initial synchronization (first
time) and incremental (new messages) synchronization working in my
script I started working on Heliotrope to GMail synchronization.
Unfortunately I found some difficulties to achieve this.
I am following rfc4549.txt and the client-
Reformatted excerpts from Gaudenz Steinlin's message of 2011-05-23:
> Merging the messages is fine and actually an improvement over other
> MUAs.
I agree. I like the behavior.
> But adding a line in the header section indicating the source
> and how often the message appears in the source would b
Excerpts from Horacio Sanson's message of Fri May 20 16:38:30 +0100 2011:
> On Wed, May 18, 2011 at 2:05 PM, William Morgan wrote:
> > Reformatted excerpts from Horacio Sanson's message of 2011-05-17:
> >> I implemented a new version of the GMail -> Heliotrope sync script and
> >> attach it here in
Hi Horacio,
FWIW, you may use -- or even just take a look at -- the 'gmail' gem.
It works pretty well for back syncing and is built on RFCs too (if I'm not
mistaken).
For maildir backsyncing, the 'maildir' gem also do the job,
both are using the great 'mail' gem (which I hope, Heliotrope & co will
On Tue, May 24, 2011 at 6:22 AM, Hamish wrote:
> Excerpts from Horacio Sanson's message of Fri May 20 16:38:30 +0100 2011:
>> On Wed, May 18, 2011 at 2:05 PM, William Morgan wrote:
>> > Reformatted excerpts from Horacio Sanson's message of 2011-05-17:
>> >> I implemented a new version of the GMail
