From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.109.137 with SMTP id hs9cs25233vdb; Wed, 30 Mar 2011 07:40:26 -0700 (PDT) Received: by 10.52.70.134 with SMTP id m6mr1742869vdu.86.1301496024957; Wed, 30 Mar 2011 07:40:24 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id w12si313883vcf.197.2011.03.30.07.40.24; Wed, 30 Mar 2011 07:40:24 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 6D7981858361; Wed, 30 Mar 2011 10:40:24 -0400 (EDT) Received: from mail-bw0-f50.google.com (mail-bw0-f50.google.com [209.85.214.50]) by rubyforge.org (Postfix) with ESMTP id 81EB11858374 for ; Wed, 30 Mar 2011 10:21:05 -0400 (EDT) Received: by bwz2 with SMTP id 2so1221819bwz.23 for ; Wed, 30 Mar 2011 07:21:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=QiMoNkjy6tlZHKx3fs6s1jK54ba0Bk6v07uZT5TQzbI=; b=U1oxk3XnNP3G4+2K9g0FESu3/EjYcZLvDZ+hxGkszguyaNntql0TOXrUPbzniIWu6Y eoBV/5bnZTypeyb3IxAFvQGSWgKjmA5dcD1yvAj6S/sQ1n1ipCmqGMMZVXmUmuvcEXeE hvo+NPVAuuFevl1uFu43USJ6StMv24rTiaMrU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=t6JXDiZgkjcf3XlylNXzuAkrHmod5QYoNPsMBj61DUF7ZY1fJnive5Wj+CPT+5fjdW YWUEa66lMwKEu15m6Um1KwahUyW8zilBcc9Z9kbHbr/9q3nDThOBKes7pxmV0M6keeQ0 CCGVVOn9951KXBgbxtLDRSNY841pikXcrb/78= MIME-Version: 1.0 Received: by 10.204.171.65 with SMTP id g1mr1173302bkz.45.1301494864523; Wed, 30 Mar 2011 07:21:04 -0700 (PDT) Received: by 10.204.16.143 with HTTP; Wed, 30 Mar 2011 07:21:04 -0700 (PDT) In-Reply-To: References: Date: Wed, 30 Mar 2011 08:21:04 -0600 Message-ID: From: Bryan Richardson To: sup-talk Subject: Re: [sup-talk] Archive Emails to Different Source X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Anyone have an idea about this? I'm really hoping Sup can be a viable option for archiving emails... -- Thanks! Bryan On Fri, Mar 11, 2011 at 2:46 PM, Bryan Richardson wrote: > Hello All, > > I'm using Sup to access email from my company's Microsoft Exchange > Server via IMAP (using offlineimap). My Exchange mailbox size > limitation is 1GB, so every once in a while I will move email from my > Inbox to a personal Outlook archive file that is stored on my local > machine. However, when I do this the emails that I archive get removed > from my local IMAP cache the next time offlineimap runs. > > Is it possible to have Sup archive (or otherwise move) email messages > to a different IMAP source? I'm not so much worried about being able > to remove the messages from my Exchange account via Sup as I am > maintaining a local copy of all my email accessible via Sup. I can > archive them via Sup first then archive them in Outlook if that's what > it takes. > > Please advise. > > -- > Thanks! > Bryan > _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk