From: sean.escriva@gmail.com (Sean Escriva)
Subject: [sup-talk] a few questions on mail handling with sup
Date: Fri, 4 Sep 2009 12:13:32 -0700 [thread overview]
Message-ID: <20090904191332.GA5525@gmail.com> (raw)
I've got sup working with the exchange server at work thanks to
offlineimap, but I have a few questions I was hope to get some input
on.
Currently I have no way to way move messages out of my inbox on the
imap server, since I'm accessing a local maildir created by
offlineimap. This is only an issue since mailboxes have a limit of
800mb in size on the server and given the volume of mail I have that
will be reached every other month. I've looked at imap filter and this
could possibly work, but anyone have experience with this sort of
sitatuation?
Additionally, since sup doesn't actually change the
maildir, messages in the maildir do not seem be getting marked as not
new when reading them with sup and offlineimap then doesn't update the
message state on the server. Is there any way to addess this?
thanks!
next reply other threads:[~2009-09-04 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-04 19:13 Sean Escriva [this message]
2009-09-04 21:01 ` Ben Walton
2009-09-08 21:50 ` Sean Escriva
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=20090904191332.GA5525@gmail.com \
--to=sean.escriva@gmail.com \
/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