From: Gaute Hope <eg@gaute.vetsj.com>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] A maildir root source: syncing labels with maildirs (imap folders)
Date: Wed, 27 Nov 2013 14:24:15 +0100 [thread overview]
Message-ID: <1385558459-sup-8094@qwerzila> (raw)
In-Reply-To: <1385557223-sup-3280@qwerzila>
Excerpts from Gaute Hope's message of 2013-11-27 14:08:36 +0100:
> Excerpts from Steven Schmeiser's message of 2013-11-27 13:42:33 +0100:
> > > I was thinking about changing one thing: currently messages are not
> > > copied into 'archive' before it has been _no_ other labels. On GMail
> > > you can still find it on the 'All mail' page on the web interface,
> > > but for regular IMAP accounts that doesn't work. Should the message
> > > always be copied to 'archive' when it is removed from the inbox?
> > >
> > > - gaute
> >
> > I don't have much personal preference between these two options. The
> > second option is closer to Gmail's "All Mail" folder that a lot of
> > people are familiar with, so maybe that is the way to go. Especially
> > if the "copy" is a hard link that doesn't take up disk space.
>
> I noticed Gmail does it that way in their IMAP interface (archive on no
> other labels), thats why I did it. I guess it doesn't matter all that
> much as long as we are all using Sup. Archive becomes a place for the
> uncategorized. I don't delete an email from archive if it is already in
> there, so if it at some point has been copied in there - it stays.
>
> Copy is hard-link, but I doubt offlineimap is able to identify remote
> identical emails. So hard-linking is only on the machine that the
> link happened on.
Another nice feature is that I now have the possibility to have my
filters on the server copy/move the message to a IMAP folder and it will be
automatically tagged in Sup as well.
Some servers automatically delete stuff in Trash / Deleted Items or
email marked as Trash (T), these will also be removed from Sup when they
are deleted (might not work when it is in several folders and only
marked with T).
- gaute
next prev parent reply other threads:[~2013-11-27 13:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 15:24 Gaute Hope
2013-11-25 18:23 ` [sup-devel] " Steven Schmeiser
2013-11-25 21:08 ` Matthieu Rakotojaona
2013-11-25 21:51 ` Gaute Hope
2013-11-25 22:28 ` Gaute Hope
2013-11-26 14:43 ` [sup-devel] " Steven Schmeiser
2013-11-26 15:14 ` Gaute Hope
2013-11-26 16:42 ` Steven Schmeiser
2013-11-26 16:55 ` Gaute Hope
2013-11-27 0:48 ` Steven Schmeiser
2013-11-27 6:21 ` Gaute Hope
2013-11-27 12:42 ` Steven Schmeiser
2013-11-27 13:08 ` Gaute Hope
2013-11-27 13:24 ` Gaute Hope [this message]
2013-11-27 18:32 ` Matthieu Rakotojaona
2013-11-27 21:10 ` Gaute Hope
2013-11-29 9:22 ` Gaute Hope
2013-11-27 6:23 ` Gaute Hope
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1385558459-sup-8094@qwerzila \
--to=eg@gaute.vetsj.com \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox