From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/66592 Path: news.gmane.org!not-for-mail From: Jake Colman Newsgroups: gmane.emacs.gnus.general Subject: Re: nnimap and Exchange 2007 Date: Fri, 28 Mar 2008 11:40:14 -0400 Message-ID: <48DD2FD744F23640B63C60A81E7679E70DA75BEC@exchange-d01.ppllc.com> References: <86iqz6vp7z.fsf@lifelogs.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1206718947 17923 80.91.229.12 (28 Mar 2008 15:42:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 28 Mar 2008 15:42:27 +0000 (UTC) Cc: "ding@gnus.org" To: 'Ted Zlatanov' Original-X-From: ding-owner+M15078@lists.math.uh.edu Fri Mar 28 16:42:58 2008 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1JfGj1-0001gC-Cb for ding-account@gmane.org; Fri, 28 Mar 2008 16:42:39 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1JfGhL-00084o-EI; Fri, 28 Mar 2008 10:40:55 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1JfGhJ-00084S-D8 for ding@lists.math.uh.edu; Fri, 28 Mar 2008 10:40:53 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtp (Exim 4.67) (envelope-from ) id 1JfGhD-0003bj-8U for ding@lists.math.uh.edu; Fri, 28 Mar 2008 10:40:53 -0500 Original-Received: from active.ppllc.com ([69.7.239.44] helo=exchange-d01.ppllc.com) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1JfGhL-00057L-00 for ; Fri, 28 Mar 2008 16:40:55 +0100 Original-Received: from exchange-d01.ppllc.com ([10.10.9.86]) by exchange-d01.ppllc.com ([10.10.9.86]) with mapi; Fri, 28 Mar 2008 11:40:14 -0400 Thread-Topic: nnimap and Exchange 2007 Thread-Index: AciQ6J3bIY2aheBNR+q+RL0TfEJd1AAAP+5Q In-Reply-To: <86iqz6vp7z.fsf@lifelogs.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US X-Spam-Score: -2.4 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:66592 Archived-At: Ted, Sorry for the top-quote. I'm stuck using Outlook for the moment (until I r= esolve my IMAP issue) and I cannot cite your message. This makes it diffic= ult for you to read my reply unless I do it this way. Please bear with me. The patch that you sent was a reverse patch. It shows what line to add to = get the old behavior. Instead, I reversed it and things seem better. I'm = not crashing out and Gnus seems to be catching up on a hell of a lot of old= marks from my server. It's certainly bust doing something - unless it hun= g. I'll keep you posted. Thanks. ...Jake -----Original Message----- From: Ted Zlatanov [mailto:tzz@lifelogs.com] Sent: Friday, March 28, 2008 11:33 AM To: Jake Colman Cc: ding@gnus.org Subject: Re: nnimap and Exchange 2007 On Fri, 28 Mar 2008 11:18:28 -0400 Jake Colman wrote: JC> I have not updated my gnus from a nightly snapshot since Feb 28 yet JC> I seem to already have the fix that you say you just committed. Am JC> I missing something here? Now I'm confused! "cvs status nnimap.el" should say 7.43. If it does, you're fine. JC> How do I use this suggested setup of your's? What will it do for me JC> exactly? I currently use nnimap-split rules to split my email into JC> folders on the IMAP server. If I do what you suggested as a JC> workaround, what will change and how do I work with it? It will take the new mail from your IMAP mail source and put it into your "home" Maildir. The mail will remain on IMAP, so you'll have two copies of it forever. You can, instead, delete the originals but I prefer not to. Disk space is cheap, resending e-mails is annoying. Please don't top-quote. Ted The information contained in this message is confidential and protected by law. If you are not the intended recipient, please contact the sender and delete this message. Any unauthorized copying of this message or unauthorized distribution of the information contained herein is prohibited.